Conversation
This commit introduces a tox.ini file which mimiks the behaviour of the Makefile which is used for verifying and testing the cram project. Attention: The build and install step is not explicitly added, because tox already takes care about this by default. See also: https://tox.wiki/en/latest/index.html For now tox just will simplify the local and the CI multi environment test execution. In case the Makefile path will be removed in the future, the tox.ini could be improved to more cleanly seperate different concerns like: linting, coverage, integratin testing, unit testing etc.
Nicoretti
changed the title
|
Is it still possible to use Travis for free? My interaction with their support team leads me to think not. Is there another service that could be used for builds? |
|
Maybe GitHub Actions would suffice?: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python |
|
Hi @Brodie, I just checked, seems you are right. It looks like that you have some free tokens for oss repos, but generally the |
|
If you are interested in having it run with GitHub Action(s) I can look into it tomorrow |
|
@Brodie migrated a basic version of the test setup to GitHub, with a couple of small adjustments in the setup (see commits above) it seems to work just fine (https://github.com/Nicoretti/cram/actions/runs/1629899894) |
by providing a python based implementation of the md5 hasing tool, it will incrase the platform independence of cram tets using it.
|
I suggest switching to GitHub actions, which allows running tests across Linux, MacOS and Windows. |
3 participants
Hi Brodie,
I hope you are doing well.
I am a huge fan of cram and recently I was digging more into it. I feel there is still some more potential
in cram (Don't get me wrong, the current state is already great!).
First thing I usually do when I pickup a project, is try to getting it to build and get the tests running.
While doing this for cram I figured, the testing/verification could be simplified by using tox.
For example the test matrix python-version(s) + shell(s).
I think there would be even more potential in using tox, but it most likely would
break compatibility with the Makefile workflow.
When I created the PR I also realised there are a similar PRs #22 #23 which may be closed in case this one will make it in.
I also have dropped support/builds in travis CI for all unsupported python versions.
Let me know what you think about it.
Best
Nico