Community
Participate
Working Groups
Our unit test system is set up so by default runs all tests. But, its also possible to name specific test suites during invocation to run only those suites. In past day or so, I "carried this forward" to work that same way with current scripts we use in Hudson. This was relatively easy to do making use of existing "args" variable and existing logic to "read remainder of line" into args. That worked, but today discoved, when going by the want to use the default "all", that the test.propererties for windows had args=/c win7-6.0_consolelog.txt Thus "messing up" the logic ... eventually causing a failure saying the test targets of "/c" and "win7-6.0_consolelog.txt" could not be found. The other platforms had args= (nothing) in their test.properties file. For windows, this /c win7-6.0_consolelog.txt was not even being used, in existing setup (as far as I can tell) ... so ... just removed it and made it also args= But ... encountering all this, make me think it would be best to use an explicit arguments, such as -tests="list of tests suites", when a subset is desired. not sure what (else) this "args" was intended for ... but ... usually better to be explicit with arguments instead of having implicit assumptions about "remainder of command line".
