As testing becomes increasilingly embedded into the development and DevOp activities, it is extremely important to make test automation part to the continuous integration or delivery process. By doing this, testers can ensure that their tests are always targeting the latest version of the software and defects are caught as early as possible. This is easily achievable by using a tool like Jenkins to trigger the automated REST or UI tests every time developers commit code and the application under tests is deployed in the CI or Staging environment. However, one of the challenges of following this process is the time that it takes to analyze test failures and keep track of known issues. Looking at the test reports generated by the framework (JUnit, TestNG, Cucumber, etc.) might be ok at first, but as the number of tests and the number of daily commits grows, this process may become overwhelming. TestRecon solves this problem by allowing the testing and development team view all test results in a central location and quickly identify trends like tests failing with the same error code or flaky tests. In addition, it allows users to link test failures to bugs, add notes to tests and even link back to screenshots or other artifacts, due to its web-based nature.
Contact us to for a free trial
No comments:
Post a Comment