DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. Testing, Tools, and Frameworks
  4. Risk-Based Testing [Podcast]

Risk-Based Testing [Podcast]

See how risk moves across projects and products.

Joel Montvelisky user avatar by
Joel Montvelisky
·
Dec. 13, 18 · Presentation
Like (2)
Save
Tweet
Share
7.94K Views

Join the DZone community and get the full member experience.

Join For Free

Joel Montvelisky, Chief solution architect at PractiTest – test management tool, and Rob Lambert, Director of cultivated management, a tech consulting company with today’s topic: Risk-based testing.

  • In the software development world, and specifically in testing, we are constantly trying to figure out where should we spend our time. With the basic understanding that we can’t test everything, we need to decide what are we going to test. This is where risk-based testing enters the picture.
  • A risk is something that threatens the delivery of value to the customer. It’s something that might go wrong. There are two types of risks:

Product risk – basically equals bugs, a functionality that doesn’t work as planned.    

Project risk – missed targets. Can be time targets or cost targets.

  • Another possible risk is the people risk. If people feel their job is on the line, they might take actions that are counterintuitive to the project. People can avoid taking innovative and intuitive actions because of the risk for their careers.  
  • The idea for testing as a risk mitigator is seeing in which areas issues might occur, and focus the testing on these areas.
  • If you are a risk manager, you need to manage each one of your risks separately: Schedule a date to approach a risk by deciding when is it going to be an appropriate time to handle it.

Dictate what is the potential damage arising from the risk – if it comes true, what would be the cause.

Probability – what chances are there for the risk to become true.

What Actions Can You Take to Avoid That Risk?

Continuous suppliance – if the risks happen, what should you do.

  • Brainstorming can be a good way to decide what are the risks you are facing in your project.
  • You can identify potential risks by consulting an external source (developers for example), dig into historical data or by using your common sense.
  • Use tools like New Relic or logz.io to identify potentially risky areas.
  • Run smoke tests and focus on failed steps to discover further risks.
Risk-based testing

Published at DZone with permission of Joel Montvelisky, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • What Is Policy-as-Code? An Introduction to Open Policy Agent
  • Apache Kafka vs. Memphis.dev
  • Web Application Architecture: The Latest Guide
  • Secrets Management

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: