-
Notifications
You must be signed in to change notification settings - Fork 69
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
[NEW] simple automated testing #54
Conversation
Signed-off-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
Signed-off-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
Signed-off-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
Signed-off-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
Signed-off-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
Signed-off-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
Signed-off-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How will / can we hook in:
- unit tests?
- end to end tests?
Please add a few mock test placeholders in the right place so we can extend this. Thanks.
Adding a "push to production" on releases (not every commit/PR) would be extremely helpful to close the CI/CD loop. Please talk with @RonLek on the production server community.rocket.chat deployment details. |
@Sing-Li - about push to production, already on it. I have the server details on hand :) |
Signed-off-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
About hooking tests in ci, depending on the testing framework and workflow, I'll add them once they're added to the project, no need to add placeholders atm :) Right now there are two simple tests to make sure the pr won't break deployment once merged. |
Signed-off-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
Signed-off-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
Signed-off-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
Signed-off-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
* use js snippets to check health statuses * remove deployment section Signed-off-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
Signed-off-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
Signed-off-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
Signed-off-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
Signed-off-by: Debdut Chakraborty <debdut.chakraborty@rocket.chat>
OK. We're going to merge this. With the caveat that if the resource consumption proves to be too much or too expensive (for the simple ack that - yes, it builds) then we will disable it. Thanks @debdutdeb ! |
I'll probably add additional steps for deploying to a staging env later.