Drive QA's evolution—share your voice and win prizes up to $3,000
TAKE THE SURVEY
All All News Products Insights DevOps and CI/CD Community
Table of Contents

Ensuring Visibility of Screenshots in Katalon Reports

Hello, Katalon users and software testing enthusiasts! Today, we’re addressing a common query raised in our community forum: why don’t screenshots appear in Katalon reports?

The Issue at Hand

Several users have reported that after successfully running their test suites, the screenshots captured during the tests do not appear in the generated reports1. This issue seems to be prevalent across different versions of Katalon Studio.

Understanding the Importance of Screenshots

Screenshots are an integral part of software testing reports. They provide visual evidence of the test results, making it easier to understand what happened during the test execution. If screenshots are missing from the reports, it can be challenging to pinpoint where and why a test failed.

Possible Solutions

Here are some steps you can take to ensure that screenshots are included in your Katalon reports:

  1. Check Your Settings: Navigate to Project -> Settings -> Execution in Katalon Studio. Ensure that the Take Screenshot when execution failed (applicable to Web UI and Mobile testings) option is checked. Apply the changes and close the settings.
  2. Verify the Report Folder: After running the test suite, check the report folder on your local machine. The screenshots might be saved there, even if they are not appearing in the Katalon interface.


 

If you’re facing a similar challenge, why not give these solutions a try? And remember, our community forum is a great place to share your experiences and learn from others. If you have any questions or need further assistance, don’t hesitate to Ask the Community!
 

The information in this blog post is based on a real-life scenario shared by a user on our Katalon Community forum and is intended to inspire peer-to-peer discussion and collaboration. Please always test solutions thoroughly before implementing them in a production environment.

Feel free to continue the discussion here


 

Click