Hi Samuli, […]
> I think the first step would be to identify the places where unit tests could > be implemented easily (if any), and where they would do most good. If > something falls to both of these categories then writing a unit test there > would probably make sense. The first candidate would be the U2F integration that I’d like to write. A proven strategy for starting unit testing is to write tests for all new features. This way the up-front cost is reduced to the invest for “the first test”. > > Then there's the other codebase (3.x) which, when publicly released, might be > a good/better candidate for writing unit tests. Please forgive my ignorance: Is this code base already a thing, and what is the time scale we are looking at (regarding “V3”)? > > If we end up writing unit tests, I too would prefer the Git submodule > approach. Great :-) Jens > > -- > Samuli Seppänen > Community Manager > OpenVPN Technologies, Inc > > irc freenode net: mattock
