The Ocean Navigator is an online tool that is used to help visualise scientific research data. a users guide is available at https://dfo-ocean-navigator.github.io/Ocean-Navigator-Manual/ and the tool is live at
Issue: The front-end components of the Navigator must be manually tested when submitting new changes and prior to each release. This leads to missed bugs and broken functionality that goes unnoticed.
Why did you take this approach?
Automating the manual work and creating the test scripts to test.
Anything in particular that should be highlighted?
Command to run:
ubuntu@u2204-dev:~/onav-cloud/Ocean-Data-Map-Project/oceannavigator/frontend$ xvfb-run -a node name_of_script.js
Screenshot(s)
Checks
[x] I ran unit tests.
[x] I've tested the relevant changes from a user POV.
[x] I've formatted my Python code using black ..
Hint To run all python unit tests run the following command from the root repository directory:
Background
Issue: The front-end components of the Navigator must be manually tested when submitting new changes and prior to each release. This leads to missed bugs and broken functionality that goes unnoticed.
Why did you take this approach?
Automating the manual work and creating the test scripts to test.
Anything in particular that should be highlighted?
Command to run:
ubuntu@u2204-dev:~/onav-cloud/Ocean-Data-Map-Project/oceannavigator/frontend$ xvfb-run -a node name_of_script.js
Screenshot(s)
Checks
black ..Hint To run all python unit tests run the following command from the root repository directory: