Articles


Introduction

What comes to your mind when you hear the term Black box, specifically concerning testing? Well, it is something that is not very common to listen to but remains an essential form of software testing. It is a software testing technique to examine the functioning of software from an external outlook without digging deeper into its code. The best thing about Black box testing is that it can be applied to all levels of testing ( Unit, integration, system, and acceptance). 

Anybody with minimum or no coding language can perform Black box testing of a software product, software testers with no coding language can also do it.

Source de l’article sur DZONE

Testers + Scrum = ?

Several times I’ve had conversations with people who work with Scrum or Agile methodologies who claim they don’t have testers and don’t run into any problems. On the other hand, I have seen testers within these schemes who often feel excluded from the development team. Other testers who have not yet worked in Agile teams question whether there is even room for testers in Scrum.

It’s often touted that everyone in a Scrum team is able to perform different tasks and that all are responsible for quality. But, there are some things that a tester can handle better than others. For example, writing good acceptance criteria requires a tester skillset, as one must keep in mind and worry about certain characteristics such as quality, testability, maintainability, etc. These are all things that the tester role is responsible for obsessing over. Therefore, when you need to write acceptance criteria, you’ll be better off delegating it to someone trained in testing over someone that’s not.

Source : https://dzone.com/articles/can-there-be-testers-in-scrum?utm_medium=feed&utm_source=feedpress.me&utm_campaign=Feed%3A+dzone%2Fagile