actions / actions/starter-workflows
### END-TO-END TESTS
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.1k
- Forks
- 7.3k
- PR merge metrics
- No merged PRs in 30d
Description
END-TO-END TESTS
- Testing started at: October 4th 2024, 7:07:18 pm
📦 Test Result Summary
- ✅ 26 passed
- ❌ 4 failed
- ⚠️ 0 flaked
- ⏩ 1 skipped
⌛ Duration: 7 minutes and 53 seconds
Overall Result: 👎 Some tests failed.
[Show/Hide] Test Result Details
| Test | Browser | Test Case | Tags | Result |
|---|---|---|---|---|
| 1 | chromium | Transition to ignored state and then back to connected state | ❌ | |
| 2 | chromium | Transition to not found state and then back to connected state | ➖ | |
| 3 | chromium | Toggle "Meshery Catalog Content" | ❌ | |
| 4 | firefox | Transition to not found state and then back to connected state | ❌ | |
| 5 | firefox | Toggle "Meshery Catalog Content" | ❌ |
Originally posted by @github-actions in https://github.com/meshery/meshery/pull/12271#issuecomment-2394409789
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the full report in the CI/CD pipeline and the originating Meshery pull request #12271. Review the four failed end-to-end cases across Chromium and Firefox, then rerun the relevant workflow. Done means the reported failures are resolved or clearly documented with a passing test result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100