Truth in Testing: The Blog Series

The idea of "truth in testing" has become a bit of a mantra here on the blog and throughout the network equipment testing industry. Our BreakingPoint Labs team is constantly introducing new application protocols and security strikes, which continue our push for realistic testing. Additionally, this team consistently shares tips and tools on how to bring more truth into your testing. A great example was the recent white paper and code examples put together by Dustin D. Trammell and Todd Manning showing you how to simulate DDoS attack scenarios.

Our team views truth in testing as having a few specific criteria:

1. Stateful blended application traffic
2. Realistic bandwidth and throughput abilities
3. Live security strikes
4. Real-time and in-depth reporting
5. Ability to share information easily throughout your team and across tests

We are certain there are more and I'd be interested in hearing what you think encompasses truth in testing. We will share additional thoughts as we discuss the topic more, perhaps we can create a community-wide definition around truth in testing.

Over the next few weeks our team at BreakingPoint Labs will be sharing with you the latest in testing functionality and tips to bring a higher level of truth into your testing scenarios. All of this information will settle around the need for more realistic testing that ultimately helps create better performing and more secure network equipment.

First up in the series will be Dustin, writing about the generation of realistic Syslog traffic. Enjoy the posts and let us know what you think.