Open the GitHub Actions page

Oct 13, 2025 by orovajewels.com 105 views

Introduction

In the world of software development, End-to-End (E2E) tests play a crucial role in ensuring the quality and reliability of applications. However, sometimes, despite E2E tests passing, the summary page may still display errors, which can be misleading and confusing. In this article, we will delve into a real-world scenario where E2E tests passed, but the summary page showed errors, and provide a step-by-step guide on how to troubleshoot and resolve this issue.

Background

While working on a Pull Request (PR) #305, a developer noticed that the E2E tests had successfully passed. The test run was executed on the WooCommerce Square repository, and the results were available on the GitHub Actions page. However, upon reviewing the summary page, the developer was surprised to see that it displayed an error message, which was misleading and required further investigation.

Error Details

The error message displayed on the summary page was:

Unhandled error: HttpError: Label does not exist
No files were found with the provided path: tests/e2e/test-results/report. No artifacts will be uploaded

These error messages indicated that there was an issue with the labeling of the test run and the absence of test results files.

Steps to Reproduce

To reproduce this issue, follow these steps:

Open the GitHub Actions page: Navigate to the GitHub Actions page for the WooCommerce Square repository, specifically the test run with the ID 13812011592.
Observe the E2E test steps: Review the E2E test steps and note that all of them have completed successfully.
Check the summary page: Despite the successful E2E test steps, the summary page should display an error message, similar to the one mentioned above.

Screenshots

The following screenshot illustrates the issue:

Troubleshooting

To troubleshoot this issue, follow these steps:

Step 1: Review the Test Run Configuration

Review the test run configuration to ensure that the labeling and test results files are correctly configured.

Step 2: Check the Test Results Files

Verify that the test results files are present in the specified path (tests/e2e/test-results/report) and that they are correctly formatted.

Step 3: Investigate the Labeling Issue

Investigate the labeling issue by checking the GitHub Actions configuration and ensuring that the label is correctly defined and applied to the test run.

Step 4: Update the Test Run Configuration

Update the test run configuration to fix the labeling issue and ensure that the test results files are correctly uploaded.

Conclusion

In conclusion, despite E2E tests passing, the summary page may still display errors due to issues with labeling and test results files. By following the steps outlined in this article, developers can troubleshoot and resolve this issue, ensuring that the summary page accurately reflects the test results.

Best Practices

To avoid this issue in the future, follow these best practices:

Verify the test run configuration: Ensure that the labeling and test results files are correctly configured.
Check the test results files: Verify that the test results files are present and correctly formatted.
Investigate labeling issues: Check the GitHub Actions configuration and ensure that the label is correctly defined and applied to the test run.

Q: What are the common causes of E2E tests passing, but the summary page showing errors?

A: The common causes of E2E tests passing, but the summary page showing errors, include:

Labeling issues: Incorrect or missing labels can cause the summary page to display errors.
Test results files: Missing or incorrectly formatted test results files can prevent the summary page from accurately reflecting the test results.
GitHub Actions configuration: Incorrect or missing configuration in the GitHub Actions workflow can cause the summary page to display errors.

Q: How can I troubleshoot labeling issues?

A: To troubleshoot labeling issues, follow these steps:

Review the GitHub Actions configuration: Check the GitHub Actions configuration to ensure that the label is correctly defined and applied to the test run.
Verify the label: Ensure that the label is correctly applied to the test run and that it matches the expected label.
Check the test run configuration: Verify that the test run configuration is correctly set up to use the label.

Q: What are the common causes of missing or incorrectly formatted test results files?

A: The common causes of missing or incorrectly formatted test results files include:

Missing test results files: Test results files may be missing due to incorrect configuration or missing dependencies.
Incorrectly formatted test results files: Test results files may be incorrectly formatted due to incorrect configuration or missing dependencies.
Test results files not uploaded: Test results files may not be uploaded due to incorrect configuration or missing dependencies.

Q: How can I troubleshoot missing or incorrectly formatted test results files?

A: To troubleshoot missing or incorrectly formatted test results files, follow these steps:

Verify the test results files: Check that the test results files are present and correctly formatted.
Check the test run configuration: Verify that the test run configuration is correctly set up to upload the test results files.
Investigate dependencies: Check that all dependencies are correctly installed and configured.

Q: What are the best practices for avoiding E2E tests passing, but the summary page showing errors?

A: The best practices for avoiding E2E tests passing, but the summary page showing errors, include:

Verify the test run configuration: Ensure that the test run configuration is correctly set up to use the label and upload the test results files.
Check the test results files: Verify that the test results files are present and correctly formatted.
Investigate labeling issues: Check the GitHub Actions configuration and ensure that the label is correctly defined and applied to the test run.

Q: How can I ensure that my E2E tests are accurately reflected on the summary page?

A: To ensure that your E2E tests are accurately reflected on the summary page, follow these best practices:

Verify the test run configuration: Ensure that the test run configuration is correctly set up to use the label and upload the test results files.
Check the test results files: Verify that the test results files are present and correctly formatted.
Investigate labeling issues: Check the GitHub Actions configuration and ensure that the label is correctly defined and applied to the test run.

By following these best practices and troubleshooting steps, you can ensure that your E2E tests are accurately reflected on the summary page, providing a clear and accurate picture of the test results.