@loafyyy added a GitHub workflow, test-phen2gene.yml, that runs some end-to-end tests whenever someone makes a PR to master or pushes to master. The workflow is run on an Ubuntu VM with Miniconda and Python 3.6 hosted by GitHub, and it just goes through the steps in the README to install and setup up Phen2Gene. Then it runs the end-to-end tests using pytest; the tests just compare the actual output of Phen2Gene to the expected output (what she got when running it today) when running some of the examples listed on the README. She also added some shields to the README to make it look more legit. @MenggeZhao You may want to write some unit tests at some point in the test directory.
If any asserts fail in test_e2e.py you get a GitHub Actions failure and the build badge in the README will show that it failed. Code coverage badge from Codecov.io (not sure how accurate it is though).
Sorry about the confusion with previous PRs, was to clean code history.
@loafyyy added a GitHub workflow, test-phen2gene.yml, that runs some end-to-end tests whenever someone makes a PR to master or pushes to master. The workflow is run on an Ubuntu VM with Miniconda and Python 3.6 hosted by GitHub, and it just goes through the steps in the README to install and setup up Phen2Gene. Then it runs the end-to-end tests using pytest; the tests just compare the actual output of Phen2Gene to the expected output (what she got when running it today) when running some of the examples listed on the README. She also added some shields to the README to make it look more legit. @MenggeZhao You may want to write some unit tests at some point in the test directory. If any asserts fail in test_e2e.py you get a GitHub Actions failure and the build badge in the README will show that it failed. Code coverage badge from Codecov.io (not sure how accurate it is though). Sorry about the confusion with previous PRs, was to clean code history.