> Due to what you wrote running the tests the way they're done at present > might be right or slightly wrong. They're right in that all OID's that > are expected to exist will be treated as failed in test 47 and that in > the tests 48 and 49 these OID's need not be handled as failed again.
Hmmmm.... In general, we've tended to regard each test as completely independent of the others. In principle, it'd be perfectly possible to run *just* tests 48 and 49 (without running 47 first) So I'd be reluctant to have the results of one test rely on a previous one. There's also the possibility of access control settings being such that certain objects are only available for one SNMP version, and not for others. > But they're wrong in that even for tests 48 and 49 the snmp daemon > doesn't return the expected value since those OID's don't exist. My main problem with these most recent tests (T16xrfc1213), is that I'm not clear what they are actually trying to test. The basic idea of the test suite is to tell whether the suite is behaving as expected, with each test checking one particular style of behaviour. That doesn't appear to be true of these last three tests, so it's unclear (to me at least), what constitutes a "successful" test. I'm wondering whether these might be better regarded as separate from the main "testing/tests" block. Dave ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
