Tests returning an inconsistent number of results

Several test submissions here use a design where if the feature is not 
available they fail to run the rest of the testsuite (e.g. [1]). This is 
an antipattern because it makes it unnecessarily difficult to compare 
the results between builds; ideal tests should always return the same 
number of results.

Will anyone object if I patch the problematic tests and commit the fixes?


Received on Thursday, 13 September 2012 08:31:55 UTC