Investigate the failure with CriticalNotificationsTest (V7)
Open
Nobody has claimed this yet.
v7
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
currently they are muted in the Teamcity
it looks the failure comes even before the screenshot comparison.
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 TeamCity build linked in the issue and inspect the failure for CriticalNotificationsTest (V7). Determine why it fails before screenshot comparison; the work is done when the test no longer fails at that earlier stage and its result can be verified in the build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100