testing

Designing good test cases can be described as an art. With test cases being written with a focus on business, testers should be part of the discovery and design phase of the project, and the business drivers should dictate test case design. But how can we ensure we are focusing on the user and bringing the biggest value possible in this phase? Larissa Rosochansky will describe what design thinking is, how it relates to the testing methodology, and how to use it in the design phase of your project. She will also show you how to better frame the business drivers and select the persona and most important exercises from a wide range of possibilities. After this introduction, Larissa will demonstrate how to apply the exercises, create the agenda for a design thinking workshop, select the team to ensure you have a diverse and multidisciplinary group, and document the results.

A test is no better than the data that drives it. Fuzz testing is a great way to find buggy, exploitable, or otherwise bad code – and if you’re working with a native application that operates on file input, it’s a solved problem. Grab AFL or some other all-in-one suite, hit go, and profit!

Many testers spend their time doing functional testing and don't come out of this cocoon. But software testing is all about discovering quality-related information to assist stakeholders in making informed decisions, and there are multiple ways to discover information in addition to functional testing. Here are six actions that will help you add more value to your projects.

Do you loathe regression? Do you tire of the repetitive tasks that are part of your product's lifecycle? If you do, then you might be lazy like Chris Loder. Since his Grade 4 teacher wrote “Chris is lazy” on his report card, it has become his way of life.