Difference between revisions of "GET TRAINING"

From Test Automation Patterns
Jump to navigation Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................")
 
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Patterns]] / Back to [[Test Automation Patterns]]</span>
 
<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Patterns]] / Back to [[Test Automation Patterns]]</span>
=<span style="font-size: 16px">Pattern summary</span>=
+
=<span style="font-size: 16px">'''Pattern summary'''</span>=
 
<span style="font-size: 16px">Plan to get training for all those involved in the test automation project.</span>
 
<span style="font-size: 16px">Plan to get training for all those involved in the test automation project.</span>
=<span style="font-size: 16px">Category</span>=
+
=<span style="font-size: 16px">'''Category'''</span>=
 
<span style="font-size: 16px">Management</span>
 
<span style="font-size: 16px">Management</span>
=<span style="font-size: 16px">Context</span>=
+
=<span style="font-size: 16px">'''Context'''</span>=
 
<span style="font-size: 16px">This pattern is especially useful when you are starting a new automation project or when you have to integrate new people on the team, but actually you may need it also in order to write disposable scripts</span>
 
<span style="font-size: 16px">This pattern is especially useful when you are starting a new automation project or when you have to integrate new people on the team, but actually you may need it also in order to write disposable scripts</span>
=<span style="font-size: 16px">Description</span>=
+
=<span style="font-size: 16px">'''Description'''</span>=
 
<span style="font-size: 16px">All those involved in the test automation project should get some kind of training. Depending on their assignment they will of course need different kinds or degrees of schooling </span>
 
<span style="font-size: 16px">All those involved in the test automation project should get some kind of training. Depending on their assignment they will of course need different kinds or degrees of schooling </span>
=<span style="font-size: 16px">Implementation</span>=
+
=<span style="font-size: 16px">'''Implementation'''</span>=
 
<span style="font-size: 16px">Some suggestions:</span><br />  
 
<span style="font-size: 16px">Some suggestions:</span><br />  
  
 
* <span style="font-size: 16px">Learn from colleagues that are already doing test automation ([[PAIR UP]])</span>
 
* <span style="font-size: 16px">Learn from colleagues that are already doing test automation ([[PAIR UP]])</span>
* <span style="font-size: 16px">Learn by checking the health of the existing automation testware ([[CHECK-TO-LEARN CHECK-TO-LEARN]])</span>
+
* <span style="font-size: 16px">Learn by checking the health of the existing automation testware ([[CHECK-TO-LEARN]])</span>
 
* <span style="font-size: 16px">Read test automation books or magazines: there are a lot of useful books on the market, that not only give tips on what to do, but also on what not to do</span>
 
* <span style="font-size: 16px">Read test automation books or magazines: there are a lot of useful books on the market, that not only give tips on what to do, but also on what not to do</span>
 
* <span style="font-size: 16px">Go to test conferences: there are always very informative test automation tracks</span>
 
* <span style="font-size: 16px">Go to test conferences: there are always very informative test automation tracks</span>
Line 19: Line 19:
 
* <span style="font-size: 16px">Get a coach to start you off or to help you implement a better automation strategy</span>
 
* <span style="font-size: 16px">Get a coach to start you off or to help you implement a better automation strategy</span>
 
* <span style="font-size: 16px">Search the web: there are a lot of very helpful sites on test automation </span>
 
* <span style="font-size: 16px">Search the web: there are a lot of very helpful sites on test automation </span>
 +
<br />
 +
<span style="font-size: 16px">Recommendations</span><br />
 +
<span style="font-size: 16px">To earn support from your managers, you may have to explain to them why you need training. Prepare a report to show how much time you would save if you could start “as an expert” instead of learning on the job.</span><br /><br /> <span style="font-size: 16px">If you get coaching, remember that you don’t need a coach all the time: After a few days you should work alone for a week or so. When the coach returns you will have gained more understanding by trying to go on your own and you will have more and better questions to ask.</span><br /><span style="font-size: 16px">Team members may be feeling unmotivated because they don’t feel up to their tasks. Make sure that they can [[ASK FOR HELP]] and let them get the training they need.</span><br /> <br /> <span style="font-size: 16px">Remember that there is a need for both formal training (courses or conference tutorials on specific tools or test automation principles), and also for informal training within your company. This would be useful to help new automators understand the application that is being tested, and to understand how automation has been done in the past in the company. Informal training may just be a group of people getting together to discuss a topic, or it could be an internal presentation.</span><br />
 +
=<span style="font-size: 16px">'''Potential problems'''</span>=
 +
<span style="font-size: 16px">Make sure that people sent to trainings share their new gained knowledge with the other team members. Also don't send always only the same people to trainings.</span>
 +
=<span style="font-size: 16px">'''Issues addressed by this pattern'''</span>=
 +
