In an automation training program I put together, introduced folks to learn about risk based testing.<\/p>\n

While there is a lot that can be said about it, here are two main types of risk assessments:<\/p>\n

Inside out risks:<\/p>\n

– Look at how different components across your tech stack interact with each other<\/p>\n

– Walk through the control structure (#STPA<\/strong> could be good tool) and highlight risks<\/p>\n

Outside in risks:<\/p>\n

– How your customer sees your application, from the outside in, the behavior of the application<\/p>\n

– This is what usually testers are more focused on<\/p>\n

It’s important for automation engineers to be good testers first, and therefore practice ‘testing well’<\/p>\n

I am also perturbed when testers are unwilling to do ‘inside out’ risk assessment, IMHO mostly that’s due to lack of willingness to get into technical details.<\/p>\n

Reference links in comments<\/p>\n

#RSQ<\/strong> #Testing<\/strong> #RiskBasedTesting<\/strong> #RBT<\/strong><\/p>\n

Risk based testing: https:\/\/www.satisfice.com\/download\/heuristic-risk-based-software-testing<\/strong><\/a><\/p>\n

STPA: http:\/\/psas.scripts.mit.edu\/home\/wp-content\/uploads\/2014\/03\/Systems-Theoretic-Process-Analysis-STPA-v9-v2-san.pdf<\/strong><\/a><\/p>\n<\/div>