DZone
DevOps Zone
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
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > DevOps Zone > Test Better, Test Faster, Test Smarter

Test Better, Test Faster, Test Smarter

How do you balance the need to “go fast” with the need to test everything and deliver high-quality software?

Anders Wallgren user avatar by
Anders Wallgren
·
Apr. 20, 16 · DevOps Zone · Opinion
Like (2)
Save
Tweet
3.05K Views

Join the DZone community and get the full member experience.

Join For Free

economics

with applications the driving force in today’s economy, the quality and release cadence of your software are critical to your business and your bottom line. you want to get software updated in the hands of your end users as quickly as possible. however, even the fastest release cycle wouldn’t make a difference if your product ends up being buggy or malfunctioning, resulting in a bad user experience or service interruption.

i want to take a look at one of the most important (if not the most important) aspects of the software delivery process: testing! as software teams become more mature in their implementation of devops and continuous delivery to streamline their software delivery, testing takes a central role as a prerequisite to these practices.

you need to have testing on your mind from the very beginning, and plan your testing as part of the initial stages of designing your software — mapping your test procedures, infrastructure configuration and acceptance criteria. as you design and develop your app, you also need to think about how you’re going to test it. the more testing is on your mind, the more you’ll have a solid understanding of what you need to test, what’s the definition of “done,” and the faster, more streamlined, your overall process will be.

for my recent article on devops.com , i review four questions every development or qa team should consider when planning their testing, as they try to balance quality with speed — managing and accelerating their testing, while ensuring a reasonable time-to-market.

  1. how much testing is enough?
  2. what kind of testing should you invest in?
  3. how can you make testing faster?
  4. where do you start if you want to make sure all your builds are green?

read the full article for tips for planning your testing, and 12 best practices for improving your testing processes.

Testing

Published at DZone with permission of Anders Wallgren, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • You Are Blind to the Risks in Your Cloud — Why Companies Need Cloud Security Monitoring
  • It's Official! Fat Arrows in JavaScript!
  • Observability Tools Help Catch Application Failures — But Automating the Observer Is Becoming Crucial
  • Testing Strategies for Microservices

Comments

DevOps Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • 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:

DZone.com is powered by 

AnswerHub logo