Patrol

Reviewing Test Results in Patrol

Estimated reading: 2 minutes 89 views
Patrol Featured Image

When it comes to quality assurance, reviewing test results is crucial for identifying issues and ensuring the software performs as intended. In Patrol Testing, the process of debugging and logging plays a vital role in making this review effective. By understanding how to navigate and analyze your test results, you can significantly improve the quality of your applications and enhance your testing workflow.

Understanding Test Results in Patrol Testing

Before diving into the review process, it’s essential to understand what test results entail in Patrol Testing. Each test run generates results that provide insight into the application’s performance, including pass/fail status, error messages, and execution times. These results are the foundation for your debugging and logging strategies.

IOS Passed Results

Locating Patrol Test Results

The location of your test results depends on whether you’re testing on an iOS or Android device, and whether your project includes flavors for different environments. Here’s where you can find them:

After running tests on an iOS device, the results are stored in the .xcresult format. You can find them here below:

build/ios_results_**********.xcresult

For Android, the test results are stored in a specific directory under your project’s build folder. The default location is:build/app/reports/androidTests/connected/debug/However, if you're using flavors (such as different environments or configurations for development, staging, or production), the results will be found under the corresponding flavor's folder. For example, for a development flavor, the path will be:  build/app/reports/androidTests/connected/debug/flavors/development

These files contains detailed information about your test execution, including screenshots, performance data, and any errors encountered during the tests.

Analyzing Pass/Fail Metrics

Once you have the test results, start by analyzing the pass/fail metrics. 

IOS Test Passed & Failed Results
IOS Test Passed & Failed Results

Investigating Error Logs

The next step in your debugging process is to investigate the error logs generated during the tests. 

Reviewing Failed Test
Reviewing Failed Test

Comparing Results Against Expectations

After collecting and analyzing your logs, compare the actual test results against expected outcomes. This comparison helps identify discrepancies and informs your debugging process.

Reviewing Failed Test Recording

Conclusion

Reviewing test results in Patrol Testing is an essential skill for any quality assurance professional. By focusing on debugging and logging, you can streamline your testing process and ensure your applications meet the highest standards. Remember to collect, analyze, and document your test results effectively to enhance your testing practices.

Leave a Comment

Share this Doc

Reviewing Test Results in Patrol

Or copy link

CONTENTS
Review Your Cart
0
Add Coupon Code
Subtotal
Total Installment Payments
Bundle Discount