Looking at replacing ATF/Kyua (in a limited fashion) with Google Test/shunit2

[Ngie Cooper (yaneurabeya)]

> On Jan 17, 2017, at 15:11, Alan Somers <asomers at freebsd.org> wrote:

…

> Before you get to far, you should ask yourself how much test case
> isolation you desire.  Googletest is great, but I think it'll be hard
> to get the strong isolation between testcases provided by ATF.
> Perhaps it'll be find if GoogleTest tests provide no per-testcase
> isolation; most C/C++ programmers don't expect it anyway.  But many of
> FreeBSD's atf-sh tests depend on it.

A lot of programmers don’t desire this at all, until they realize how their tests might be affected by system state if/when there are files/directories/other inputs infecting their results on the test system.

> Also, how are you planning to hook up GoogleTest and shunit2 to Kyua?

It’s early enough on in the process of trying to figure out how things work that I cannot definitively say, other than it may end up being something like:

kyua <-> googletest <-> atf

or something more like:

kyua <-> googletest_atf_compat

and just mimic the output of ATF, while hiding the implementation details of the test suites. If that turns out to be a pain, then I’ll just implement another hook into kyua for googletest which will implement the features we need, potentially as a patch to the port, because “legal reasons” (contributor agreements shouldn’t be impediments, but because I signed an individual CLA vs corporate CLA and they aren’t equivalent) are blocking me from giving code back to Google as a Dell EMC employee (things may change, but when I fought for a corporate CLA, it got stuck in the bureaucratic quagmire that is my company’s legal/business dept).

Thanks,
-Ngie
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freebsd.org/pipermail/freebsd-testing/attachments/20170117/7d93bcd0/attachment.sig>