Machine Data Is Everywhere: Use It for Testing!
As more applications are hosted on servers, they produce immense quantities of logging data. Quality engineers should verify that apps are producing log data that is existent, correct, consumable, and complete. Otherwise, apps in production are not easily monitored, have issues that are difficult to detect, and cannot be corrected quickly. Tom Chavez presents the four steps that quality engineers should include in every test plan for apps that produce log output or other machine data. First, test that the data is being created. Second, ensure that the entries are correctly formatted and complete. Third, make sure the data can be consumed by your company’s log analysis tools. And fourth, verify that the app will create all possible log entries from the test data that is supplied. Join Tom as he presents demos including free tools. Learn the steps you need to include in your test plans so your team’s apps not only function but also can be monitored and understood from their machine data when running in production.
Upcoming Events
Apr 28 |
STAREAST Software Testing Conference in Orlando & Online |
Jun 02 |
Agile + DevOps West The Latest in Agile and DevOps |
Sep 22 |
STARWEST Software Testing Conference in Anaheim & Online |
Recommended Web Seminars
On Demand | Building Confidence in Your Automation |
On Demand | Leveraging Open Source Tools for DevSecOps |
On Demand | Five Reasons Why Agile Isn't Working |
On Demand | Building a Stellar Team |
On Demand | Agile Transformation Best Practices |