Articles

Graph showing how testing earlier costs less and means fewer overall defects The Shift-Left Approach to Software Testing

The earlier you find out about problems in your code, the less impact they have and the less it costs to remediate them. Therefore, it's helpful to move testing activities earlier in the software development lifecycle—shifting it left in the process timeline. This article explores the shift-left methodology and how you can approach shifting left in your organization.

Arthur Hicken's picture Arthur Hicken
QA Is More Than Being a Tester QA Is More Than Being a Tester

QA testers often take on more of a role than just testing software code. When the team needs help, QA should lend a hand in assisting with business analysis, customer communication, user experience, and user advocacy.

Amanda Perkins's picture Amanda Perkins
Icons showing test optimization 5 Ways to Optimize Tests for Continuous Integration

Many teams have existing automated test suites that are not included in a continuous integration program. Maybe the tests take too long to execute, or they are not reliable enough to give accurate results. Here’s how to assess your test suites in terms of value added and time to execute, along with five proven strategies to optimize those suites for CI.

John Ruberto's picture John Ruberto
Agile DevOps East Continuous Testing Is Not Test Automation
Slideshow

The DevOps movement is front and center across enterprises. Companies with mature systems are breaking down siloed IT departments and federating them into product development teams and departments. Testing and its practices are at the heart of these changes, so companies are turning to continuous testing with the hopes that they can automate their way through the testing bottleneck by focusing on automating regression tests. But this strategy is failing. Adam Auerbach will explain why he thinks that is, what true continuous testing looks like, and how continuous testing should be implemented. Adam will demonstrate that to keep pace with development in the new “you build it, you own it” environment, testing teams and individuals must develop new technical skills and even embrace coding to stay relevant and add more value to the business.

Adam Auerbach
STARCANADA Mobbing for Test Design: Connecting with Your Colleagues’ Test Ideas
Slideshow

Do you have trouble generating test case ideas? Are there seemingly obvious bugs getting through your test plan? Are you considering revamping your current test analysis and design? If you answered yes to any of these questions, then this session is for you. You may have heard of mob...

Jeff MacBane
STARCANADA Testing at 43,000 Feet: Reporting Risk That Matters
Slideshow

Testing dashboards can give stakeholders the false impression that projects are under control. But are they really? As a tester, you can see a counter indicating a high percentage of passing tests but know that you may still have critical failures in the product. Alexandre Bauduin will...

Alexandre Bauduin
STARCANADA Ditch Your Bug-Tracking Tool: 3 Solid Tactics to Minimize Bug Counts
Slideshow

A bug-free product release is an ideal that testers, developers, and project managers strive for, but when it comes to the go/no-go decision, the balance is often struck between "good" and "good enough," leaving behind a rotting to-do pile in the bug-tracking tool that is rarely acted upon...

Jerry Penner
STARCANADA Gaining Consciousness
Slideshow

Testers make difficult decisions with minimal information in turbulent times on critical projects.  Independent consultant, Fiona Charles, suggests that testers must learn to draw a line in the decision-making process between trained intuition and careless assumption.  In this...

Fiona Charles
Fighting Test Flakiness: A Disease that Artificial Intelligence Will Cure
Slideshow

Artificial Intelligence (AI) is making it possible for computers to diagnose some medical diseases more accurately than doctors. Such systems analyze millions of patient records, recognize underlying data patterns, and generalize them for diagnosing previously unseen patients. A key challenge is determining whether a patient's symptoms and history are attributed to a known disease or other factors. Software testers face a similar problem when triaging automation failures. They investigate questions like, Is the failure due to a defect, environmental issue, or nondeterministic test script? Is there current or historical evidence to support one belief over another? Join Tariq King as he describes how test failures and flakiness can be modeled for machine learning (ML) as causal disease-symptom relations.

Tariq King
Engineering for Compatibility
Slideshow

Modern software development has brought us an incredibly powerful tool: continuous integration and deployment. However, taking advantage of this new system isn’t always straightforward. With powerful new tools come powerful new ways of making mistakes that can take your product down in a heartbeat. Melissa Benua has years of experience making CI and CD work for her, with lots of insights—both good and not so good. Come and learn from her as she shares key tips and tricks for coding and testing for both forward and backward compatibility in software releases. Useful for both traditional testers as well as combined engineers, Melissa provides technical and actionable advice to enable your team to make the right trade-offs and the right time investments, allowing your product to release to your customers safely and successfully.

Melissa Benua

Pages

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.