Application Discovery and Baselining
Once the login task is created, an automatic application discovery is triggered by Relicx Copilot. This discovery process involves navigating through the pages of your application, establishing a visual baseline that serves as a reference for subsequent comparisons during release validation runs.
Application discovery is triggered automatically only when the login task is created. All subsequent runs should be manually submitted using the Explore Application button. New exploration runs are only needed when your application undergoes any significant changes, new pages are added or existing pages are removed from the application
๏ปฟ
During this stage, our AI-driven Relicx Copilot autonomously discovers your application and generates an application map. This map serves as Relicx's representation of your application, with each page depicted as a node and interconnected by purple ribbons symbolizing navigation between pages. At a broader level, this application map facilitates a comprehensive understanding of the pages requiring testing prior to deploying a new release in production or any designated environment. Application discovery typically takes about 30 minutes but for more complicated applications it can take over an hour.
During application discovery, Relicx creates visual baseline of you entire application. You can click on each node in the graph to check the snapshot of the page i.e. how Relicx visualized your page during the app discovery phase.
Relicx copilot generates a page purpose and also breaks down the page into several components. Each component is highlighted by a purple bounding box on the page. The components are compared during the release validation and any indentified difference triggers a visual validation issue for that run.
Relicx Copilot also recommends at least 5 test cases as it discovers the applications. These test cases can be converted to full fledged tests using Relicx's intent based test authoring.
Relicx suggests you to review these recommendations are then convert them to tests as you see fit. These tests will be executed as part of release validation.
