All That Testing ... ...Getting ... ... the Way of ...
Your contribution
1. 2. 3. 4. The tests I develop are as valuable as any code a developer writes Test is important but not quite as much as development Test is definitely a second class citizen The developers are the heroes in my company
Your contribution
1. 2. 3. 4. The tests I develop are as valuable as any code a developer writes Test is important but not quite as much as development Test is definitely a second class citizen The developers are the heroes in my company
Your compensation
1. 2. 3. 4. I make as much or more than my development counterparts I make less, but it's close Testers at my company swim in the shallow end of the wage pool I would trade salaries with almost anyone in the development org
12-16
12-16
17-21
12-16
17-21
22-24
Uh, there's more to life than work ... right? ... right?
Respect
You can whine about it ...
Respect
You can whine about it ...
Respect
You can demand it ...
Respect
You can demand it ...
Respect
Or you can earn it ...
Really? How's that whole authority thing working out for you Bret?
Really? How's that whole authority thing working out for you Bret? Reality check: how many of you work for a company where you enjoy such authority?
These are the same criteria by which we judge admins, document writers and every other support organization. Is test just another support org?
Or, does the work we do make us more critical path?
So this confirms the support status of the test discipline. We support the people doing the high value work by tidying up around them. Surely there must be more?
Vs.
Only the software matters The value of testing is in the activity, not the artifacts The only important artifact is code Bugs don't count unless they get fixed
Only the software matters The value of testing is in the activity, not the artifacts The only important artifact is code Bugs don't count unless they get fixed
Only the software matters The value of testing is in the activity, not the artifacts The only important artifact is code Bugs don't count unless they get fixed
Only the software matters The value of testing is in the activity, not the artifacts The only important artifact is code Bugs don't count unless they get fixed
The test team's relevancy is related to their impact on the product not their ability to create documents
In fact, as long as testing gets done it really doesn't matter who does it
Only the software matters The value of testing is in the activity, not the artifacts The only important artifact is code Bugs don't count unless they get fixed
Only the software matters The value of testing is in the activity, not the artifacts The only important artifact is code Bugs don't count unless they get fixed
Only the software matters The value of testing is in the activity, not the artifacts The only important artifact is code Bugs don't count unless they get fixed
Only the software matters The value of testing is in the activity, not the artifacts The only important artifact is code Bugs don't count unless they get fixed
"If I don't find all these bugs, users will suffer" you will never
find them all, users will suffer no matter what you do
Devs can do it better The old stereotype is gone, if not whose fault is it?
Take on a specialty
Be a web security tester now An entire discipline for privacy testing is waiting for a guru
James Whittaker
Engineering Director Google