Transcript for this video
Thank you for joining us to learn more about SilverCreek, the authoritative SNMP test suite.
This is the introduction to our three-part series on saving test results.
SilverCreek helps quality assurance engineers and testers find and fix bugs in their SNMP agent implementations by automatically executing a series of tests against the device under test, and recording result for each one.
With SilverCreek, we can automate our testing operation and focus on test results to pinpoint errors and to correct them.
Today we will explore the various mechanisms for saving test results.
There are three ways to save test results in SilverCreek: quicksave, the journal, and logging.
Let's take a quick look at each of these three methods.
This screenshot shows SilverCreek connected as an MD5 user to an SNMPv3 agent, as indicated at the top of the screen.
On the left side, notice we have selected and will execute the test suite for RFC 3412.
Our first method for saving the results of our test is “quick-save results.”
When the agent fails the test, here's what the quick-save results looks like.
Note the explanation for the agent's failure indicated by the red arrows.
Notice we're saving the config and setup information, the test number and description, the test result, and specific information about the error.
The second method for saving test results is logging.
When the agent fails a test, here's what the log file looks like.
The agent failed test number 188.8.131.52
Our third way of saving test results is the journal.
The journal file includes the SNMP operations that were performed.
The quick-save and logging do not.
We just showed you a quick overview of the differences in test output between the three methods of saving results in SilverCreek.
#1. Quick-save results
#2. Automatic logging of test results
and #3. The journal
To learn more about each method, please watch our three-part video series.
Want to Know More?
|Find more videos||How to buy||Contact an Expert|