Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance Troubleshooting for Discrepancies in E2E Test Results Between Local and CI Environments #30766

Open
victoralfaro-dotcms opened this issue Nov 25, 2024 · 0 comments

Comments

@victoralfaro-dotcms
Copy link
Contributor

victoralfaro-dotcms commented Nov 25, 2024

User Story

As a software engineer, I want to help QA troubleshoot the cause of having different results in local and CI environments when it comes to E2E tests.

Acceptance Criteria

  • A clear comparison mechanism is established between local and CI environments for E2E tests.
  • Logs or diagnostic tools are integrated to identify discrepancies in test results.
  • A process is documented for QA to analyze and address these discrepancies efficiently.

dotCMS Version

master

Proposed Objective

Quality Assurance

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

to_define

Assumptions & Initiation Needs

  • Access to both local and CI environment configurations and logs.
  • Tools or frameworks currently used for E2E tests are compatible with added diagnostic enhancements.

Quality Assurance Notes & Workarounds

  • Use existing debugging tools and configurations as a baseline.
  • If discrepancies are identified, ensure a fallback process is documented.

Sub-Tasks & Estimates

  • Analyze and document differences in local vs. CI environments (3h)
  • Develop or integrate a tool to identify discrepancies in test results (5h)
  • Create a guide for QA to troubleshoot using the new mechanism (2h)
  • Test and validate the solution in both environments (4h)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

No branches or pull requests

1 participant