test methodologies
Guaranteed Methods to Ruin Your Test Automation After working to develop the test automation patterns used by experienced practitioners to solve common test automation issues, Seretta Gamba started to consider what can ruin a test automation effort instead. Here she shares two sure-fire methods that can destroy your test automation. Steer clear of these examples! |
||
Testing Artificial Intelligence: How Low Can You Go? Artificial intelligence (AI) is propelling to the forefront once more. With the growing importance of AI comes the question: How do I test it? AI systems do not necessarily behave predictably. This means that traditional test cases of the form "do this, expect that" are not always sufficient. |
||
Automation for the People We tend to contrast automated and manual testing, but really, they should support each other. The key is to define what our testing objectives are, then build the solution needed to achieve them—probably a combination of manual and automated testing. We should not let the method become more important than the results. |
||
Software Testing Trends for 2018 The software testing trends that are being predicted for the new year are all over the place. Rajini Padmanban looks at the predicted trends for software testing while also examining what she is already seeing as the common requests and needs in the field. |
||
The Lifecycle of Technology Trends Trends are very important to follow, especially in the technology world, for both product and service companies. Mukesh Sharma explains the technology trend lifecycle and what it means for testers. |
||
Continuous Testing: New Improvements on an Old Idea The concept behind continuous testing is far from new, but what’s different now is that software development practices have evolved to a point where developers are embracing testing as part of their responsibilities. Testing is slowly moving from being an “event” to an activity throughout the development lifecycle. |
||
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. |
||
Encouraging Just-In-Time Testing When the development landscape is extremely dynamic, a testing effort that is adaptable and flexible with an ability to learn the system and craft scenarios on the go is increasingly important. Testers should be encouraged to be just-in-time testers with the ability to test anything at any time. |