Running Release Validation
In order to run Release Validation on your application, all you need to do is to click the "Validate Release" button in the Flows page view and set the desired configuration. Once complete, you will visually be able to see Relicx Release Validation traverse your application in the Flow diagram.
As Relicx captures sessions from your instrumented environments it will start building a graph of application pages that represent the user actions on your app. You will notice all nodes are colored purple as it represents an un-tested state.
Relicx recommends you to capture at least 100 user sessions before executing release validation
If a user selects the "Validate Release" button, a side bar with options for your run configurataion will appear. The user can choose the environment (i.e. Staging, Production, etc.) they would like the run Relicx Autonomous Testing on as well as the location depending on where your environment is hosted (i.e. Relicx Cloud or behind a firewall). The number of concurrent browsers control the number of browsers that will log into your test environment.
Relicx will restrict the number of concurrent browsers to 5 in the self serve tier. To increase the number of concurrent browsers please contact Relicx.
The default setting for concurrent browsers is 5, but more browsers allow Relicx to get all the points in your application faster. Needed parameters can be set and saved for future runs, the most common being login credentials, and that's it!
Once kicked off, Relicx Autonomous Testing will show how many browsers are currently executing at the top of the screen. This number can change based on where the browsers are operating and if they are able to proceed forward or backward at any given URL.
As the different parts of your application are traversed, the URL node will start to turn Green, Yellow or Red. GREEN means that all of the elements Relicx was able to find on any given page all functioned as expected. YELLOW means the node has passed testing with warning and RED means a critical or significant failure.
If a URL appears RED, then Relicx has reported an Issues within that portion of the application based on the checks above. A list of these issues can be seen in the next section Interpreting the results.
The Time stamp and length of Run can be seen underneath the main metrics at the top. As AutoTest does it's job, you will see the metrics change based on what it finds.
Page CX Coverage is defined as how much of the application Autonomous Testing was able to visit given the time, concurrent browsers and parameters provided.
Perfect application coverage may not be able to automatically achieved because of edge cases, or data seeding use cases that weren't captured in the Application's User Sessions. However, the effort removed from the bulk test cases creation through Relicx Autonomous Test takes a hands off approach the vast majority of repetitive tasks traditionally found in insuring Application quality.
