Filter: behavior of e2e test differs from true http request

I’m submitting a…

[ ] Regression 
[x ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

I register a global filter SequelizeValidatorFilter

import { ExceptionFilter, Catch, HttpStatus } from '@nestjs/common'
import { Sequelize } from 'sequelize-typescript'

@Catch(Sequelize.ValidationError)
export class SequelizeValidatorFilter implements ExceptionFilter {
    catch(exception: typeof Sequelize.ValidationError, response: any) {
        response
            .status(HttpStatus.CONFLICT)
            .json({
                error: exception.message,
                message: exception.errors.map(error => error.message),
            })
    }
}

then, I ran the application and used Swagger UI sent a true request, here is the result

{
  "error": "Validation error",
  "message": [
    "username must be unique"
  ]
}

and statusCode is 409

however, when I use npm run test:e2e, the statusCode is 500, the e2e-spec.ts:

it('Post /user conflict', () => {
        return request(app.getHttpServer())
            .post('/user')
            .send({
                username: 'Hex',
                email: '[e-mail]',
                name: 'Hex,
                password: '123456'
            })
            .expect(HttpStatus.CONFLICT)
            .expect(res => {
                const resp = res.body as ValidationErrorDto
                expect(resp.error).toBe('Validation error')
                expect(resp.message).toHaveLength(1)
            })
    })
})

the console:

expected 409 "Conflict", got 500 "Internal Server Error"

      at Test.Object.<anonymous>.Test._assertStatus (../node_modules/supertest/lib/test.js:266:12)
      at Test.Object.<anonymous>.Test._assertFunction (../node_modules/supertest/lib/test.js:281:11)
      at Test.Object.<anonymous>.Test.assert (../node_modules/supertest/lib/test.js:171:18)
      at Server.assert (../node_modules/supertest/lib/test.js:131:12)
      at Object.onceWrapper (../events.js:254:19)
      at Server.emit (../events.js:159:13)
      at emitCloseNT (../net.js:1689:8)
      at process._tickCallback (../internal/process/next_tick.js:152:19)

Environment

Nest version: 4.6.6
    
Jest version: 21.1.10,
> ts-jest: 21.2.4
 
For Tooling issues:
- Typescript version: 2.7.2
- Node version: 9.3.0
- Platform:  MacOS 10.13.4

Others:

[kamilmysliwiec]

Therefore you need to do the same inside your tests. Once you created a Nest instance using createNestApplication(), you have to bind appropriate filters.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.