I think that lot of us, QA testers, dream of spending less time on regressions and doing something more valuable such as: automation, non functional testing and many more. In my talk, I would like to share with you how you can save time for more interesting task simply by teaching developers how to tests their own code.

1. ●

5. ●
●
●

8. Profit
Ready for
release
2*Y
Takes only “X + Y” time to complete
Development
X
Testing

9. TestingDevelopment
Reopened and
waiting for a
developer
X Y Z
(unknown)

10. Context
switch and
bug fixing
A
TestingDevelopment
Reopen and waiting
for being picked up by
developer
X Y Z
(unknown)
(unknown)

11. Context
switch and
bug fixing
A
TestingDevelopment
Reopen and waiting
for being picked up by
developer
X Y Z
(unknown)
(unknown)
Waiting
in review
queue
B
(unknown)

12. Waiting
in QA
queue
Context
switch and
bug fixing
A C
TestingDevelopment
Reopen and waiting
for being picked up by
developer
X Y Z
(unknown)
(unknown) (unknown)
Waiting
in review
queue
B
(unknown)

13. Waiting
in QA
queue
Context
switch and
bug fixing
Retes-
ting
A C D
(unknown)
TestingDevelopment
Reopen and waiting
for being picked up by
developer
X Y Z
(unknown)
(unknown) (unknown)
Waiting
in review
queue
B
(unknown)

14. X + Y + Z + A + B + C + D =

15. X + Y + Z + A + B + C + D =

52. ALL THAT

53. ALL THAT
TIME

54. the parts that may be
applicable to your ticket

65. MIND MAPS: FOR FAST AND EFFECTIVE TESTING http://bit.ly/QAmindMap