On Wed, Jul 20, 2011 at 08:03:59AM +0000, David Holland wrote: > In just about every other test suite I've used (which includes some > very large ones with turing complete/scripted test harness programs > and other fancy stuff) there are test programs and test driver > scripts, but all the pieces have clearly defined and clearly separated > roles, and moreover are self-contained so they can be worked with > easily. > > ATF, however, insists on sticking its fingers and APIs in everywhere > ("intrusive") with the net result that everything becomes vastly more > complicated and working with individual tests directly becomes awkward > and difficult. One of the predictable consequences is not being able > to fold in preexisting test programs.
A lot of empty talk here. What is exactly your problem? Not being able to fold existing tests? That sounds like a bug. Indeed one ought to be able to #/bin/sh atf-run /usr/tests/lib/libc/gen/t_vis atf-run /usr/tests/include/sys/t_types > But apparently I'm not entitled to an opinion since I haven't been > working on the test suite. (I was at one point some time back, > actually, but got fed up with all the unnecessary hoops to jump > through and with how straightforward usability problems like PR 38746 > got ignored.) Feel free to roll your own and write the +2500 test cases, or get on with it and be constructive. - Jukka.