The main (and probably major) consumer of ATF at this point is the NetBSD test suite. We must ensure that the test results delivered by Kyua do not deviate from those of ATF. I am aware that at the problem this is not true, so this issue is intended to fix all the problems in this area.
We need to implement integration tests and add this particular case to
them. The unit tests we currently have are very good know but they will
be brittle during future refactorings.
Some integration tests for the cli-side of the tool have been added. While thinking of adding more integration tests for things like isolation and requirements checking, I realized it is a waste of time to do it now: such things are already very well-tested in their corresponding module-specific tests, and duplicating the tests (in a slower language: sh) will not help much.
I have just run the recent test suite from NetBSD both as root and as a regular user and the results Kyua yields are the same as those produced by atf-run. Modulo regressions later on, this ticket provides no additional value and can be closed. We now have all the required functionality implemented!
From jmmv@google.com on March 19, 2011 10:54:48
The main (and probably major) consumer of ATF at this point is the NetBSD test suite. We must ensure that the test results delivered by Kyua do not deviate from those of ATF. I am aware that at the problem this is not true, so this issue is intended to fix all the problems in this area.
Original issue: http://code.google.com/p/kyua/issues/detail?id=16
The text was updated successfully, but these errors were encountered: