[chirp_devel] Using TOX to test on MS Windows

[Jim Unroe]

On Sun, Dec 3, 2017 at 3:32 PM Eric A. Cottrell via chirp_devel
<chirp_devel at intrepid.danplanet.com> wrote:
>
> On 12/3/2017 12:29 PM, Dan Smith via chirp_devel wrote:
> >> 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
> > _______________________________________________
> Hello,
>
> I was using tox. I just tried run_all_test.bat which partly works. The
> run_all_test.bat problem is the "python tests\run_tests" line in the
> batch file will run the run_tests shell script instead of the
> run_tests.py file. If I enter python tests\run_tests.py on the command
> line it works.
>
> The problem with tox seems to be the zip file under .tox/dist is not
> named with the right version number and is missing most of the needed
> files. I have included the output/logs of running tox.
>
> 73 Eric

Dan,

Has this been looked into yet? I'm in to process of replacing my very
old CHIRP development computer. I've gone through the
DevelopersWin32Environment setup (writing down all additional steps
that are needed) and the only thing that doesn't work is the running
of the the tests using tox. I basically get the same error(s) that
Eric is getting according to the logs he provided.

Thanks,
Jim KC9HI