Make test success a requirement for Jenkin deployment (from 1933)

[gigamorph]

Problem Description: We need a way to make a success of all tests a requirement for the Jenkins build. The developers can individually make the test a git commit hook but there's no way to enforce it.

Expected Behavior/Solution: Describe the solution to the problem or the expected behavior.

Requirements:

• Include yarn test --watchAll=false in Docker build, and let the Jenkins build process fail if the test fails.

Needed for promotion: If an item on the list is not needed, it should be crossed off but not removed.

• [ ] Wireframe/Mockup - Mike
• [ ] Committee discussions - Sarah
• [ ] Feasibility/Team discussion - Sarah
• [ ] Backend requirements - TBD
• [ ] Frontend requirements- TBD
• [ ] Questions
• List of questions for discussions. Answers should be documented within the issue.

UAT/LUX Examples:

• NA as it is through Jenkins.

Dependencies/Blocks: N/A

Related Github Issues: N/A

Related links: N/A

Wireframe/Mockup: N/A

[roamye]

Comments from old tix (https://git.yale.edu/lux-its/lux-web/issues/1933)

@gigamorph "Docker update problem was solved and chromium issue turned out to be a non-issue. We can go ahead once the work on frontend tests is done and no failure state is achieved."

[roamye]

@gigamorph do we need a front end ticket for the frontend tests that need to be done?

cc: @prowns

[roamye]

@gigamorph - is there any information that can be added above to move this to prioritization review?

bringing to ticket forming 9/10 to discuss.

tf 9/10: -- our internal test suites for the code. @kamerynB to discuss with @gigamorph. please feel free to repurpose the issue.

[roamye]

dev mtg 10/21:

• this issue is fully formed and untestable as it is through Jenkins. (screenshots can be provided if needed)
• no further discussion is needed.

moving to prioritization review.