There is an approach to testing called Exploratory Testing and it is important to know how to use it, when to use it, how to manage it, what are its strengths and some of its weaknesses and we want to talk about this today
[Part 2 from Joel and Rob all about software testing bugs.] Bugs are an important part of the work of testers, but for some reason, we tend to take them for granted and don’t invest the proper value and thoughts to them.
Joel and Rob discuss the current meaning of creating a master test plan in the age of Agile and DevOps. "The fact we moved to Agile and that we are working more on the UserStory level should not mean that we do not need to plan our testing".
Testers or Quality Assurance? Can we influence or drive quality? Should we? People can and should, but not everyone can. And some organisations do not welcome it. We can and should, but not everyone CAN right now. It’s all about communication skills - being able to articulate ideas and change. And also to the right person. Context is key. Some teams it is easier. Some companies do not welcome change. We need to do it.
Culture is nothing more than group habit - it’s what people do every day. So in order to change a culture to one of a “quality” one, you must identify the behaviors that lead to good outcomes and encourage these throughout the organization.
Is Software Testing More About Testing Or Programming? As the testing world evolves, the lines between tester and developers are starting to fade. Testers now need to have some programming abilities as well.
Being a sole tester of a company is without a doubt a big responsibility, but panicking won’t help here. Your job is to lead the testing process of the company, it doesn’t mean you should be the one that performs all the necessary tests. Therefore, not every bug that would be found after releasing the product is your responsibility.