I wrote an article about logging your autotests/scripts for debugging Writing Your Own Logs - DZone. It isn’t particularly about capturing technical information within the autotest framework, but anyway, I believe it’s quite relevant to the topic. I think that it’s crucial to collect as much data as possible - all actions, entity IDs, test data, and sometimes even timestamps, as well as response codes or the entire content, payload, headers, response time, etc. + collecting all the application logs makes it easier to identify the issues and how it was reproduced, and to locate specific logs on the server or other microservices/3rd party services
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| What do you share in your automation reports? | 13 | 2037 | 15 December 2025 | |
| What steps do you take to reproduce automation failures? | 7 | 562 | 26 March 2021 | |
| Collecting trends across multiple automation runs | 4 | 383 | 22 January 2021 | |
| What sort of questions would you be interested to have automation to help to answer? | 1 | 352 | 5 September 2020 | |
| How do you “Investigate Failed Automated Tests”? - Automation in Testing Curriculum | 3 | 4844 | 28 January 2023 |