banner-649x60

Tag Archives: continuous delivery

Letter From The Editor

By Michael Hackett, LogiGear Corporation

DevOps can be a big scary thing. Culture change, constant collaboration— whatever that means— a big new set of tools… it’s a lot. What most teams want is to have a smooth running software development pipeline. I have stopped using the phrase “DevOps,” and now I say “Continuous Delivery.” There are many reasons for this.

Facebooktwittergoogle_plusredditpinterestlinkedinmail

Mega Trends in Testing: Continuous Delivery, Production Line and the Deployment Pipeline

DevOps may be the next big buzzword, but Test teams really need to focus on its little sister, Continuous Delivery

By Michael Hackett, LogiGear Corporation

If you pay attention to trends in software development—from the perspective of what some sophisticated teams are doing, what articles and books are being written, to conference topics, you may have noticed the tools being developed— there have been transformations in the past decade:

Facebooktwittergoogle_plusredditpinterestlinkedinmail

Free Delivery: 5 Things Amazon Prime Taught Me About Deployment Automation

Eric Minick brilliantly demonstrates how automation works in Continuous Delivery using this real-world “case study”.

By Eric Minick, IBM

As a product manager at IBM working on our UrbanCode products, I think a lot about Continuous Delivery, how to do it and what it does for teams. Continuous Delivery techniques enable teams to deliver software faster and with less risk. The ideal in continuous delivery is for a developer to push a code change, and have that change rapidly built and tested. Minutes later, the code should either be rejected as having a rejection, or be available to be released into production. Needless to say, most teams are still working towards that ideal.

Facebooktwittergoogle_plusredditpinterestlinkedinmail

3 Ways to Get in Shape for Continuous Testing

Making the leap to CT is easier than you think— follow this guide to transform your testing process

By Alex Martins, CA Technologies

No pain, no gain! Achieving Continuous Testing shouldn’t take a “Hans and Franz” attitude. It should be painless, more like a natural progression from implementing certain practices over time.

Facebooktwittergoogle_plusredditpinterestlinkedinmail

Introducing TestArchitect Team!

A tool empowering you to reach your automation success

By Janine Nguyen, LogiGear Corporation

In case you haven’t heard, earlier this month we launched TestArchitect Team, the new, free, test automation tool that empowers testers to achieve automation success.

 

Facebooktwittergoogle_plusredditpinterestlinkedinmail

The Results of our Testing in Continuous Delivery Survey

This survey takes an in-depth look at teams that practice DevOps and compares it to teams that don’t practice DevOps.

By Michael Hackett, LogiGear Corporation

For 2017, LogiGear is conducting a 4-part survey to assess the state of the software testing practice as it stands today.

This is a 4-part series to mirror LogiGear Magazine’s issues this year.

Facebooktwittergoogle_plusredditpinterestlinkedinmail

Why is test automation the backbone of Continuous Delivery?

LGMweb.201512.Sakalley.SS_310023587

The path to continuous delivery leads through automation

By Ranjan Sakalley

Software testing and verification needs a careful and diligent process of impersonating an end user, trying various usages and input scenarios, comparing and asserting expected behaviours. Directly, the words “careful and diligent” invoke the idea of letting a computer program do the job. Automating certain programmable aspects of your test suite thus can help software delivery massively. In most of the projects that I have worked on, there were aspects of testing which could be automated, and then there were some that couldn’t. Nonetheless, my teams could rely heavily on our automation suite when we had one, and expend our energies manually testing aspects of the application we could not cover with automated functional tests. Also, automating tests helped us immensely to meet customer demands for quick changes, and subsequently reaching a stage where every build, even ones with very small changes, went out tested and verified from our stable. As Jez Humble rightly says in his excellent blog about continuous delivery, automated tests “take delivery teams beyond basic continuous integration” and on to the path of continuous delivery. In fact, I believe they are of such paramount importance, that to prepare yourself for continuous delivery, you must invest in automation. In this text, I explain why I believe so.

Facebooktwittergoogle_plusredditpinterestlinkedinmail
Subscribe