spirent.com
Posts Tagged "network testing"

In the real world, how do most people create a test case? In most instances, they open the tester GUI, configure the test, debug the test, run the test, print the report, and are done. The question when we drill deeper is “Is this the most effective way for us to be performing our testing?” Let’s drill down into the problems this technique creates for organizations. Generally, many test engineers are given a test set which may include a full DUT or specific test ports on a shared DUT. The configuration of specific attributes of these ports such as routing/IP information, firewall rules, ALCs typically do not change unless they are specifically being tested. In the classic model, the user keeps rebuilding attributes of the test over and over again potentially building the same test hundreds of times.

Read full post 0 Comments
× Spirent.com uses cookies to enhance and streamline your experience. By continuing to browse our site, you are agreeing to the use of cookies.