Access screenshots from certain tests directly in testomat.io. Typically, artifacts are associated with automatic testing, but testers can add screenshots to manual tests as well; they will also be stored in reports.
Why Your Team Needs This Feature
The Screenshots capturing artifacts option allows you to view screenshots and thus visualize test results faster and easier. How does this process work without testomat.io?
- If you run autotests on a local PC, all screenshots are saved in a project. To view them, you need to open a specific project in the editor, find the appropriate folder and open the desired file.
- If you are launching in the cloud, on GitHub, Jenkins, etc., searching for the necessary screenshot is even more difficult.
Testomat.io gets all the necessary screenshots and automatically adds them to the report. The tester sees everything on one screen and understands what needs to be worked with first. This significantly saves time in testing a product, which means its release is faster.
How Screenshots Capturing Artifacts Works
So how does testomat.io get artifacts after testing on a local PC or in the cloud on a CI/CD service? We have integration on the platform with various S3 Storages: AWS, DigitalOcean, Azure, and Google Cloud. To get screenshots, all you need to do is:
- Have an S3 Object Storage Bucket on one of the mentioned S3 Storage;
- when running autotests, add parameters where you specify the configuration of your cloud storage;
- upon completion of the run, get a report with screenshots in testomat.io.
Note: artifacts are loaded after testing is completed and are available in Reporters by testing frameworks.
Features of Working With Function
- You can create screenshots only for passed tests, only for failed tests, or absolutely for all tests. To do this, in the project configuration, you need to select the appropriate settings according to the framework (Cypress, Playwright, etc.). That is, this parameter depends solely on your framework settings, not on testomat.io.
- It is possible to upload a screenshot in a public or private format. For private access, additional parameters and encryption are used. This option is relevant for projects that require enhanced security measures or when company policy forbids public access to their projects. Note: if you want to share a private screenshot, your recipient will receive a message that they do not have permission to view the file.
- If you have a problem while running manual tests, you can also easily take a screenshot and add it to testomat.io using Attachments from clipboard.
Reporters by testing frameworks
Test reports from testomat.io give you a complete picture of the product’s quality level. In Reporters by testing frameworks, you can see the results of end-to-end, integration, unit testing, and API testing. Thanks to the integration with many S3 Storages, testomat.io retrieves test artifacts (including screenshots) and uploads them to the report in a convenient format.
Automated Tests Analytics
All test results in testomat.io are used for in-depth analytics. Determining the percentage of automation, the total number of tests, and the ratio of tests to uncompleted tests – all of these allow you to prioritize testers’ work and make the process clear to all team members involved in product development.
After installing the Jira plugin, you can work with test cases directly from the project management system. You can bind tests to a project in Jira, perform a test run, and access reports of the test results. You can also go from Jira to the Run Report and view the desired screenshots.
Video Capturing Artifacts
In addition to saving screenshots, you can also save videos from tests, passed, failed, or all completed, regardless of the result. From Test Runner and Reporter, video files, like screenshots, are uploaded to S3 Storage, from where they end up in testomat.io in a user-friendly format. The videos can be viewed in the report or downloaded to your device.
Artifact S3 Support
With testomat.io, you can store artifacts in the cloud and choose the provider your company or CI/CD tool is comfortable working with: AWS, DigitalOcean, Azure, and Google Cloud.
Note: cloud providers’ services are far from being free, so when cooperating with them, consider the cost of using the desired configuration.