Related Content
 |
Testing Is Insurance, Not Assurance The Iowa Democratic Party used a mobile app to pull results from statewide precincts for the Iowa caucus. But the app was not properly tested or deployed, and it turned into a high-profile tech disaster. When deadlines loom, release testing is often what gets cut, but this situation shows why it's a crucial activity. |
|
 |
Why You Should Treat Tests as Products There's a case for treating some of your tests as products—project deliverables in their own right, created as a business investment. "Productizing" tests can show their value to management, but more importantly, it can help them contribute more effectively to the development lifecycle. Here are four steps to consider. |
|
 |
Defect Reporting: The Next Steps When a software defect is identified, best practices usually only pertain to the initial writing of the defect, not the tasks required to close it. Many factors can influence the tester's work. The solution is to add a “Next Steps” section that identifies the work remaining and the person responsible for completing it. |
|
 |
Softer Testing Skills to Focus On in 2020 Although technical skills will always be essential for testers, this should be the year we also have a collective responsibility to focus on two softer aspects: being realistic about goals for quality, and bringing back simplicity into the software engineering discipline. Here's how these goals can bring value in 2020. |
|
 |
2 Simple Ways to Improve Developer-Tester Relationships Supposedly there is a constant tension between developers and testers, like the roles of artist and art critic. They can’t exist without each other, and yet they can’t get along. It doesn't have to be that way! Here are two ways testers can reduce that feeling so that developers and testers can work better together. |
|
 |
The Curse of Rushed Requirements When development is outsourced, a documented baseline of expected functionality sets expectations for both the client and developer. Acknowledging that agile practices are flexible, beware the trap of rushing requirements just because you know they are going to change. It's still essential to be as accurate as you can. |
|
 |
A Framework for Scaling Continuous Testing across an Enterprise Scaling agile and DevOps across a large enterprise is much more difficult than practicing it in smaller groups. Frameworks can help, but focus tends to be placed on development, so testing teams struggle to figure out how to best support faster development cycles. The ACT Framework puts the focus on continuous testing. |
|
 |
Architecting Your Test Automation Platform With all the pressure to “just automate,” we may not invest enough in architecting our test automation. You wouldn't remodel a house without doing some planning and design; our test automation journey should be treated no differently. A comprehensive architecture plan is crucial for increasing test automation coverage. |
