Articles

Please enter an article title, author, or keyword
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
Arrow pointing to the right Shifting Right Offers New Possibilities for Agile and DevOps Teams

The shift-right concept originates from testing. But agile and DevOps teams also can use it to improve their systems and service to the client. However, there is a complicating factor: Different people have different explanations for what shifting right is. Let’s look at the different forms of shifting right, what the potential benefits are, and who should ideally be involved in your shift-right process.

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
Gearbox for a car with a manual transmission Shifting Your Testing: When to Switch Gears

Shifting your testing either left or right can meet different needs and improve different aspects. How do you know whether to make a change? Let your test cycles be your guide. Just like when driving a car with a manual transmission, if the engine starts to whine or you’re afraid you’re about to stall out, switching gears may be just what you need.

Maximilian Bauer's picture Maximilian Bauer
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
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
Branching example Picking the Right Branch-Merge Strategy

A good branch-merge strategy facilitates processes among multiple developers and is the basis for any well-functioning DevOps pipeline that uses continuous integration. Let’s explore branching strategies, merging strategies, and how you can put them together in a way that’s right for your team in order to bring quality features to production faster.

Alan Crouch's picture Alan Crouch
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's picture Steve Poling
Circle made of arrows Why You Need Continuous Testing in DevOps

DevOps is more than adopting the right set of tools; it's a cultural shift that incorporates testing at each stage of the agile project lifecycle. Continuous testing is key to unlocking this culture change because it weaves testing activities into every part of the software design, development, and deployment processes, which helps everyone involved communicate more, collaborate better, and innovate faster.

Tom Alexander's picture Tom Alexander

Pages

Upcoming Events

Apr 19
May 03
Jun 07
Oct 04