Downloaded 36 times
![Risk Example: Contact Form on Web Site
You received this e-mail message through your website:
reason: default
E-mail: ngjchr@somewebsitethatdoesnotexist.com
Name: ewogwah
Message: pK9ctN kfoummnkudob,
[url=http://dnaaimbzpgyg.com/]dnaaimbzpgyg[/url],
[link=http://mmkwfndaydxb.com/]mmkwfndaydxb[/link],
http://bwtjxnpecomy.com/
:
IP: 46.161.9.32
Browser: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Points: 0
Join the conversation – use the hashtag #risktesting on Twitter](https://image.slidesharecdn.com/qasymphonyalanrichardsonriskfinal-160629155625/75/Risk-Mitigation-Using-Exploratory-and-Technical-Testing-QASymphony-Webinar-13-2048.jpg)
![Opportunity: Contact Form doubles as Web
Site is ‘up’ checker
You received this e-mail message through your website:
reason: default
E-mail: ngjchr@somewebsitethatdoesnotexist.com
Name: ewogwah
Message: pK9ctN kfoummnkudob,
[url=http://dnaaimbzpgyg.com/]dnaaimbzpgyg[/url],
[link=http://mmkwfndaydxb.com/]mmkwfndaydxb[/link],
http://bwtjxnpecomy.com/
:
IP: 46.161.9.32
Browser: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Points: 0
Web Site Status
Join the conversation – use the hashtag #risktesting on Twitter](https://image.slidesharecdn.com/qasymphonyalanrichardsonriskfinal-160629155625/75/Risk-Mitigation-Using-Exploratory-and-Technical-Testing-QASymphony-Webinar-14-2048.jpg)
![Risk Example: Contact Form on Web Site
You received this e-mail message through your website:
reason: default
E-mail: ngjchr@somewebsitethatdoesnotexist.com
Name: ewogwah
Message: pK9ctN kfoummnkudob,
[url=http://dnaaimbzpgyg.com/]dnaaimbzpgyg[/url],
[link=http://mmkwfndaydxb.com/]mmkwfndaydxb[/link],
http://bwtjxnpecomy.com/
:
IP: 46.161.9.32
Browser: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Points: 0
Join the conversation – use the hashtag #risktesting on Twitter](https://crownmelresort.com/image.slidesharecdn.com/qasymphonyalanrichardsonriskfinal-160629155625/75/Risk-Mitigation-Using-Exploratory-and-Technical-Testing-QASymphony-Webinar-13-2048.jpg)
![Opportunity: Contact Form doubles as Web
Site is ‘up’ checker
You received this e-mail message through your website:
reason: default
E-mail: ngjchr@somewebsitethatdoesnotexist.com
Name: ewogwah
Message: pK9ctN kfoummnkudob,
[url=http://dnaaimbzpgyg.com/]dnaaimbzpgyg[/url],
[link=http://mmkwfndaydxb.com/]mmkwfndaydxb[/link],
http://bwtjxnpecomy.com/
:
IP: 46.161.9.32
Browser: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Points: 0
Web Site Status
Join the conversation – use the hashtag #risktesting on Twitter](https://crownmelresort.com/image.slidesharecdn.com/qasymphonyalanrichardsonriskfinal-160629155625/75/Risk-Mitigation-Using-Exploratory-and-Technical-Testing-QASymphony-Webinar-14-2048.jpg)
Uploaded byQASymphony
Risk Mitigation Using Exploratory and Technical Testing | QASymphony Webinar
The document discusses a webinar titled 'Risk Mitigation Using Exploratory and Technical Testing,' presented by Alan Richardson, who emphasizes the importance of understanding and managing risk in the testing process. It covers different types of risks associated with software testing, including functional and project risks, and suggests methods for identification, mitigation, and detection of these risks to enhance testing effectiveness. The content also highlights technical testing's role in addressing complexities and improving testing outcomes.
More Related Content
Similar to Risk Mitigation Using Exploratory and Technical Testing | QASymphony Webinar
Risk Mitigation Using Exploratory and Technical Testing | QASymphony Webinar
- 1. Risk Mitigation Using ExploratoryandTechnical Testing 28th June 2016 Alan Richardson – Compendium Developments Ltd Join the conversation – use the hashtag #risktesting on Twitter The audio for this webinar is delivered through your computer. There is no dial-in number. Make sure your speakers are turned up or use a pair of headphones.
- 2. HOWTOWATCHTHISWEBINAR Join the conversation– use the hashtag #risktesting on Twitter • Audio for this webinar is delivered through your computer. Make sure your speakers are turned up or use a set of headphones. • If your audio quality is choppy, it could be your internet connection. • You can customize your webinar viewing experience by increasing, decreasing or minimizing the size of the widgets on your screen. • If you have questions, enter them in the widget on the left.
- 3. • This webinarwill be recorded and available on-demand tomorrow. You will get an email when it is available. • Join the conversation on Twitter using the hashtag #risktesting • Use the Q&A widgets to ask questions during the webinar. • At the end of the webinar, you will be asked to take a short survey. HOUSEKEEPING Join the conversation – use the hashtag #risktesting on Twitter
- 4. Robust test managementplatform purpose-built to help agile teams centralize, organize and accelerate software testing ABOUT QASYMPHONY
- 5. OTHER WEBINARS &RESOURCES Join the conversation – use the hashtag #risktesting on Twitter WWW.QASYMPHONY.COM/RESOURCES
- 6. Guest Speaker: AlanRichardson • Alan has worked in Software Development for over 20 years; as a programmer, tester, test manager. As an independent test consultant he helps organisations improve their agility, technical skills and testing processes.Alan wrote the books "Dear EvilTester", "Java For Testers" and "Selenium Simplified"; he also created online training courses on technical web testing, Java and SeleniumWebDriver. • Alan blogs at EvilTester.com, SeleniumSimplified.com, and JavaForTesters.com; you can find information on his consultancy, training and conference talks at CompendiumDev.co.uk. Follow him on twitter as @EvilTester. OUR PRESENTER Speaker Headshot BRANDING OR PROMOTION CompendiumDev.co.uk Join the conversation – use the hashtag #risktesting on Twitter
- 7. Everyone is alreadyfamiliar with risk… • Differences for thisWebinar –Risk as a belief model –Risk underpins testing, so use risk »to derive and change process »to explore more »to push testing further »to become more technical Join the conversation – use the hashtag #risktesting on Twitter
- 8. Commonsense Risk • Whatis risk? –Something that might go wrong • Probability • Impact Join the conversation – use the hashtag #risktesting on Twitter
- 9. Commonsense Webinar Risks •What might go wrong – With me • What if I’m ill?What if I still have a cold and can’t talk? • What if I forget what I’m talking about? – With my broadband • What if the connection drops?What if the speed is poor? – With my computer • What if it crashes? – With the webinar system • What if it stops? • What might go wrong – With the phone? • What if it cuts out? – With the locale • What if there is a power cut? – With the content • What if I bore people? • What if they drop out? Join the conversation – use the hashtag #risktesting on Twitter
- 10. Commonsense Risk Process •Identify • Mitigate • Detect • Accept Join the conversation – use the hashtag #risktesting on Twitter
- 11. So with theWebinar… • Identify • Mitigate – Illness – sleep more, pre-record webinar just in case – Forget – presenter notes, practice – Broadband – give slides to host – Computer crash – multiple computers – Power cut – battery, UPS – Phone – landline, mobile • Accept – Boredom, Drop out • Detect – Have computer watching webinar – risk: impacts Mbps Join the conversation – use the hashtag #risktesting on Twitter
- 12. Risk Is… • Everywhere •Associated with EveryThing • Inherent in Every Process • All pervasive https://www.flickr.com/photos/britishlibrary/11065829793 Join the conversation – use the hashtag #risktesting on Twitter
- 13. Risk Example: ContactForm on Web Site You received this e-mail message through your website: reason: default E-mail: ngjchr@somewebsitethatdoesnotexist.com Name: ewogwah Message: pK9ctN kfoummnkudob, [url=http://dnaaimbzpgyg.com/]dnaaimbzpgyg[/url], [link=http://mmkwfndaydxb.com/]mmkwfndaydxb[/link], http://bwtjxnpecomy.com/ : IP: 46.161.9.32 Browser: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) Points: 0 Join the conversation – use the hashtag #risktesting on Twitter
- 14. Opportunity: Contact Formdoubles as Web Site is ‘up’ checker You received this e-mail message through your website: reason: default E-mail: ngjchr@somewebsitethatdoesnotexist.com Name: ewogwah Message: pK9ctN kfoummnkudob, [url=http://dnaaimbzpgyg.com/]dnaaimbzpgyg[/url], [link=http://mmkwfndaydxb.com/]mmkwfndaydxb[/link], http://bwtjxnpecomy.com/ : IP: 46.161.9.32 Browser: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) Points: 0 Web Site Status Join the conversation – use the hashtag #risktesting on Twitter
- 15. Risk & Opportunity •What is risk? – Something that might go wrong • Probability • Impact Opportunity for testing Join the conversation – use the hashtag #risktesting on Twitter
- 16. General Risks Relatingto Testing • The functionality might not work – “Functional Condition Risk” • There is a risk that this change might have a knock on effect in the system – “Regression Risk”, “Change Risk” Create Process to mitigate risk Join the conversation – use the hashtag #risktesting on Twitter
- 17. You probably alreadyuse risk in your testing •Business Risk •Project Risk •Functional Risk Join the conversation – use the hashtag #risktesting on Twitter
- 18. Typical Risk Modeling:Business Risks • We might run out of funding • Our requirements might be wrong • We might be hit by a regulatory requirement Less likely to be used for testing Join the conversation – use the hashtag #risktesting on Twitter
- 19. We usually meanproject and functional risk • Project Risk – We might not have enough staff – Our staff might go sick – Everyone takes holiday at the same time – Our business users don’t know the requirements – Our business users change their requirements – etc. • Functional risk – User’s can’t register on the site – The payment integration fails – The regulatory reporting fails – etc. Test Manager Test Practitioner Join the conversation – use the hashtag #risktesting on Twitter
- 20. Risk • What isrisk? –Something that might go wrong • Probability • Impact People get hung up here Join the conversation – use the hashtag #risktesting on Twitter
- 21. Priority and ProbabilityProcrastination for Project Head Person Protection http://www.slideshare.net/profmcgill/risk- analysis-for-dummies Mitigate against Beliefs and fears about being wrong Join the conversation – use the hashtag #risktesting on Twitter
- 22. Risk & Testing Jointhe conversation – use the hashtag #TBD on Twitter How does risk relate to testing?
- 23. ISTQB “Risk-Based Testing” “Anapproach to testing to reduce the level of product risks and inform stakeholders of their status, starting in the initial stages of a project. It involves the identification of product risks and the use of risk levels to guide the test process.” http://www.astqb.org/glossary/search/risk-based%20testing Join the conversation – use the hashtag #risktesting on Twitter
- 24. ISTQB Risk BasedTesting “An approach to testing to reduce the level of product risks and inform stakeholders of their status, starting in the initial stages of a project. It involves the identification of product risks and the use of risk levels to guide the test process.” http://www.astqb.org/glossary/search/risk-based%20testing Join the conversation – use the hashtag #risktesting on Twitter
- 25. ISTQB Risk BasedTesting http://www.astqb.org/glossary/search/risk-based%20testing Mitigation Detection Analysis Prioritization Derivation Join the conversation – use the hashtag #risktesting on Twitter
- 26. Risk Management &Testing • Mitigation – Do something to make the risk less likely • Detection – Find out if the risk has manifested as an issue • Analysis – Identify Risks • Prioritization – Decide which risks are more important: how bad is the impact, who is it bad for, how likely to we believe the risk to be? • Derivation – How can you test for this: make it manifest, check if it manifests, explore impact? Risk Management Testing Join the conversation – use the hashtag #risktesting on Twitter
- 27. Some Risk Classifications •Functional Risk – Relating to the functionality • function, security, performance, accessibility • System Risk – performance, security, backups, install, restore • Technical Risk – Technology involved: load balancing, libraries, protocols, platform compatibility • Non-system Related – Process Risk – Business Risk – Project Risk Based on the System Of Development Join the conversation – use the hashtag #risktesting on Twitter
- 28. Some Risk Classifications •Functional Risk – Relating to the functionality • function, security, performance, accessibility • System – performance, security, backups, install, restore • Technical Risk – Technology involved: load balancing, libraries, protocols, platform compatibility • Non-system Related – Process Risk – Business Risk – Project Risk See Related References See Related References Join the conversation – use the hashtag #risktesting on Twitter
- 29. Process Risk • System“of” Development – How we develop software – What is our process? – What are our skills? – What tools do we use? – etc. The way we develop software opens us up to different types of risk. Join the conversation – use the hashtag #risktesting on Twitter
- 30. Process Risk • System“of” Development – How we develop software – What is our process? – What are our skills? – What tools do we use? – etc. The way we develop software opens us up to different types of risk. And that is why we adopt different approaches in how we test. Join the conversation – use the hashtag #risktesting on Twitter
- 31. Process Risk Analyse Process IdentifyRisks Any issues that happen? What works what doesn’t? Change Process To… Mitigate Detect Accept Risk Join the conversation – use the hashtag #risktesting on Twitter
- 32. Every Process HasInherent Risk • “We use a very structured and traditional approach to testing” Risks: • We can’t estimate accurately in advance • Development over-runs • Testing takes too long at the end (to meet our schedule) • Testing can’t respond fast enough when requirements change • Test Cases • Test Scripts • Test Plans • Test Strategies • etc. • “We use waterfall development” & Join the conversation – use the hashtag #risktesting on Twitter
- 33. Process & CultureClash Risk • “We use a very structured and traditional approach to testing” Risks: • Testing is too slow • Testing doesn’t add value • We don’t need testing • Test Cases • Test Scripts • Test Plans • Test Strategies • etc. • “We use an Agile approach to development” & Join the conversation – use the hashtag #risktesting on Twitter
- 34. Process as aSystem Stories Conversations Code Explore Done Automate Time-boxed Join the conversation – use the hashtag #risktesting on Twitter
- 35. Process Risk Stories Conversations Code Explore Done Automate Time-boxed Miscommunication Misunderstanding, Omissions,Bugs Overcommit, Emergencies Too much to automate, wrong tools Tech Debt Too early Join the conversation – use the hashtag #risktesting on Twitter
- 36. Risk Driven Process Stories ConversationsCode Explore Done Automate Time-boxed Miscommunication Misunderstanding, Omissions, Bugs Overcommit, Emergencies Too much to automate, wrong tools Tech Debt Too early Discuss ‘test ideas’, add ideas to story Log testing done, debrief, small chunks, prioritise iteratively Early questions, but not too early Join the conversation – use the hashtag #risktesting on Twitter
- 37. Process Risks AreSystem Risks • InterconnectedTeams • Individuals • Relationships – Communication – Artefact delivery and review • Timings • Expectations, Input/Output, Contracts • Etc. “System of Development” Create Process to mitigate risk Join the conversation – use the hashtag #risktesting on Twitter
- 38. Changing Process isa Risk But if we already know it doesn’t work how can we justify not changing? Join the conversation – use the hashtag #risktesting on Twitter
- 39. Beliefs https://www.flickr.com/photos/britishlibrary/11291184996 Join the conversation– use the hashtag #risktesting on Twitter
- 40. Secondary Gain • Unrecognised‘benefit’ • e.g. Smoking • -> Main Risk -> I might die • Secondary Gain – I get to take breaks outside – I get to chat and socialise – I have stress relief breaks • Secondary Gain means I might not stop smoking, even if I try. https://www.flickr.com/photos/britishlibrary/11103578275/ Join the conversation – use the hashtag #risktesting on Twitter
- 41. Hypothetical Examples ofSecondary Gain • Risk keeps us in business • Process risk justifies our ‘standard’ • Not enough time means we never have to finish • Not enough time means we don’t have to learn • Secondary Gain is a massive risk to change – Identify secondary gain – and change your attitude to it Join the conversation – use the hashtag #risktesting on Twitter
- 42. Testing must notbe limited by our beliefs • What do I think could go wrong? –Options are limited by our model of the world –5Whys questioning specifically targets beliefs. –What Else? –Systems Analysis Join the conversation – use the hashtag #risktesting on Twitter
- 43. How does “risk”lead to exploratory testing • I believe – The more complicated a system the more risk that something can go wrong – We want to simplify the ‘process’ as much as we can Join the conversation – use the hashtag #risktesting on Twitter
- 44. How does “risk”lead to exploratory testing If you had no test process and designed one based on risk: I don’t know how to test it What is it supposed to do? Who is going to use it? What data does this process? Join the conversation – use the hashtag #risktesting on Twitter
- 45. How does “risk”lead to exploratory testing If you had no test process and designed one based on risk: I don’t know how to test it What is it supposed to do? Who is going to use it? What data does this process? Risk: We don’t know if it works. Risk: It might not function. Risk: It might not meet user need. Risk: It might not handle input Join the conversation – use the hashtag #risktesting on Twitter
- 46. How does “risk”lead to exploratory testing • Then we would improve the process by looking at other risks: – Risk that we haven’t tested enough • Agree high level conditions, review the conditions before we start, review the work – Risk that we can’t tell people what we did • Learn to take notes, communicate what we do, collate reports in a searchable form – Risk that we can’t plan it because we don’t know what we’ll test • agree a time constraint, work in small chunks, prioritise coverage, adjust based on review of the output – etc. Join the conversation – use the hashtag #risktesting on Twitter
- 47. Basic System Login WebPage <-> HTTP Server <-> DB with user details HTTP Server User Details Database Join the conversation – use the hashtag #risktesting on Twitter
- 48. Risk: Basic AcceptanceCriteria is not enough • A user must correctly fill in their username and password on the website before they login and access the system – User Exists, Password correct • user logged in – User Exists, password wrong • user not logged in – User does not exist, password meets valid criteria • user not logged in High Level Acceptance Criteria Join the conversation – use the hashtag #risktesting on Twitter
- 49. Mitigate risk ofmissing Acceptance Criteria • We would ask for additional information about requirements and acceptance criteria. – How often can a user try to login? – What if user is already logged in? – What error messages displayed? • For getting password wrong • When user does not exist • If username blank • If password blank • etc. Acceptance Criteria Nuances & Details & some technical implementation details Join the conversation – use the hashtag #risktesting on Twitter
- 50. Mitigate limited coverageof business domain to cover web page structure and platforms • Non-domain input – Username and password are text fields • how much text can they handle? maxlength=’20’, JS validation • Unicode chars? JS validation of valid chars • Drag files in? • URLs • Special chars • Injection payloads • Etc. • Platform concerns – Browser Compatibility, JavaScript Technical implementation details and platform risks. Join the conversation – use the hashtag #risktesting on Twitter
- 51. What is TechnicalTesting? Testing informed by a technical understanding of the system. • Not programming. Not automating. • Technical knowledge Applied toTesting Join the conversation – use the hashtag #risktesting on Twitter
- 52. Let’s Build aSystem Technical Model HTTP Server User Details Database • failedLoginCookie & JavaScript (disable login) • JS Validation of username password: • Chars • length Join the conversation – use the hashtag #risktesting on Twitter
- 53. Technical Testing Model •failedLoginCookie & JavaScript (disable login) • JS Validation of username password: • Chars • length • What if user disables cookies? • What if user amends cookies? • What if JavaScript disabled? • What if JavaScript amended? • What if maxlength html changed? Join the conversation – use the hashtag #risktesting on Twitter
- 54. Technical Testing Skills •failedLoginCookie & JavaScript (disable login) • JS Validation of username password: • Chars • length • What if user disables cookies? • What if user amends cookies? • What if JavaScript disabled? • What if JavaScript amended? • What if maxlength html changed? • What browser is JS compatible with? Do we have the technical knowledge to: • Spot the technical risks around reqs • Identify the ‘what if’ risks • Know how to manipulate JS, HTML, and Cookies 1. HTML 2. Cookies 3. How to disable JavaScript 4. Multiple Browsers 5. Browser Dev Tools 6. How to write JavaScript 7. Use the JavaScript Console 8. Intercept and manipulate the source through a proxy Join the conversation – use the hashtag #risktesting on Twitter
- 55. System Model Technical risks. Risk that weignored HTTP transport layer and server communication What Risks are there from technical knowledge of HTTP and Server? • JavaScript and Server side validation use different rules • Server side does not implement max failed logins 10 times • Server side max login count is tracked separately from client count • Server side can’t handle form field input values > 20 • ‘massive’ input values cause server to crash • Invalid form details are not processed correctly • Submitting form to different end point causes problem • Adding basic-auth headers fools system • etc. Join the conversation – use the hashtag #risktesting on Twitter
- 56. Do we havethe technical knowledge to identify these risks and build this model and explore it? Risk that we ignored HTTP transport layer and server communication What Risks are there from technical knowledge of HTTP and Server? • Risk that the JavaScript and Server side validation use different rules • Risk that the server side does not implement max failed logins 10 times • Risk that the server side max login count is tracked separately from client count • Risk that server side can’t handle form field input values > 20 • Risk that ‘massive’ input values cause server to crash • Risk that invalid form details are not processed correctly • Risk that submitting form to different end point causes problem • Risk that adding basic-auth headers fools system • etc. 1. HTTP 2. Observe HTTP Traffic (proxies or dev tools) 3. Manipulate and send HTTP form submission without GUI using Proxies 4. Access to server logs 5. Telnet, SSH Join the conversation – use the hashtag #risktesting on Twitter
- 57. How did weget to this? Structure of Technical System Platform & Input Common DomainReqs Join the conversation – use the hashtag #risktesting on Twitter
- 58. What are therisks of doing this? • we don’t have the skills • we don’t have the inclination • our staff don’t want to learn • we don’t have the time to learn • we do technical stuff and ignore the ‘requirements’ • we don’t have the tools • we are not allowed to use the tools • we can’t ‘sell’ this to our managers We have to decide if these are important enough to mitigate Join the conversation – use the hashtag #risktesting on Twitter
- 59. What are therisks of not doing this? • Risk that we miss entire areas of errors in our testing. • Risk that no-one reviews the system at this level of technical details. The errors that can slip through, can be system threatening. The easiest place to do this type of testing is through exploratory testing. Join the conversation – use the hashtag #risktesting on Twitter
- 60. How can wedo this? • You can use all the various mnemonics and ‘heuristics’ that are out there, to expand your analysis of the system. – http://www.qualityperspectives.ca/resources_mnemonics.html • Work from ‘first principles’ – Build system and technical models – Analyse the model for gaps and risks • Both require you need to increase your technical knowledge: – To work from first principles to build a model and identify gaps in your knowledge and identify risks – To gain maximum value from the mnemonics because they help you explore your model Join the conversation – use the hashtag #risktesting on Twitter
- 61. Simple decisions • Areyou prepared to increase your technical knowledge? • Are you prepared to put in the time and effort to learn more? – You /Your Company /Your Manager /Your Project Join the conversation – use the hashtag #risktesting on Twitter
- 62. You don’t haveto know everything If learn in small chunks, you apply what you learn, during your testing, then you will keep learning and keep your knowledge up to date. Join the conversation – use the hashtag #risktesting on Twitter
- 63. My High LevelGuide • Model – Model what you know.This will help you identify gaps. • Observe – How can you observe technical details? • Reflect – Think about gaps in the model, risks, issues, capabilities. • Interrogate – How can you drill deep into the information and system? • Manipulate – How can you interact with it at a technical level. Join the conversation – use the hashtag #risktesting on Twitter
- 64. Warning: Risks • Youwill test slower when you are learning • You will be more uncertain because you are expanding your model • You might raise false flags because you misunderstand what you are seeing • You will go down rat-holes that lead nowhere • You will spend time evaluating tools Join the conversation – use the hashtag #risktesting on Twitter
- 65. Hints • You willtest slower when you are learning – But you will speed up when you are more proficient • You will be more uncertain because you are expanding your model.You might raise false flags because you misunderstand what you are seeing – But you will learn to understand what you are seeing • You will go down rat-holes that lead nowhere – Time-box investigations, the same with exploratory testing • You will spend time evaluating tools – Don’t evaluate them in isolation. Use them on the project. Join the conversation – use the hashtag #risktesting on Twitter
- 66. Yeah, but seriously,I’m a manager… • I’m in meetings all day • I nod when my staff tell me stuff • If it isn’t an email or a word processor or a spreadsheet, I don’t open it Join the conversation – use the hashtag #risktesting on Twitter
- 67. I manage seriously… Itis always an individual’s choice to improve their technical skills. But a manager’s job is to manage risk.They can decide to take action to mitigate the risk that there are gaps in testing caused by a lack of technical focus regardless of their technical knowledge. Join the conversation – use the hashtag #risktesting on Twitter
- 68. Start to End •We test systems to the level that we understand them enough to observe their behaviour and compare it to our model of how we think it should behave. • We test systems at the places where we can manipulate them. • We test systems to the level that we can interrogate them to understand the data that they process and produce. Join the conversation – use the hashtag #risktesting on Twitter
- 69. End to End Jointhe conversation – use the hashtag #TBD on Twitter • Expanding our technical knowledge expands: – Our models – Our ability to observe – Our ability to reflect on gaps and risks – Our ability to interrogate the system – Our ability to manipulate the system – Our ability to test
- 70. End to End •Expanding our technical knowledge expands: – Our models – Our ability to observe – Our ability to reflect on gaps and risks – Our ability to interrogate the system – Our ability to manipulate the system – Our ability to test And the risk of not doing that, is not one I’m prepared to take. Join the conversation – use the hashtag #risktesting on Twitter
- 71. Q&A Questions? Join the conversation– use the hashtag #risktesting on Twitter
- 72. Thank you Join theconversation – use the hashtag #risktesting on Twitter
- 73. Related Resources • http://www.developsense.com/blog/category/risk/ •http://www.slideshare.net/profmcgill/risk-analysis-for-dummies • http://www.astqb.org/glossary/search/risk • Heuristic Risk BasedTesting http://www.satisfice.com/articles/hrbt.pdf • http://www.satisfice.com/blog/archives/category/risk-analysis • https://www.cmcrossroads.com/sites/default/files/article/file/2014/A%2 0Risk-Based%20Test%20Strategy.pdf • http://kaner.com/pdfs/QAIRiskBasics.pdf • https://en.wikipedia.org/wiki/Risk • http://www.qualityperspectives.ca/resources_mnemonics.html Join the conversation – use the hashtag #risktesting on Twitter