Create testing container
License and Copyright Notice
By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).
What is the goal or the problem, and why is it important?
- The goal of this issue is to create a container which holds all of our tests.
- This container can be run from the command line, and will run all of it's tests on our frontend and backend.
How are you going to acheive the goal or solve the problem?
- Some research needs to go into creating an additional docker container
- Some research needs to go into using a service to run/ automate tests
- Some research needs to go into getting these tests to run every time a commit is pushed up to the remote. That way, we can't add code that breaks previous functionality.
What will be produced as a result of this effort and where will it live on GitLab?
- As a result of this effort, another testing docker file will need to be created. I do not currently know where it will live on gitlab. Changes to the package and package-lock are likely.
Give a justification of weight or due date.
- This should be a 6 point ticket. It has a research element, and a few parts including
- finding where the code should live
- finding the proper package to use as a testing service
- finding out how to get that to work in a container
- finding how to get that whole thing to run atomically with gitlab
Who will do it, and what will they do?
- @mm413 will be responsible for this issue. He will create the new container, and update the related documentation.
What was the outcome?
- testing location was made in the frontend with placeholder test
- testing location was made in the backend with placeholder test
- testing packages were added to the npm package for testing (mocha and other small ones)
- testing (and linting) are now both jobs on the pipeline, and happen automatically with pushes. -- this was made possible through changes to gitlab ci
Template Version 1.0.0
Edited by Mark Meade