-
Notifications
You must be signed in to change notification settings - Fork 103
Description
This issue is pick up on a bug from a previous hackhour . This Bug is also referring to this original issue written
Some more context: so we wanted to add a GitHub actions CI jest test for push and pull in our repo. However, we need to fix the error before merging that workflow. So, during the hackathon we will work on fixing the error and then merge the workflow.
Before you open an issue, please check if a similar issue already exists or has been closed before.
Expected Behavior
- CI Node.js test check in Create ci-tests.yml #1062 should not be failing
Current Behavior
- CI Node.js test check in Create ci-tests.yml #1062 is currently failing
Possible Solution
Fix the below error
FAIL server/tests/integration/axios-cache-interceptor.test.js (12.247 s)
● test Axios cache invalidation option › tests cache invalidation
expect(received).toBe(expected) // Object.is equality
Expected: false
Received: true
49 | const res3 = await req3
50 | // assertions: the second request is expected not to be cached, due to the ttl
> 51 | expect(res3.cached).toBe(false)
| ^
52 | }, 70000)
53 | })
54 |
at Object.toBe (server/__tests__/integration/axios-cache-interceptor.test.js:51:25)
Steps to Reproduce
- CI Node.js test check will fail on every commit to PR Create ci-tests.yml #1062
Context (Environment)
We are trying to add jest testing workflow to our repo so when we merge a PR we are confident that no tests fail if the check passes. This is useful because we don't want to merge in any breaking code.
Detailed Description
Possible Implementation
Labels
Please add the following labels dependent on the bug type
- Security Bug: Creates an issue that can cause harm
- Vulnerability Bug: Creates an issue to update a supply chain dependency error
- Functional Bug: something that is causing a crash of the app