As a software tester, inspiration could come from anywhere and everywhere. As we navigate through life, we do so in a way that test the limits of our abilities. Questions I have asked myself in the past are, “Can I make it to work on time if I leave now?”, “What happens if I use baking soda instead of baking powder?”, and on days when I am feeling especially strong, “Can I deadlift 200lbs?”.
“Tools and machines are great, but in the end, it is the people who matter. Putting together an effective automated test team requires lots of planning and skills.” This might the emblematic quote of this great book about software testing automation. The book groups case studies written each by a different author. Each case study is presented in the preface, so you can pick the story that you prefer, based on many criteria like application domain, tool type… or if the project was successful or not.
Continuous testing, continuous delivery, DevOps – these are all terms very popular in the last couple of years, and they all involve a shift in the way we deliver products, software testing included! So who is responsible for the quality assurance nowadays?
Nowadays, you have to make every effort to keep a website visitor. If a user doesn’t like your website design or its logic, you can be sure that this user will immediately leave the page and never come back. That is why every project should create a balanced and effective web design.
A feature toggle is a DevOps technique that provides an alternative to maintaining multiple branches in source code, such that a software feature can be tested even before it is completed and ready for release. Feature toggle is used to hide, enable or disable the feature during runtime.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates