Related Content
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. |
||
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. |
||
2 Ways to Standardize QA Practices Testing can get complicated when each project is using a completely different toolset, language, and reporting status, with different measurements and formats. Testing is a reaction to context and what we encounter, so how we test cannot be standardized. What we can standardize is the stuff that surrounds the testing. |
||
Getting Support for the Tests You Need Done It’s often hard for teams to get sufficient time and resources for the amount and quality of tests they think are needed. It’s like management wants testing done but at the same time doesn’t want to commit what’s needed to do it. If that's your case, look at the business side, rank priorities, and negotiate resources. |
||
Get Your Defect-Tracking Database Back on Track When defects are ignored or mismanaged, it can compromise the integrity of the defect-tracking database. When this happens, defects could go unfixed, or code fixes may not be verified by the production release. Before you can resolve a compromised defect-tracking database, you need to know how to recognize one. |
||
It’s 10 p.m. Do You Know Where Your Defect Fix Is? Have you ever had to ask whether your defect fix was deployed to a particular environment? You shouldn’t need to, because the answer should always be readily available. Having to request information on the status of your defect fix indicates inefficiencies and a lack of maturity within your organization’s process. |
||
5 Ways Test Management Tools Help in Agile Environments Test management tools help improve the efficiency of development and testing teams by prioritizing test cases, so it makes sense that they would appeal to companies that have adopted an agile methodology to enable quicker release cycles. Here are five ways test management tools make a difference in agile environments. |
||
Merging New Codeless Test Automation with Your Existing Code-Based Test Scripts Adopting a codeless solution can be an amazing boost to quality, productivity, and tester career growth, but in most organizations, such test suites will have to be merged into existing code-based test scripts. To succeed, developers, testers, and management all should consider the differences between the two options. |