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
Code on a computer screen Testing a Software Rewrite

Suppose we’re looking at a system rewrite where the stakeholders have none of the original engineering documentation. (This isn't surprising; documentation becomes obsolete—or even misleading—as the system changes, and corresponding docs don't get updated.) What can we do? Here are some tactics to use—and risks to anticipate—when testing a system rewrite.

Steve Poling
Arrow pointing left Shifting Testing Left Is a Team Effort

There is a lot of talk in the testing world about shifting left. Basically, “shift left” refers to moving the test process to an earlier point in the development process, independent of the development approach. This article explores a case in which shift-left has been applied, and the lesson is that shifting left cannot be achieved by testers alone—it must result from a team effort.

Monitoring dashboard with criteria set up Solving Production Issues Using Testing Tools

Standard web-monitoring tools can ping webpages and verify that they’re responding, but they don’t alert you to an issue. But you can use the technology in load testing to monitor your sites by running an interactive script that can detect issues and generate emails as needed. It runs constantly like a silent sentry, never sleeping or taking a vacation, improving your sites' reliability.

Nels Hoenig

Better Software Magazine Articles

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
The Unspoken Truth about IoT Test Automation The Unspoken Truth about IoT Test Automation

The internet of things (IoT) continues to proliferate as connected smart devices become critical for individuals and businesses. Even with test automation, performing comprehensive testing can be quite a challenge.

Rama Anem
Test-Driven Service Virtualization Test-Driven Service Virtualization

Because enterprise applications are highly interconnected, development in stages puts a strain on the implementation and execution of automated testing. Service virtualization can be introduced to validate work in progress while reducing the dependencies on components and third-party technologies still under development.

Alexander Mohr
testing Adopt an Innovative Quality Approach to Testing

How much testing is really enough? Given resources, budget, and time, the goal of comprehensive testing seems impossible to achieve. It’s time to rethink your test strategy and start innovating.

Rajini Padmanaban

Interviews

Alon Eizenman Testing with the Lights On: An Interview with Alon Eizenman
Video

In this interview, Alon Eizenman, the CTO and cofounder at SeaLights Technologies, discusses his many experiences with startup companies, how software teams are adapting to the current demand for speed, and why you need data before you take testing actions.

Jennifer Bonine
Hans Buwalda Bigger and Better Test Design through Automation: An Interview with Hans Buwalda
Video

In this interview, LogiGear's Hans Buwalda explains how better test design can lead to improved test automation and can make the difference between automation success and failure. He details why successful automated testing is a test design challenge, not a technical challenge.

Jennifer Bonine
Mike Faulise discusses Continuous Integration and Test Automation STAREAST 2015 Interview with Mike Faulise on Continuous Integration and Test Automation
Video

In this interview from STAREAST 2015, TapQA's Mike Faulise goes into detail on continuous integration and continuous delivery, the required technical skills needed to implement these methods, and how automation is embedded today.

Jennifer Bonine
Jonathan Cooper discussing API testing and context-driven software testing All About API Testing: An Interview with Jonathan Cooper

In this interview, Jonathan Cooper, a principal quality engineer for the ExactTarget Marketing Cloud, sits down to talk about various aspects of API testing, the difference between SMS and push notification, and why he is a proponent of the context-driven methodology of software testing.

Cameron Philipp-Edmonds

Conference Presentations

STARWEST 2018 Testing In The Dark
Slideshow

Isn’t it amazing? Stakeholders drop software on our desks and expect us to test it—without any requirements, design, or product knowledge whatsoever. About the only clear thing is the absurd and unrealistic deadline. We are expected to bend over backward, spread magic pixie dust, and heroically test quality into a product we have never heard of before. But testing in the dark is not impossible, and as Rob Sabourin shows, it can even be a very valuable and fun experience. Learn strategies to emerge from a murky fog into clear, meaningful quality insights and leverage unlikely sources about what stakeholders care about and what users really need the software to do. Rob introduces you to methods of reconnaissance-style, charter-driven, and session-based exploratory testing and help you provide meaningful estimates to stakeholders with minimal hard information about the software under test.

Rob Sabourin
STARWEST 2018 7 Fundamentals of a Successful Testing Team
Slideshow

You want to build an effective testing team, but you’re asking yourself, “Where do I begin?” Greg Paskal, a quality assurance engineer with over thirty years of testing experience, shares seven keys to building a successful testing team. Learn the fundamentals every tester should know and how to build upon them to achieve an effective manual and automated testing strategy. Greg’s minimal essential testing strategy (METS), coupled with his proven experience, will help you build an amazing testing organization. Greg will provide specific instruction through each of these seven areas, including fundamentals of software testing, how to begin implementing and executing the METS manual test strategy, outfitting your manual test team with automated testing, and the importance of building strategic partnerships across your IT and technology organization.

Greg Paskal
Better Software West 2018, Agile Dev West 2018, DevOps West 2018 Engineering Productivity and Enterprise Quality at Scale
Slideshow

Over the past two years, PayPal has been on a journey to modernize its internal development and test systems, from test environments, implementing enterprise continuous integration and code propagation into the development pipeline, to release processes and production code validation. Jose Buraschi and Nir Szilagyi will talk about transforming the code of 5,000 developers across 350 teams and how it required social “magic” to influence behaviors and motivate engagement. This modernization of PayPal's development practices has involved creating reliable integrated test environments, continuous integration, automated code propagation, and automated validation before each deployment. Instead of asking for a list of things developers need to do differently, Jose and Nir asked for simple changes that, through side effects, led to the desired results.

Nir Szilagyi
Agile Dev West 2018, Better Software West 2018, DevOps West 2018 Things Are Broken: A Case Study In Moving Too Fast
Slideshow

"Move fast and break things” tells quite a story of the relationship between speed and agile. Speed has been a driver in our industry before it was even an industry. Books promise that certain frameworks can deliver twice as much in half the time, yet teams still struggle delivering what's expected of them. This session describes a six-month case study of a multi-team transformation. The orders were to make the teams deliver faster, but they were consistently missing deadlines. Frustration was on the rise. Only after taking the time to understand what they meant by "faster" could the teams improve—and the solution ended up being to slow down. Chris Murman will help you learn how to make the case to slow down, work in increments, deliver frequently, and delight customers. He will explain which metrics to use to measure progress, patterns of successful teams, and the necessary coaching stances.

Chris Murman

CMCrossroads is a TechWell community.

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