[chirp_devel] Using TOX to test on MS Windows

[Dan Smith]

> Yeah. I think I posted a comment after the change that
> "run_all_test.bat" is broken. I had to edit the batch file to get it
> to run.

Ah, okay, wanna send a patch for that in the meantime at least?

> So what is this TOX thing?

The tox tool is a thing that builds virtual environments for the purposes of running tests. It insulates the running tests from your actual system to a high degree, which means that tests should be a little easier to run in more places. It installs the packages that we need and properly “installs” chirp to run the tests. It’s a lot better for the build system, which means it should break less and require less maintenance from me.

Now, if you have tox installed, all you should need to do to run the tests is type “tox”. It’ll build the venvs for driver and style checks the first time and then run the tests. I also have made the driver tests fit into the standard python testing infrastructure so we can use the regular test runners. In the future, that will let me run them in parallel more easily, which will make it much quicker to get a test result.

On windows, try running this to install too:

  python -mpip install tox

Let’s see what Eric reports about what isn’t working to see if it’s something easy. Luckily, I was able to do all of the above without disturbing the regular way of running tests, so you can continue to do that until we sort it out.

—Dan