test management

combination lock What Testers Need to Know about Security

Every single tester should keep an eye on what security vulnerabilities might be plaguing their testing, but speaking in an interview at STARWEST 2016, Jeff Payne, the CEO and founder of Coveros, explained why you need to put a focus on security very early in the process.

Josiah Renaudin's picture
Josiah Renaudin
exploding lightbulb Naive Innovation in Software Testing

The idea behind naive innovation is that a person with the right mindset and passion for a certain area is a great candidate for innovation, even without having the same subject matter expertise as a domain expert. Rajini Padmanaban looks at naive innovation in software testing.

Rajini  Padmanaban's picture
Rajini Padmanaban
Chalkboard with 1+1=2 The Value of Testing Simply

People obsess over the number of tests and test coverage, but tests that cover more code don’t always improve quality. Some tests have low value and thus, implicitly, high cost. Simple tests may not seem impressive at first glance. But the goal of testing is to ensure quality, and simple tests can be very valuable.

Steve Berczuk's picture
Steve Berczuk
Agile Testers Shouldn’t Be Enablers

Testing has often been seen as the final stage of creating an application. Since we weren’t shifting testing left as much as we do today, a great deal of work was thrown on the testing team at the very end of an exhausting project cycle. But testers shouldn’t be seen as the last line of defense.

Josiah Renaudin's picture
Josiah Renaudin
world clocks The Importance of Testing in Conjunction

While it is important to have distinction between testing efforts to maintain specialization and core subject matter expertise, having overlap in test efforts—testing in conjunction—is becoming a common practice.

Rajini  Padmanaban's picture
Rajini Padmanaban
team meeting Why Testers and Developers Don’t Have to Be on the Same Page

Since software development is highly subjective in nature, different thought processes and assumptions between development and testing teams can positively impact applications and lead to a more successful, well-rounded product. It might not seem like it at the time, but there’s value to dissonance.

Josiah Renaudin's picture
Josiah Renaudin
Start here Where to Begin with Test Automation

Most test teams want to try automation for some tasks in order to be more efficient, but it can be daunting. If you are wondering where to start automating, the answer is usually as close to the code as you can possibly get. The farther you get from the code, the more you expose yourself to issues.

Justin Rohrman's picture
Justin Rohrman
Master test plan Reviving the Master Test Plan in the Age of Agile

In the competitive environment of delivering software more quickly, many teams have abandoned detailed test plans. Michael Sowers argues for bringing back the overarching master test plan—not to have more documentation, but for the questions, creative test designs, and critical thinking the planning brings.

Michael Sowers's picture
Michael Sowers