Software Testing is one of the most misunderstood things within the software industry. Too many people have misconceptions about the craft, probably because it’s hard to define and describe, and it’s often seen as a second class activity compared to programming.
Various models have been used in the past to describe parts of testing, but many of these models have been misused and have added to the problem (take the automation pyramid as an example).
The time has come for us to get serious about this craft. Software is becoming so relied on by the entire world. Its used everywhere, and even small apps play a big part for people. But the quality of our software is holding us back…
It’s almost a daily occurance – turning on the news to hear about another glaring software bug, preying that it’s not your banking software that has a huge problem, or that it’s not your flight that it having checkout problems, or that it’s not your letter that failed to get dispatched from a health service provider.
For too long, we have been pushing quality to the back of the queue, replacing it with our thirst for tech and speed. Now it’s time for us to shift the focus back to quality for our customers and users sakes.
But what does quality mean? How does software testing help us? What is software testing? And where does it fit in our fast paced Agile world?
And further to that, what does “good” testing look like? And how can we fit this “good” testing within a continuous integration and continuous delivery or deployment environment?
#Testing #AgileTesting #Devops