Always document changes; repeatability is important, and full documentation will help testing go more smoothly in the future.
After testing is complete, compile your results and present them. We find it helpful to build a template of features or questions that crop up during testing, and to answer each question for each product. This ensures that we can compare both hard and soft test results per SUT.
Even if you're testing just one system, maintaining a template helps organize results and assessments as you progress.
Here's a sample test plan we used for a recent review of NIP devices (see "Inside the NIP Hype War"):
NIP Test Plan
Discover the benefits of scalable backbone and network services for application and cloud providers.
Network automation is gaining momentum. Here's how you can drive this powerful technology to its full potential.
Subsea cable alternatives can provide a level of comfort for those concerned about disruptions. Realistically, they will continue to play a small, but critical role in the short term.
