Gitlab pipeline is not failing when Jest test case fail or throw error

Asked May 07 '20 at 19:02

Active May 09 '20 at 10:40

Viewed 792 times

I am using Jest for testing mu nodejs code an after commiting my code the pipeline runs and Jest test case is throwing error but pipeline is not failing. In test case it shows there are not expected results and so test case is failing but is not forcing the gitlab pipeline to fail. Any help?

  ✓  (10 ms)
  ✓ Test case for creating patient form testing (12 ms)

Test Suites: 1 passed, 1 total
Tests:       2 passed, 2 total
Snapshots:   0 total
Time:        3.174 s
Ran all test suites matching /patient_create.test.js/i.
(node:18484) UnhandledPromiseRejectionWarning: Error: expect(received).not.toBeDefined()

Received: [Error: expect(received).toBe(expected) // Object.is equality·
Expected: 200
Received: 404]```

edited May 09 '20 at 10:40

skyboyer

22,209
7
57
64

asked May 07 '20 at 19:02

jazeb007

1

were you able to solved this issue? – Diego Dec 09 '21 at 20:27
We have exactly the same issue, no clue what is going on, because locally tests are returning exit code 1. – Michał Hernas May 24 '22 at 12:54
Bro use Done as callback function and call done as `done();` at the end of text – jazeb007 May 26 '22 at 09:28

Gitlab pipeline is not failing when Jest test case fail or throw error

0 Answers0