The document emphasizes that self-education in software testing is the individual's responsibility, rather than relying on employers or educators. It details various methods for self-improvement, including personal blogging, social media involvement, and learning programming languages. Additionally, it outlines resources such as testing challenges, dojos, and online courses for practical skill development.

1. Alternative Paths for Self-Education In Software Testing
Markus Gärtner -http://blog.shino.de -Twitter: @mgaertnehttp://commons.wikimedia.org/wiki/File:Education_-_Grad_Hat_-_Jordan.png

2. Education in Software Testing
My story
University studies until October 2005
1st position as a software tester April 2006
1st training course in software testing: October 2007
Appointed a software testing group lead position in September 2007!

3. Who is responsible for your education?
Your employer?
Your superior?
Your teacher back in school?
Maybe your husband/wife?
Your kids?

4. Who is responsible for your education?

5. YOU!
http://commons.wikimedia.org/wiki/File:Uncle_Sam_(pointing_finger).jpg

6. Feedback
Start a personal blog or private journal
Write an article
Contribute to mailing lists
Involve yourself in social media
Twitter
LinkedIn
Software Testing Club
Weekend Testing

7. Learn to program
Scripting languages: Ruby, Python, Groovy
Design Patterns
Technology: TDD, Mocking
Pairing
http://stevelucasmetz.blogspot.com/2008/01/rambo-baby.html

8. Hypothesis vs. Synthesis
Hypothesis
Books
Rapid Software Testing
Black-box software testing
Buccaneer-scholar
Synthesis
Black-box software testing
Testing Dojos & Challenges
Weekend Testing
Miagi-Do school
http://wordandimage.files.wordpress.com/2007/12/brain.gif

9. Bookshttp://blog.lib.umn.edu/isss/isss/2009/02/

10. Rapid Software Testing
DevelopedbyJames Bach andMichael Bolton
Taughtasa course, but slidesavailableonline:
http://www.satisfice.com/rst.pdf
Contents include:
Whatistesting?
The Heuristic Test
StrategyModel
Heuristics, Oracles
andthetester‘smind
… andmuchmore
http://s0.geograph.org.uk/photos/06/47/064756_80eeb599.jpg

11. Black-box Software Testing
Developed by Cem Kaner and James Bach
Online courses by AST
Videos online available:
http://www.testingeducation.org/BBST/
http://upload.wikimedia.org/wikipedia/commons/1/1b/Peering_Inside_the_Black_Box.jpg

12. Black-box Software Testing
Bug advocacy
Testing techniques
Domain testing
Scenario testing
Function testing
Risk-based testing
Combination testing
Specification-based testing
http://upload.wikimedia.org/wikipedia/commons/1/1b/Peering_Inside_the_Black_Box.jpg

13. Buccaneer-scholar
Book by James Bach
Learning heuristics
SACKED SCOWS
Long Leash Heuristic
Obsess and Forget Heuristic
Procrastinate and Push Heuristic
… are just some of the underlying principles
http://running-wild.net/pics/content/gallery/tattoos/04.jpg

14. Testing Challenges
Testingchallenges
Practicalexerciseof testingskills
Haveinternetwill test:http://www.satisfice.com/blog/archives/322
http://www.defibolivie2010.org/challenge_Sajama.jpg

15. Testing Dojos
Similar to Coding Dojos
Collaboration
Save Environment
Deliberate Practice
Content:
Single Testing vs. Paired Testing
Test this, Evaluate Tools, Learn new approaches
http://www.matrix-architekt.de/bilder/desktop/dojo.jpg

16. Weekend Testing
Testing on the weekend online
Typical session:
1 hour Practical testing
1 hour Discussion
Content:
Test this
Evaluate tools
Learn new approaches
Watch out for traps!

17. Miagi-Do School of Software Testing
Founded by Matt Heusser
Non-commercial, zero-profit
Improve testing skill
Through practice
Belt system
http://farm3.static.flickr.com/2074/2200982710_8cf8e0d422.jpg

18. Summary
Education is your repsonsibility
Different styles
Feedback
Hypothesis
Synthesis
You may have preferences for one or the other, but you should apply as much as possible