How To Do Good Regression Testing
The latest from the Software Testing Clinic
How To Do Good Regression Testing
The question of ‘How do I do good regression testing?’ came up in the Software Testing Clinic section of The Club, but it’s a common question some testers struggle with. There is a dichotomy when it comes to regression testing. Not enough regression testing and you risk bugs slipping through to production, too much regression testing and you and your team become swamped. Finding the right balance of test coverage is an important part of regression testing. Read the rest of the article
99 Second Introduction to Diagrams
In this video Dan and Mark will introduce you to what diagrams are, the value of using them, provide some examples and discuss the pitfalls you should be aware of. Watch the video.
How To Gain Experience Software Testing As A Novice
If you’re new to testing it can be hard to find a way to practice your new skills and to gain more experience. Are there tools you use? Or maybe there is a platform you practice testing on? We’ve been sharing some resources over on The Club. Join the discussion.
Defining ‘regression’ in testing
We’ve been thinking about regression testing and it’s definition. When talking about regression testing we’re concerned with investigating if our product has ‘regressed’ back to an unacceptable or worse state. If a bug is introduced through new code, so technically never existed before, can we acceptably say that the state of the software has regressed? Too literal? Share your thoughts.
Upcoming Sessions
- Communication — Monday 23rd October — London
- Exploratory 101 — Thursday 26th October — Manchester
- Become a Mentor — Monday 11th December — Manchester
5 Things We Found Interesting This Month
Each month we will share a few post and articles, both new and old that have caused pause for thought.
The AI Revolution — Whilst this isn’t entirely related to learning about software testing this 2 part blog is an astonishing introduction to the future of AI and how it might impact us. It’s a long read but the discussions on the speed in which we are discovering new technologies is important to how we develop our skills.
The Myth Of The Degree — Some people feel to be in software development you have to have a degree in computer science, but having academic diversity in test teams is a powerful thing and it proves you can gain the necessary skills without qualifications. All you need to is explore!
DevOps chat with Steve Hazel — Steve Hazel (CTO of Sauce Labs) talks about DevOps, the role that automation plays, why he thinks we’ll need more higher quality testing from people and more security testing, plus a few other things.
Auditors and testing — This post is great for anyone working in a context where they have auditors. I’ve recently been changing testing strategies in a big regulated company, and there have been many discussions with auditors about how they can read test reports detailing ET notes and results, use SBTM and even understand Agile, iterative releases, and more. James shares his experiences and stories in this post about good and bad auditing practices and what auditors really need as evidence.
Heuristics for Mushroom Picking (and testing) — I love how Helena explains testing by comparing it to another task she’s passionate about. Understanding the value but also the trade offs of testing activities is just as important as knowing how to use them in the first place
