RE: Errors during net-snmp 5.2.x tests not recognized

This is a discussion on RE: Errors during net-snmp 5.2.x tests not recognized within the SNMP Coders forums, part of the Networking and Network Related category; Johannes Schmidt-Fischer wrote: > >I'd vote for a separate probably optional test block which tests the > &...


Go Back   Usenet Forums > Networking and Network Related > SNMP Coders

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 08-23-2005
Dave Shield
 
Posts: n/a
Default RE: Errors during net-snmp 5.2.x tests not recognized

Johannes Schmidt-Fischer wrote:
> >I'd vote for a separate probably optional test block which tests the
> >availability of most (or all) mib-II variables and maybe also other MIB
> >variables (like the host MIB). This test block should in no case stop
> >the build process, but it could become part of the delivery process as
> >it is the case with the configuration summary that can be downloaded
> >from the net-snmp files section.

>
> >This way everyone can inform himself which mib variables are supported
> >for a certain platform and which aren't available due to any reason (not
> >implemented, not available for that platform etc.).


That sounds sensible to me.
I'm not sure I'd include it as part of the default build,
but it would certainly be appropriate as a separate make target.
Something like:

make testMIBsupport

which would report which MIB groups were (or weren't) supported
by that agent.


Bruce Shaw wrote:
> I'm not sure what you're asking for.
>
> I've already got a HOST-RESOURCES-MIB test in CVS Main and 5.1.


The difference between your HostRes tests and the RFC1213 tests
we've been discussing is that:

a) You are testing a small core group of MIB objects (of one!)
that are guaranteed to be supported on any architecture.

b) Your test checks to see whether the relevant group is
configured into the agent before running the test.

So "make test" will either report "PASS" or "SKIP" (depending
on how the agent was configured). It won't report "FAIL" unless
there actually *is* a bug somewhere.

The problem with the RFC1213 tests is that they blindly assume
that all the objects being tested will be available (on every
architecture). So a missing object (which is *known* to be
missing on a particular system) will cause the test run to fail.
That rather undermines the point of having a test suite.


I'd still raise the question of exactly what the T152hostuptime
test is actually testing (and similarly for most of the other
scripts in that suite), but it is at least "well behaved".



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
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders
Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 10:18 PM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0