Articles

Brain made of computer circuits and binary code A Simpler Way of Using Machine Learning to Shift Testing Left

The advantages of shifting left and testing as early as possible are obvious. But as you automate more testing, the test suite grows larger and larger, and it takes longer and longer to run. Instead, just automate the process of finding the right set of tests to run. The key to that is machine learning. This isn't AI bots finding bugs autonomously without creating tests; this is a different way to use machine learning, and it’s far simpler.

James Farrier's picture James Farrier
Pyramid in Egypt Inverting the Test Automation Pyramid

A growing company was tasked to develop a test automation program from scratch, change its coding practices, and build a continuous testing toolchain. Martin Ivison details how they did it, including realizing that implementing the traditional test pyramid wasn't going to work—it would have to be turned upside down. They found out that small is beautiful, cheap is good, and cultural change matters.

Martin Ivison's picture Martin Ivison
Computer screen showing clean code Clean Coding Practices for a Scalable Test Automation Framework

Many organizations are looking to expand their automation abilities by designing and developing test automation frameworks. However, we often abandon good coding practices in favor of working as fast as possible. We need to treat this project like any other application development project. Here are three of the most important clean coding practices to keep in mind in order to make a scalable test automation framework.

Sumon Dey's picture Sumon Dey
Infinity symbol with test automation gear incorporated Test Everywhere: A Journey into DevOps and Continuous Testing

A move to DevOps creates an opportunity to shift the testing process to the left. But what if you went further? DevOps supports continuous testing, so you can advocate for a constant focus on quality, with testing permeating the entire software development process. Here's how you can actually have a faster testing process when the software is tested throughout the lifecycle, by developers, testers, and automation alike.

Metal gears 6 Steps for Succeeding with Test Automation in Agile

Lots of test automation efforts in agile software development fail, or at least do not maximize their potential. This article looks at two main reasons test automation may not live up to the expectations that testers and other stakeholders in the agile development process have, then outlines six steps to avoid falling into these traps. Here's how to succeed with test automation in an agile environment.

Bas Dijkstra's picture Bas Dijkstra
Integration overview path Who Should Set Up Continuous Integration for Automated Tests?

If you want to trigger long-running, end-to-end automated tests, you must integrate the test execution system with the continuous integration system. But this job falls in a fuzzy area that meets at the nexus of feature development, test automation development, quality assurance, and build and release engineering. Here's how to decide who should be responsible for the setup.

Ajeet Dhaliwal's picture Ajeet Dhaliwal
Four yellow pipes Continuous Delivery Is Not a Pipeline

Pretty much everything you hear about DevOps mentions “the pipeline.” Continuous delivery is not really about the pipeline, however. Continuous delivery is about two things: testing strategy and branching strategy. The pipeline is important; it is an integral part of DevOps. However, the central element is the practice of testing continually using automated tests.

Clifford Berg's picture Clifford Berg
Power button Simplify Continuous Operation Tests with a Periodic Reboot

Continuous operation tests find important bugs, partly as a result of their long operation and partly by increasing the probability of finding statistical bugs. However, CO tests have their own downsides. Mandating a periodic reset or reboot can work around these issues, as well as save time and cost for testing, reproduction, debugging, and fix verification.

Michael Stahl's picture Michael Stahl
Testing feedback loop 5 Key Factors to Achieve Agile Testing in DevOps

Part of the path to DevOps requires adoption of agile methodologies. What does it mean for testing when you switch from the traditional waterfall model, with a few long release cycles per year, to the agile model, with changes occurring every two weeks? Here are five key factors to achieve the agile software testing necessary in DevOps.

Denise Rigoni's picture Denise Rigoni
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

Pages

CMCrossroads is a TechWell community.

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