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

What We Can Learn From Software Failures

Tricentis partnered with DZone for a webinar on stopping software failures. Read on for insights and the full webinar.

Chelsea Frischknecht user avatar by
Chelsea Frischknecht
CORE ·
Nov. 19, 18 · Presentation
Like (1)
Save
Tweet
Share
4.75K Views

Join the DZone community and get the full member experience.

Join For Free

Software failures happen every day. You've probably experienced a software failure in the past week, or even days — fails as simple as an app glitching on your smartphone to serious ones like canceled flights or crashing infrastructure systems. Software bugs have become so ubiquitous to everyone's lives that it would be easy to simply roll our eyes and sigh, "here we go again..." But if software professionals do that, we miss a valuable opportunity to learn.

A software failure is an invitation to explore. The fact that a bug is occurring means that there is something we can learn about our software, which will in turn, improve our future software. DZone and Tricentis recently partnered up to explore this very topic in a webinar titled "How You Could Stop Top Software Fails", featuring panelists from a variety of backgrounds and perspectives: Tricentis' Distinguished Evangelist Ingo Philipp, Senior Software Test Consultant and Trainer, Sue Atkins, Tricentis' Director of Engineering, Michael Niessl, and Flood's Performance Testing Consultant, Nicole van der Hoeven.

In the webinar, the panellists discussed the biggest software bugs they have encountered professionally, and more importantly, how to learn from them. As they observed, while each software bug likely has a complex history — how it got there, why it wasn't discovered before it appeared in production, etc. — we can learn a lot by extrapolating the larger themes that connect all these software bugs together.

For example, how can developers keep up with the constantly increasing gap between software complexity and the speed at which the software is being developed? At the end of the day, that is one of development's biggest challenges: supporting rapid innovation while maintaining a high level of quality. One of the ways to do that is through using Microservices - ie: releasing software in smaller and smaller packages, each of which has minimal impact on the functionality of the larger system. These tiny bits of software may have just one function, but they execute their one function really well and they can be updated frequently with minimal risk.

Another question that should be addressed is, what do software testers need to change to keep pace with the ever-changing software world? One skill that is crucial for a tester is the ability to prove and demonstrate the relevance and value of their work. It is unfortunately quite common in an organization for testing to simply be shoved to the side or undervalued. In those environments, testers need to stand up for themselves, highlighting their specialized skills and unique perspectives to demonstrate the value that they bring to their organization. Large, public software fails can be useful in that sense because testers can use them as internal case studies to bring the topic of software testing back to the forefront of the organization's attention.

Studying software failures inevitably raises the question, "Where is software and software testing headed?" One theory comes in the form of SDETs — Software Development Engineers in Test. Some even say that testing as we know it today will cease to exist and become "Optimising Engineering Productivity". Is that actually realistic? As long as organizations agree that software quality has value, software testing will never go away. What will change, however, is how software testing is conducted. The age of testing being a bookend to development, where testers manually follow step-by-step execution lists, is ending. The reality is that there is a need for testing in every stage of the development process. The idea that you can "bake quality in" to development with strategic testing is one of the practices that will be instrumental in stopping epic software failures and crashes in the future.

Want to hear more? List to the full webinar panel discussion on-demand here.
Software development

Published at DZone with permission of Chelsea Frischknecht, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Playwright vs. Cypress: The King Is Dead, Long Live the King?
  • DevSecOps Benefits and Challenges
  • Exploring the Benefits of Cloud Computing: From IaaS, PaaS, SaaS to Google Cloud, AWS, and Microsoft
  • Best Practices to Succeed at Continuous AWS Security Monitoring

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: