Testing is about breaking illusions for our software systems. It’s work where results - information at our disposal - matters, with no easy way of listing the results. There is no ‘answer key to all the bugs’, the practice of us testing turns the invisible ink visible line by line.
The world of testing is changing. We can factually state that levels of automation and programmatic tests have increased. A raise of hands in a developer conference asking which of them tests has all hands up. Testing is too important to be left just for testers. And testing is too important to be left without testers. Agile mindset and practices have effectively removed test managers, and redistributed that work to product owners and teams.
Let’s look at what the recipe for resultful testing includes - how different roles contribute, how we assess testing as a whole, and we all have our part to play in creating an environment where resultful testing is not only possible, but likely, both in software delivery and acceptance organizations.
maaretp
k_koheyi
line_developers_tw
huffon
kentosuzuki
tomuro
hiashisan
oracle4engineer
hk_shino
ytaisei
soudai
miyashino
mitsuakitohei
rasmusluckow
bryan
zakiyama
panda_program
shpigford
geeforr
kastner
mongodb
lara
mclloyd
bcantrill
hannesfritz