For as long as I have been in software testing, there has been a constant demand to grow technology, grow skills, automate more, and do it all faster (that is a given). What has been so remarkable recently is the rate at which these demands shift gears and move in different directions, new products, and evolving technologies.
Agile’s most defining qualities are speed of delivery and testing friendliness. Automating the tests and building a sustainable, low-maintenance framework is the key to maximizing Agile’s benefits. Doing it right requires new thinking and strategic methods—not old or random test automation practices. When coupled with testing and driven by Action Based Testing (ABT), Agile practices will improve system development and test development.
Agile’s additional value lies with its ability to benefit your company by constructing a collaborative environment. Testers rely on developers, who rely on designers, who rely on automation.
It is our belief at LogiGear that good test design drives automation success. We also believe that, when used properly, Action Based Testing is the key method with which to optimize your test design and automation. We have written a new eBook that highlights the most important aspects of Agile automation; it will teach you everything you need to know about the relationship between Agile and testing, including:
- How Action Based Testing (ABT) drives Agile test automation.
- How to improve your automation using better test design.
- How to ensure that your Agile test automation will be successful.
Automation is a costly investment, and can be a waste of resources if used incorrectly. But when successfully implemented, automation has a return on investment with significant time savings, and increased confidence in your release. Our new Agile Automation ebook will show you how to successfully implement the Action Based Testing methodology and how it will benefit you in the long run. Ultimately, the successful implementation will have a positive effect on your bottom line by improving the integrity of your product, so you and users both win. Download the eBook here today!
Michael Hackett, Senior Vice President
Michael is also a co-founder of LogiGear Corporation, and has over two decades of experience in software engineering in banking, securities, healthcare and consumer electronics.
Michael is a Certified Scrum Master and has co-authored two books on software testing. Testing Applications on the Web: Test Planning for Mobile and Internet-Based Systems (Wiley, 2nd ed. 2003), available in English, Chinese and Japanese, and Global Software Test Automation (HappyAbout Publishing, 2006). He is a founding member of the Board of Advisors at the University of California Berkeley Extension and has taught for the Certificate in Software Quality Engineering and Management at the University of California Santa Cruz Extension. As a member of IEEE, his training courses have brought Silicon Valley testing expertise to over 16 countries.
Just when you thought you were safe from more process improvement for a while—not so fast. There’s DevOps, Continuous Testing, Continuous Delivery and Continuous Deployment. In this issue, we are focusing on Continuous Testing, the part most concerning Test teams.
This article was originally published on DevOps.com
It wasn’t long ago that the Dev and test teams would work late hours, focused and rushed to meet a deadline: rapid fixing, reprioritizing and deferring bugs to close out the bug list, move everything to the staging server, do one last run of the regression and pass it over to Ops/IT to move to production. What happened after? No one knew. For most Dev and test team members, Ops is a black box. More often than not, they are oblivious to what happens at Ops, the roles, responsibilities and timelines. One day—long after the drop-dead deadline for Dev and test teams—after delays, questions and changes, the product went live. Continue reading “What is CT and How Do Traditional Test Teams Fit In?”