Related Content
 |
Transitioning from a Traditional Tester to an Agile Tester Shifting from being a tester in a traditional lifecycle model to in an agile methodology is not easy. There is a spectrum of differences, ranging from redefining the testing role and responsibilities completely to making only minor changes in context and accountability. Read on for some key changes. |
|
 |
Analyzing the Value of a Test Tool Approach Many test managers want to assess the value of their test tool approach. There is a way to do it that does not require writing code—only the ability to read it a little. Matt Heusser helps you figure out if what your team is doing is working, what you could drop, and what might be worth picking up. |
|
 |
Agile Testing: A Lesson in Diversity Though many QA organizations today use agile development methods, depending on the industry, they can experience very different challenges and successes. By exploring the diversity in the testing world, you can learn other industries’ strengths and think about how they could apply to your field. |
|
 |
Maintaining Tester Independence in an Agile World As organizations adopt agile methodologies, one of the key challenges is reinventing traditional roles. The entire agile team is now accountable for quality—carrying the quality flag is not the sole responsibility of the tester. But we also want to ensure that we maintain tester role independence. |
|
 |
Keeping Quality in DevOps In our drive for better quality and productivity, we are coming close to realizing full continuous application lifecycle management. Continuous testing is emerging as a best practice that focuses on developing testing procedures, primarily automated, to meet the need for fast application testing. |
|
 |
Quality Principles for Today’s Glueware In this STARWEST 2014 keynote, Julie Gardiner goes into how to make the business case for including test professionals in software evaluation in order to add their unique focus on software quality. She gives advice on how to talk to managers and produce better software. |
|
 |
Why You Should Focus On What Automation Does Not Do Often, what automation “does” directly relates to the bottom line. This has loosely been interpreted as the misconception that the more automation you have, the fewer people you will need on your payroll. Melissa Tondi focuses on what automation does not do to give a more accurate idea. |
|
 |
Maintaining Testable Requirements and Acceptance Criteria Once a testable requirement or acceptance criteria have been “created,” there is a tendency to assume that the task can be considered completed. Because that may or may not be true, it is better to continue to pay attention to testability. Here are four ways to maintain testable requirements. |
