Interactive feature verification testing
You can use the interactive feature verification testing framework to request tests for your system. When you request a test, Microsoft uses the framework to prepare tests that require manual interactive steps. Microsoft can use the framework to chain together several standalone automated tests.
This article describes a simple manual scenario. The test checks replacing a disk in Azure Stack Hub. The framework gathers diagnostic logs at each step. You can debug issues as you find them. The framework also allows the sharing of logs produced by other tools or processes and enables you to provide feedback on the scenario.
Important
This article references the steps to perform a Disk Identification Test. This is simply a demonstration and any results gathered from the Test Pass workflow can't be used for new solution verification.
Overview of interactive testing
A test for disk replacement is a common scenario. In this example, the test has five steps:
- Create a new Test Pass workflow.
- Select the Disk Identification Test.
- Complete the manual step when prompted.
- Check the result of the scenario.
- Send the test result to Microsoft.
Create a new test pass
If you don't have an existing test pass available, follow the directions for scheduling a test.
Schedule the test
Select Disk Identification Test.
Note
The version of the test will increment as improvements to the test collateral are made. The highest version should always be used unless Microsoft indicates otherwise.
Select Edit and provide the domain admin username and password.
Select the appropriate test execution agent/DVM to launch the test on.
Select Submit to start the test.
Access the UI for the interactive test from the agent selected in the previous step.
Follow the Documentation and Validation links to review instructions from Microsoft on how to perform this scenario.
Select Next.
Follow the instructions to run the precheck script.
Once the precheck script has completed successfully, run the manual scenario (Disk replacement) as described in the Documentation and Validation links from the Information tab.
Important
Don't close the dialog box while you're performing the manual scenario.
When you're finished performing the manual scenario, follow the instructions to run the post check script.
On successful completion of the manual scenario (Disk replacement), select Submit.
Important
If you close the window, the test will stop before it's done.
Provide feedback for the test experience. These questions will help Microsoft assess the success rate and release quality of the scenario.
Attach any log files you wish to submit to Microsoft.
Accept the feedback submission EULA.
Select Submit to send the results to Microsoft.
Next steps
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for