[NEW TEST] Automated E2E Testing about testing-nestjs HOT 6 CLOSED

I'll try to setup for my project and contribute once I figure it out.

from testing-nestjs.

@jmcdo29 Are we looking at including test coverage for the setup, or we're just looking at able to run the e2e test as starter?

from testing-nestjs.

As a start, just ensuring they run properly. Coverage can be updated later

from testing-nestjs.

Manage to get something working for my project here: https://github.com/malcolm-kee/dine-in/blob/master/.github/workflows/e2e-test.yaml

@jmcdo29 do you have any suggestion for the examples of the container-ized tests? Should we create separate example or we use existing sample by adding more configuration/code?

from testing-nestjs.

@malcolm-kee I kind of like using the existing samples, but if it is easier to create a separate sample, then let's go with that if it will still be extensible.

from testing-nestjs.

Thinking out loud on the E2E Testing example. @jmcdo29 If you have any idea to simplify it, that would be great!

2 Apps Will Be Created

• e2e-example-redis-publisher have a single REST endpoint, which when called will publish an event to redis
• e2e-example-redis-subscriber will listen to the event from redis and save the data in mongoDB. It also expose a single REST endpoint which can be called to retrieve the saved data.

Dockerfile on how to build each apps will be available in their respective folder.

A e2e-testing folder will be added for E2E test scripts

The endpoints of the request will be injected by environment variables.

A single docker-compose.yaml file in the project root

• The apps and the test scripts will be listed here. We'll let Docker Compose to figure out which apps to bring up when we docker-compose run in GitHub Actions.

from testing-nestjs.