First Test Run
Last updated
Last updated
After performing the setup and configuring HyperTest, HyperTest is ready to run tests.
Click on the START NEW TEST from the Test Results Page.
You get a number of options while starting a new test:
Test Ids: has two options, custom and all.
Custom takes in ids of test cases you want to use in the test.
All will include every test case that satisfies the criteria that are further provided in the new test dialog box.
Initial and final timestamps: The range of traffic that will be considered. HyperTest will throw an error if there are no requests within the specified time frame.
Run only Smoke tests
Stop on the first failure
Run only saved test cases: Directly run a test that will be containing all the saved test cases.
Check API coverage: This shows the percentage of API that will be covered in the test that will be created.
In order to be able to see the percentage of APIs covered by HyperTest, it needs a swagger API file, the path of which can be provided to HyperTest via the OAS_DOC_PATH config parameter.
Upon the successful completion of the test, an analysis will be generated for you. Every such analysis contains a report called a Build Report that shows every change that has been observed by HyperTest.
Test id, for referencing purposes.
Primary Base Url
Candidate Base Url
Range of traffic covered by this test
API coverage for the test
Percentage of test cases that passed
Delete the test
View the test cases
Every test has at least one analysis, called a default analysis. HyperTest provides a number of filters that can be used to selectively pick information, which creates a new analysis.
For example, suppose a new change has been observed by HyperTest which is actually desired. Now if this change appears too frequently in the default report, it can be added to a custom list which creates a new Analysis. This also means that analysis are immutable; there will be one per set of conditions: analysis and other parameters such as filters.
