Skip to content
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

Move to testing mainly via BATS #9

Open
5 of 12 tasks
CasperWA opened this issue Mar 12, 2020 · 0 comments
Open
5 of 12 tasks

Move to testing mainly via BATS #9

CasperWA opened this issue Mar 12, 2020 · 0 comments
Labels
CI Continuous Integration - Issues with testing the action tests Test-related issue or PR

Comments

@CasperWA
Copy link
Member

CasperWA commented Mar 12, 2020

Related to discussion in #3, particularly from this comment onwards.

Essentially we should explicitly test the action (mainly entrypoint.sh) does the expected thing, not that the server from optimade-python-tools can be validated.
This possibly involves changing the current CI tests to not setup a local server, but instead test public URLs, and expand the BATS tests to include all input parameters.

Input parameters to test in BATS:

@CasperWA CasperWA added the CI Continuous Integration - Issues with testing the action label Mar 12, 2020
@CasperWA CasperWA added the tests Test-related issue or PR label Sep 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous Integration - Issues with testing the action tests Test-related issue or PR
Projects
None yet
Development

No branches or pull requests

1 participant