Difference between revisions of "HowCanWeBecomeBetterTesters"
PaulJulius (talk | contribs) (Created page with "How do we become better testers? 2 Questions: How do we teach newbee testers?") |
PaulJulius (talk | contribs) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | How do we become better testers? | + | ==How do we become better testers?== |
| − | + | ===Two Questions:=== | |
| − | How do we teach newbee testers? | + | ====1. How we choose our tools, languages, etc? (Our destiny)==== |
| + | |||
| + | ====2. How do we teach newbee testers?==== | ||
| + | * pair programming/testing | ||
| + | |||
| + | '''Real world example''': 10 people in room, 2 people were being projected== | ||
| + | * mob programming | ||
| + | |||
| + | ====How do we become better testers when we are at the same level?===== | ||
| + | * Join monthly meetups | ||
| + | * Get outside our comfort zone | ||
| + | * SpeakEasy free program for learning how to speak of conference | ||
| + | |||
| + | =====What Qualities Makes a Good Tester==== | ||
| + | |||
| + | Analytical Thinking | ||
| + | Curiosity | ||
| + | Critical Thinking | ||
| + | Being Organized | ||
| + | Active Reading | ||
| + | Fundamental Understanding of Systems (or Software Systems) | ||
| + | Human Skills - Communication Skills | ||
| + | Fast Learner | ||
| + | Programming | ||
| + | Software Architecture | ||
| + | Domain Knowledge | ||
| + | User Experience | ||
| + | |||
| + | =====Should people go directly from university to being a tester?===== | ||
| + | Do an internship | ||
| + | Internships typically do not offer learning how to code | ||
| + | Internships can help discover your true calling as a tester | ||
| + | |||
| + | =====So how do we become a better tester?===== | ||
| + | Explain project architecture | ||
| + | Explain tools | ||
| + | Internship program 3 months - focus mostly on testing knowledge | ||
| + | Do some test automation | ||
| + | Focus on a learning project, create a test, and then debrief with someone more knowledge | ||
| + | Mentoring continues beyond the initial introduction | ||
| + | Session-based testing | ||
| + | Long process toward autonomy | ||
| + | Domain knowledge can be critical | ||
| + | |||
| + | '''SBTM''' | ||
| + | Created by James & John Bach | ||
| + | Each session 60 to 90 minutes | ||
| + | Has a goal | ||
| + | Debriefing at the end | ||
| + | Purpose is to learn to split | ||
| + | |||
| + | =====Regression Testing?===== | ||
| + | "I hate the word regression. It's a regression of the testing, really." - Alex R | ||
| + | Communication between development and product management | ||
| + | |||
| + | ===Destiny=== | ||
| + | More than just tools | ||
| + | More than just the car I am driving.... | ||
| + | |||
| + | Maybe.... | ||
| + | "Finding a new path, instead of tooling." | ||
| + | |||
| + | More notes here .... | ||
Latest revision as of 01:06, 16 April 2016
How do we become better testers?
Two Questions:
1. How we choose our tools, languages, etc? (Our destiny)
2. How do we teach newbee testers?
- pair programming/testing
Real world example: 10 people in room, 2 people were being projected==
- mob programming
How do we become better testers when we are at the same level?=
- Join monthly meetups
- Get outside our comfort zone
- SpeakEasy free program for learning how to speak of conference
=What Qualities Makes a Good Tester
Analytical Thinking Curiosity Critical Thinking Being Organized Active Reading Fundamental Understanding of Systems (or Software Systems) Human Skills - Communication Skills Fast Learner Programming Software Architecture Domain Knowledge User Experience
Should people go directly from university to being a tester?
Do an internship Internships typically do not offer learning how to code Internships can help discover your true calling as a tester
So how do we become a better tester?
Explain project architecture Explain tools Internship program 3 months - focus mostly on testing knowledge Do some test automation Focus on a learning project, create a test, and then debrief with someone more knowledge Mentoring continues beyond the initial introduction Session-based testing Long process toward autonomy Domain knowledge can be critical
SBTM Created by James & John Bach Each session 60 to 90 minutes Has a goal Debriefing at the end Purpose is to learn to split
Regression Testing?
"I hate the word regression. It's a regression of the testing, really." - Alex R Communication between development and product management
Destiny
More than just tools More than just the car I am driving....
Maybe.... "Finding a new path, instead of tooling."
More notes here ....
