Difference between revisions of "Diagnostic"
Jump to navigation
Jump to search
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
<div id="content_view" class="wiki" style="display: block"><span style="font-family: Arial,Helvetica,sans-serif; font-size: 16px">Test Automation Patterns are most useful if you can focus on the ones that really help solve your issues. We start the diagnostic process by asking some questions. Some will lead you directly to a specific issue; others will have a number of possible answers which lead to more detailed questions or to the issue that best describes your problem. At any level you will be able to return to the preceding level. Your answers should help pinpoint your main issue(s). These issues contain recommendations for the patterns that will help you solve your problems. In the resolving patterns we give some guidelines, but choosing how to apply the patterns is something that you will need to think about for your own situation.</span><br /> | <div id="content_view" class="wiki" style="display: block"><span style="font-family: Arial,Helvetica,sans-serif; font-size: 16px">Test Automation Patterns are most useful if you can focus on the ones that really help solve your issues. We start the diagnostic process by asking some questions. Some will lead you directly to a specific issue; others will have a number of possible answers which lead to more detailed questions or to the issue that best describes your problem. At any level you will be able to return to the preceding level. Your answers should help pinpoint your main issue(s). These issues contain recommendations for the patterns that will help you solve your problems. In the resolving patterns we give some guidelines, but choosing how to apply the patterns is something that you will need to think about for your own situation.</span><br /> | ||
| − | <span style="font-size: 16px">Note</span>'''<span style="font-size: 16px">: we are talking about automating system level tests, </span><u><span style="font-size: 16px">not</span></u><span style="font-size: 16px"> unit | + | <span style="font-size: 16px">Note</span>'''<span style="font-size: 16px">: we are talking about automating system level tests, </span><u><span style="font-size: 16px">not</span></u><span style="font-size: 16px"> unit tests.</span><br /> <br /> <span style="font-size: 16px">Here are some questions to get you started looking for the issues you may be encountering:</span><br /> <br /> |
| − | # <span style="font-size: 16px">Are you | + | |
| + | # <span style="font-size: 16px">Are you dissatisfied with your current automation? Did you try automation and it didn't work and is now abandoned, or it just isn't giving you the benefits you had wanted and expected. In this case you want to </span><span style="font-size: 20px">'''[[Improve or revive test automation]]'''.</span> | ||
# <span style="font-size: 16px">Are you just starting with automation and have never done it before? Look at the issue ''[[NO PREVIOUS TEST AUTOMATION]].''</span> | # <span style="font-size: 16px">Are you just starting with automation and have never done it before? Look at the issue ''[[NO PREVIOUS TEST AUTOMATION]].''</span> | ||
# <span style="font-size: 16px">Are you joining a test automation team and have no experience in test automation? Look at the issue ''[[LIMITED EXPERIENCE]]'' for suggestions on how to catch up fast.</span> | # <span style="font-size: 16px">Are you joining a test automation team and have no experience in test automation? Look at the issue ''[[LIMITED EXPERIENCE]]'' for suggestions on how to catch up fast.</span> | ||
| − | |||
# <span style="font-size: 16px; line-height: 1.5">Do you already know what your specific issues are? If so, you can go straight to the relevant issue(s) </span><span style="font-size: 16px">from the </span>''<span style="font-size: 16px">[[Test Automation Issues]]</span>''<span style="font-size: 16px">.</span> | # <span style="font-size: 16px; line-height: 1.5">Do you already know what your specific issues are? If so, you can go straight to the relevant issue(s) </span><span style="font-size: 16px">from the </span>''<span style="font-size: 16px">[[Test Automation Issues]]</span>''<span style="font-size: 16px">.</span> | ||
<br /> <br /> <span style="font-size: 16px">Tips: </span><br /> | <br /> <br /> <span style="font-size: 16px">Tips: </span><br /> | ||
* <span style="font-size: 16px">If the first option you try doesn't seem to fit your situation, come back to this page and try another.</span> | * <span style="font-size: 16px">If the first option you try doesn't seem to fit your situation, come back to this page and try another.</span> | ||
| − | * <span style="font-family: 'Arial',sans-serif; font-size: 16px">If in your company there are different teams working with automation, let each do the diagnostic first by themselves. If the issues they wind up with differ substantially you should then look up the issue ''[[LOCALISED REGIMES]]'' because that’s a sign that each team is working completely independently from the others, there is no sharing of know-how, methods, standards etc. | + | * <span style="font-family: 'Arial',sans-serif; font-size: 16px">If in your company there are different teams working with automation, let each do the diagnostic first by themselves. If the issues they wind up with differ substantially you should then look up the issue ''[[LOCALISED REGIMES]]'' because that’s a sign that each team is working completely independently from the others, there is no sharing of know-how, methods, standards etc. </span> |
| − | <br /> <br /> <span style="font-size: 16px">Note: Diagnostic pages have titles in "Sentence" case (first letter capitalised, then lower case), ''ISSUES'' and PATTERNS have titles in UPPER CASE.</span><br /> <br /> <span style="font-size: 16px">(Let us know if there is a question we should be asking at any point that would be more relevant to you than the ones we already have - thanks.)</span><br /> <br /> | + | <br /> <br /> <span style="font-size: 16px">Note: Diagnostic pages have titles in "Sentence" case (first letter capitalised, then lower case), ''ISSUES'' and PATTERNS have titles in UPPER CASE.</span><br /> <br /> <span style="font-size: 16px">(Let us know if there is a question we should be asking at any point that would be more relevant to you than the ones we already have - thanks. See [[Feedback]] page for reporting this or other feedback.)</span><br /> <br /> |
| − | |||
</div> | </div> | ||
Latest revision as of 16:16, 21 August 2018
Test Automation Patterns are most useful if you can focus on the ones that really help solve your issues. We start the diagnostic process by asking some questions. Some will lead you directly to a specific issue; others will have a number of possible answers which lead to more detailed questions or to the issue that best describes your problem. At any level you will be able to return to the preceding level. Your answers should help pinpoint your main issue(s). These issues contain recommendations for the patterns that will help you solve your problems. In the resolving patterns we give some guidelines, but choosing how to apply the patterns is something that you will need to think about for your own situation.
Note: we are talking about automating system level tests, not unit tests.
Here are some questions to get you started looking for the issues you may be encountering:
- Are you dissatisfied with your current automation? Did you try automation and it didn't work and is now abandoned, or it just isn't giving you the benefits you had wanted and expected. In this case you want to Improve or revive test automation.
- Are you just starting with automation and have never done it before? Look at the issue NO PREVIOUS TEST AUTOMATION.
- Are you joining a test automation team and have no experience in test automation? Look at the issue LIMITED EXPERIENCE for suggestions on how to catch up fast.
- Do you already know what your specific issues are? If so, you can go straight to the relevant issue(s) from the Test Automation Issues.
Tips:
- If the first option you try doesn't seem to fit your situation, come back to this page and try another.
- If in your company there are different teams working with automation, let each do the diagnostic first by themselves. If the issues they wind up with differ substantially you should then look up the issue LOCALISED REGIMES because that’s a sign that each team is working completely independently from the others, there is no sharing of know-how, methods, standards etc.
Note: Diagnostic pages have titles in "Sentence" case (first letter capitalised, then lower case), ISSUES and PATTERNS have titles in UPPER CASE.
(Let us know if there is a question we should be asking at any point that would be more relevant to you than the ones we already have - thanks. See Feedback page for reporting this or other feedback.)