The matrix view gives an overview of test cases (rows), test runs (columns), and test instances (cells), with green indicating successful test runs and red indicating failed test runs. If you hover over a test run, a screenshot is displayed. With a single click, you’ll first get the most vital information. Double-click and you’ll receive even more—all the aggregated information, screenshots, and logfiles for the test run in one place.
.png)
Sqeed shows you the coverage of tests. The graph illustrates, for each test run, which page objects (nodes) were covered often (larger nodes), less often (smaller nodes) or never (grey). Page objects where test cases failed are marked in red, those without problems in green. The graph is compiled by parsing already available information from the logfiles.
-1.png)
The natural language-clustering algorithm automatically assigns failed test cases to a cluster. This saves time in root-cause analysis, as only one representative of the cluster needs to be inspected. Also, analyzing the clusters over time can identify trends and issues within the application, allowing you to focus on fixing the most critical ones first.
.png)
Sqeed offers the possibility to dynamically rerun a select number of test cases from different places. In the coverage graph, you can list all test cases related to the “home” screen with just one click and run them with another click. You can dynamically select and deselect test cases to include in the test run, see aggregated average runtime, and inspect coverage of the selected test cases.
.png)
The aggregated detail view provides log information from various sources, screenshots, videos, and other information in one centralized place. All you have to do is double-click on any test run in the matrix view to get to this information. No more different VM (Virtual Machine) logins, no more time-consuming and manual processes.
.png)
The matrix view gives an overview of test cases (rows), test runs (columns), and test instances (cells), with green indicating successful test runs and red indicating failed test runs. If you hover over a test run, a screenshot is displayed. With a single click, you’ll first get the most vital information. Double-click and you’ll receive even more—all the aggregated information, screenshots, and logfiles for the test run in one place.
Sqeed shows you the coverage of tests. The graph illustrates, for each test run, which page objects (nodes) were covered often (larger nodes), less often (smaller nodes) or never (grey). Page objects where test cases failed are marked in red, those without problems in green. The graph is compiled by parsing already available information from the logfiles.
The natural language-clustering algorithm automatically assigns failed test cases to a cluster. This saves time in root-cause analysis, as only one representative of the cluster needs to be inspected. Also, analyzing the clusters over time can identify trends and issues within the application, allowing you to focus on fixing the most critical ones first.
Sqeed offers the possibility to dynamically rerun a select number of test cases from different places. In the coverage graph, you can list all test cases related to the “home” screen with just one click and run them with another click. You can dynamically select and deselect test cases to include in the test run, see aggregated average runtime, and inspect coverage of the selected test cases.
The aggregated detail view provides log information from various sources, screenshots, videos, and other information in one centralized place. All you have to do is double-click on any test run in the matrix view to get to this information. No more different VM (Virtual Machine) logins, no more time-consuming and manual processes.
