-
Notifications
You must be signed in to change notification settings - Fork 2
[joss] Run automated tests with GH Actions? #11
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
Comments
It's not only useful to show that the commits & code are being tested, but also to show users & devs how to run the tests in an automated way. I followed the README instructions to run the tests, for instance, and it displayed the browser windows for me to close, and then to proceed. I tried |
Another advantage of running in an automated way: I ran the backend tests, and one is failing for me:
Now I have no way of knowing if there's something wrong on my code, if maybe it's trying to access a port bound by the running Docker, or if it's just because I am using the latest code 🙂 |
Hi Bruno, thank you for the detailed feedback.
GH actions is indeed only building the PDF at the moment. As demonstrated with the issues you ran into, it might indeed be useful to add this to the repository. I will see whether I can implement it. I do think the review process can continue without the automatic testing through GH actions?
Yes sorry about this. We placed all environment variables into a .env file, Docker dynamically creates a TypeScript file with some variables that the front-end needs from this .env file. Since tests are not running through Docker this lead to some issues. I have created a file with a dummy variable, this is sufficient for the front-end tests to run (the tests do not depend on this variable for their correctness so there shouldn't be any issues). If you now follow the instructions in the readme the frontend tests will run. After they have completed a browser window will open showing how many have passed and failed (pass/fail rate should also display in your command prompt).
Indeed a bit sloppy on our part, sorry for this. I have resolved the issue. |
Hi @JarlJansen123 , @muctadir , I'm going through the review checklist for the JOSS paper again today. Confirmed two items had been fixed.
I had a look at the latest GH Actions on this repo, and also at the files under Could you provide some more information on how this has been addressed, please? Thank you! |
Actually, I believe this is the last point pending in my review now 👍 fixed once we have automated tests that can be executed by readers/users, and that are preferably being run automatically in a CICD pipeline with the code. Cheers. |
Hi, so in the readme.md there is a detailed description on how to run the tests manually, so automated tests can be executed by readers/users as far as I know. They are currently not automatically executed by a pipeline, but as far as I understand this is not necessary for JOSS submission. Please let me know if anything is unclear or missing. |
I will try to execute the tests from the readme.
Correct. You must provide automated tests but they do not need to run in gh actions. Note, however, that there is a distinction between a Good and an OK approach to pass the review. https://joss.readthedocs.io/en/latest/review_criteria.html#tests
I thought since you have gh actions already, hooking up ng and pytest there would be pretty simple. But if you prefer to keep tests executed manually I think that's Ok too. If the tests pass on my environment I will check that final item off the review list, and end my review with a note about the tests being manually executed and not with every commit or release (which is Ok to pass the review but I believe it should be made clear to users/readers in the review issue). Cheers Bruno |
Hi,
Related to openjournals/joss-reviews#5135, the item
Looks like GH Actions is only building the PDF at the moment? Any plans to add tests to the frontend and to the backend, and run them automatically on GH Actions?
The text was updated successfully, but these errors were encountered: