`testFailed` does not work with detox@20
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- mobile-dev, testing-qa
Research direction
Start with the afterEach snippet in the issue and check how the example application integrates Detox 20 and exposes test-failure state. Reproduce the ReferenceError, then verify that the failed-test screenshot behavior works and the E2E tests still pass.
Written by the indexing model from the issue text.
Description
Thanks for the example application.
Currently I am facing the error ReferenceError: testFailed is not defined while running my tests
If I comment testFailed flag in the below code everything is working fine but missing the feature of only taking screenshot for failed test cases.
here is my code, please suggest how to solve this issue.
ReferenceError: testFailed is not defined
1 |
2 | afterEach(async () => {
> 3 | if (testFailed) {
| ^
4 | await device.takeScreenshot('screenshot');
5 | }
6 | });
- Dominant language
- Java
- Stars
- 34
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from expo/eas-tests-example
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
expo/eas-tests-example#10 ·
All issues in expo/eas-tests-example
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
apache/arrow-java#1311 ·
Maintainers usually reply within 2 days
-
bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
IBM/networking-java-sdk#204 ·