''<span style="font-size: 16px">[[KNOW-HOW LEAKAGE]]</span>''<br /> ''<span style="font-size: 16px">[[LIMITED EXPERIENCE]]</span>''<br /> ''<span style="font-size: 16px">[[LOCALISED REGIMES]]</span>''<br /> ''<span style="font-size: 16px">[[NO PREVIOUS TEST AUTOMATION]]</span>''<br /> ''<span style="font-size: 16px">[[UNMOTIVATED TEAM]]</span>''
 +
=<span style="font-size: 16px">'''Experiences'''</span>=
 +
 +
<span style="font-size: 16px">If you have used this pattern and would like to contribute your experience to the wiki, please go to [[Feedback]] to submit your experience or comment.</span><br /> <br />
 +
  
=<span style="font-size: 16px">Recommendations</span>=
+
<span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Patterns]] / Back to [[Test Automation Patterns]]</span></div>
<span style="font-size: 16px">To earn support from your managers, you may have to explain to them why you need training. Prepare a report to show how much time you would save if you could start “as an expert” instead of learning on the job.</span><br /> <br /> <span style="font-size: 16px">If you get coaching, remember that you don’t need a coach all the time: After a few days you should work alone for a week or so. When the coach returns you will have gained more understanding by trying to go on your own and you will have more and better questions to ask.</span><br /> <span style="font-size: 16px">Team members may be feeling unmotivated because they don’t feel up to their tasks. Make sure that they can [[ASK FOR HELP]] and let them get the training they need.</span><br /> <br /> <span style="font-size: 16px">Remember that there is a need for both formal training (courses or conference tutorials on specific tools or test automation principles), and also for informal training within your company. This would be useful to help new automators understand the application that is being tested, and to understand how automation has been done in the past in the company. Informal training may just be a group of people getting together to discuss a topic, or it could be an internal presentation.</span>
 
=<span style="font-size: 16px">Issues addressed by this pattern</span>=
 
''<span style="font-size: 16px">[[KNOW-HOW LEAKAGE]]</span>''<br /> ''<span style="font-size: 16px">[[LIMITED EXPERIENCE]]</span>''<br /> ''<span style="font-size: 16px">[[LOCALISED REGIMES]]</span>''<br /> ''<span style="font-size: 16px">[[NO PREVIOUS TEST AUTOMATION]]</span>''<br /> ''<span style="font-size: 16px">[[UNMOTIVATED TEAM]]</span>''
 
=<span style="font-size: 16px">Experiences</span>=
 
<span style="font-size: 16px">If you have used this pattern, please add your name and a brief story of how you used this pattern: your context, what you did, and how well it worked - or how it didn't work!</span><br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Management Patterns]] / Back to [[Test Automation Patterns]]</span></div>
 

Latest revision as of 14:47, 21 August 2018

.................................................................................................................Main Page / Back to Management Patterns / Back to Test Automation Patterns

Pattern summary

Plan to get training for all those involved in the test automation project.

Category

Management

Context

This pattern is especially useful when you are starting a new automation project or when you have to integrate new people on the team, but actually you may need it also in order to write disposable scripts

Description

All those involved in the test automation project should get some kind of training. Depending on their assignment they will of course need different kinds or degrees of schooling

Implementation

Some suggestions:

  • Learn from colleagues that are already doing test automation (PAIR UP)
  • Learn by checking the health of the existing automation testware (CHECK-TO-LEARN)
  • Read test automation books or magazines: there are a lot of useful books on the market, that not only give tips on what to do, but also on what not to do
  • Go to test conferences: there are always very informative test automation tracks
  • Subscribe to webinars: quite often they present interesting issues and they are mostly free
  • Tool vendors offer courses and training on how to use their tools
  • Get a coach to start you off or to help you implement a better automation strategy
  • Search the web: there are a lot of very helpful sites on test automation


Recommendations
To earn support from your managers, you may have to explain to them why you need training. Prepare a report to show how much time you would save if you could start “as an expert” instead of learning on the job.

If you get coaching, remember that you don’t need a coach all the time: After a few days you should work alone for a week or so. When the coach returns you will have gained more understanding by trying to go on your own and you will have more and better questions to ask.
Team members may be feeling unmotivated because they don’t feel up to their tasks. Make sure that they can ASK FOR HELP and let them get the training they need.

Remember that there is a need for both formal training (courses or conference tutorials on specific tools or test automation principles), and also for informal training within your company. This would be useful to help new automators understand the application that is being tested, and to understand how automation has been done in the past in the company. Informal training may just be a group of people getting together to discuss a topic, or it could be an internal presentation.

Potential problems

Make sure that people sent to trainings share their new gained knowledge with the other team members. Also don't send always only the same people to trainings.

Issues addressed by this pattern

KNOW-HOW LEAKAGE
LIMITED EXPERIENCE
LOCALISED REGIMES
NO PREVIOUS TEST AUTOMATION
UNMOTIVATED TEAM

Experiences

If you have used this pattern and would like to contribute your experience to the wiki, please go to Feedback to submit your experience or comment.


.................................................................................................................Main Page / Back to Management Patterns / Back to Test Automation Patterns