There are more than one contributors to the code now, it runs on at least 2 platforms, and is being open-sourced. Let's write some tests!
Upping the priority, as I'm starting to contribute to the code, and I really miss the tests.
As a general rule, I personally like to ensure 100% line and branch coverage for Python, simply because it's not type-safe and silly typos tend to crash otherwise parseable code. But any tests are better than no tests.
This work will happen after Franky is open-sourced, and I'm happy to contribute!
I'm grabbing the bug for the time being, as I plan to start writing tests very soon.
In addition, running unit tests will require custom Python packages like coverage, and other packages Franky depends on. Rather than expecting each developer to install those on a system, I want the repo to use a hermetic virtualenv. We have a new tool called 'vpython' just for that.
The plan is to add vpython to depot_tools (which is required to work with the repo anyway), and implement all the developer workflow assuming vpython is on the path.
Comment 1 by sergeybe...@chromium.org
, Apr 6 2017