I have a NestJs project and I wrote a few e2e tests that send a request to my controllers and check for a response. They run just fine while I have nest running in my localhost. They look like this:
describe('Health Check', () =>
{ it('should ping', () => {
return request(app)
.get('/health')
.expect(({ body }) => {
expect(body.code).toEqual(200);
expect(body.data).toEqual('Active!');
})
});
})
however, when I try to add a bitbucket pipeline, it always fails when trying to run the e2e tests. It gives this error: connect ECONNREFUSED 127.0.0.1:8080 which seems to mean that it's trying to connect to a localhost.
What do I need to do in order to get these kind of tests to run? Is it something I need to do with the pipeline or something I should configure in my NestJs app?
My pipeline file currently looks like this:
image: node:10.15.3
pipelines: default:
- step:
caches:
- node
script:
- npm install
- npm run prestart:prod
- npm test
Hi @Virginia Elizabeth Gil Vásquez
I've tried running few example projects from https://github.com/nestjs/nest/tree/master/sample in Pipelines and they all work just fine. This makes me think that it may be some specific configuration related to your project that requires checking out. Firstly Pipelines runs inside Docker so I would make sure that your project runs inside Docker in your local environment. You would likely encounter the same error and then it's not specific to Pipelines. If that's the case I would try to search for the specific error in relation to NestJS like https://stackoverflow.com/questions/35199384/node-js-error-connect-econnrefused-response-from-server/35203694
If your project works well inside of Docker but still fails in Pipelines reach out to our support for help https://support.atlassian.com/bitbucket-cloud/
Thanks,
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.