-
-
Notifications
You must be signed in to change notification settings - Fork 242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Integration Testing Pipeline #6
Labels
help wanted
Extra attention is needed
Comments
WonderPanda
added a commit
that referenced
this issue
Mar 26, 2019
WonderPanda
added a commit
that referenced
this issue
Mar 26, 2019
WonderPanda
added a commit
that referenced
this issue
Mar 26, 2019
WonderPanda
added a commit
that referenced
this issue
Mar 26, 2019
WonderPanda
added a commit
that referenced
this issue
Mar 27, 2019
WonderPanda
added a commit
that referenced
this issue
Mar 27, 2019
WonderPanda
added a commit
that referenced
this issue
Mar 27, 2019
WonderPanda
added a commit
that referenced
this issue
Mar 27, 2019
Merged
WonderPanda
added a commit
that referenced
this issue
Mar 27, 2019
WonderPanda
added a commit
that referenced
this issue
Mar 27, 2019
WonderPanda
added a commit
that referenced
this issue
Mar 27, 2019
WonderPanda
added a commit
that referenced
this issue
Mar 27, 2019
WonderPanda
added a commit
that referenced
this issue
Mar 28, 2019
WonderPanda
added a commit
that referenced
this issue
Mar 28, 2019
WonderPanda
added a commit
that referenced
this issue
Mar 28, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As we continue to build out packages that integrate with third party systems and frameworks (eg RabbitMQ, Caching, etc) it's important to ensure that a proper integration test pipeline exists that actually utilizes
nestjs-plus
packages in a real environment. This will help to ensure that functionality works as intended and that there are no regressions as the codebase evolves.This pipeline should be integrated with Docker Compose and be capable of running on Travis (or an equivalent CI) platform as part of normal builds and before new packages are released.
The text was updated successfully, but these errors were encountered: