Artifacts

In the context of the GobletQA Platform, artifacts refer to the outputs or artifacts generated during the execution of tests and automation. These artifacts are valuable resources that provide insights, documentation, and evidence of the testing and automation activities. Let's explore the various types of artifacts produced by the GobletQA Platform:

Artifacts Directory

All artifacts generated by goblet are automatiaclly placed in the paths.artifactsDir directory defined in the Goblet Config.
If the paths.artifactsDir path is not defined in the config file, the default path of ./goblet/artifacts will be used, relative to the repositories root.
If a folder does not exist at paths.artifactsDir path of the config, one will be automatically created.

Test Reports

The GobletQA Platform generates detailed test reports that document the results of test executions. These reports provide a comprehensive overview of the tests that were performed, including the test outcomes (pass/fail), any errors or failures encountered, and relevant metrics and statistics. Test reports are essential for understanding the test results, tracking progress, and identifying areas that require attention or further investigation.

Code Coverage Reports

Code coverage reports provide information about the extent to which your code is covered by tests. The GobletQA Platform integrates with code coverage analysis tools to generate reports that highlight which parts of your codebase were executed during the testing process. These reports help you assess the effectiveness of your test suite and identify areas of your code that may require additional testing.

Automation Logs

During the execution of automation workflows, the GobletQA Platform generates detailed logs that capture the steps performed, any actions taken, and the corresponding outcomes. These logs provide a chronological record of the automation process, allowing you to trace the execution flow and investigate any issues or unexpected behavior. Automation logs are valuable for troubleshooting and debugging purposes.

Screenshots and Videos

The GobletQA Platform allows you to capture screenshots or record videos of the test execution or automation process. Screenshots are useful for visually documenting the state of the application at specific points in time, capturing potential UI issues or anomalies. Videos provide a more comprehensive recording of the entire test or automation workflow, enabling you to replay and review the execution for analysis or debugging purposes.

Playwright Traces

Because the platform uses Playwright for browser automaion, it can also take advantage of it's trace-viewer (opens in a new tab) features. When enabled, all traces are automatically saved to the path defined paths.artifactsDir in the goblet.config file.

Please see recording-a-trace (opens in a new tab) in the Playwright documentaion for more information

Custom Artifacts

Depending on your specific testing or automation requirements, you may generate custom artifacts as part of your workflows. These can include log files, performance reports, network traffic captures, or any other files or documents that provide additional insights into the behavior or performance of your application. The GobletQA Platform supports the inclusion and management of these custom artifacts through the use of paths.artifactsDir directory defined in the Goblet Config file. To take advantage of this feature, any custom generated artifacts should be placed in that directory.

The GobletQA Platform facilitates the management and accessibility of artifacts by providing features such as artifact storage, retrieval, and organization. You can easily access and download artifacts generated during the testing and automation processes, share them with team members or stakeholders, or integrate them into your existing documentation or reporting workflows.

Artifacts play a crucial role in ensuring traceability, collaboration, and documentation throughout the testing and automation lifecycle. The GobletQA Platform empowers you to generate and utilize artifacts effectively, enabling better analysis, troubleshooting, and communication surrounding your testing and automation efforts.