development lifecycles

Jeff Checkner's picture

Quality processes in Continuous Integration/Deployment

In traditional waterfall and agile processes we implement a test strategy to set expectations (and receive feedback) on approach for a release (multiple sprints of work) and test summary to capture results of the execution (functionl, security, and performance testing).  

In a a CI/CD model when we have a 2 week sprint and plan to deploy every 2 weeks it seems a bit cumbersome to do a strategy and summary every 2 weeks.  Ideally the summary could be pulled from an automation tool and produced to a dashboard so that should not be too bad.

Michael Tomara's picture

I would add that having a long-term strategy should not be incompatible with 2-week release periods unless you are releasing something brand new each time. So this depends on a scope of each release. Release scope defines the scope of testing as well: usually it is quite a challenging task to test absolutely everything for short release periods. Of course the bigger the better, but some priorities must be established. 

Sure, automated testing tools seem to be the best way to deal with the lack of time here - given that you have such a solution which is compatible with CI and at the same time can perform regression testing properly. By the way, if you need to run some UI regression tests, I would suggest you trying Screenster, a visual testing tool which was designed to help with UI testing in CI environment.

Justin Rohrman's picture

I'm not sure what you mean by setting a strategy and summary, but it sounds like you mean writing something. Strategies (and other common test artifacts) don't have to be heavy things that drag you down. If they aren't helping you do a good job testing, or release more often, I would encourage you to abandon them.

Regarding CD, not to be dismissive of your point, but releasing every two weeks isn't close to continuous delivery. This is the standard compressed waterfall interpretation of agile that many companies take. The more often you want to release software, the more crucual it becomes to have useful quality percieving activities like pairing, layering of automation, build pipeline automation, and monitoring. It also means your testers must be technical for some definition of the word technical.

 

To start with though, I'd encourage you to reevaluate what strategy and summaries are, and why you need to create them every two weeks. 

10 Lessons Learned in Cross-Platform Development

Building an app for a single platform is difficult, but designing, implementing, and testing an app targeting multiple operating system platforms can be next to impossible. The secret balances upfront design with customer feedback.

Better Software Magazine
[article]

Test Coverage in the Age of Continuous Delivery

Summary:
Test coverage is a strategy to help us spend scarce testing time on the right priorities. When things were tested last, how much automation coverage we have, how often the customers use the feature, and how critical the feature is to application are all factors to consider. Here are some ideas for keeping quality high when you're transitioning to continuous delivery.

Test coverage is a strategy to help us spend scarce testing time on the right priorities. When things were tested last, how much automation coverage we have, how often the customers use the feature, and how critical the feature is to application are all factors to consider. Here are some ideas for keeping quality high when you're transitioning to continuous delivery.

About the author

2017 Is a Pivotal Year for DevOps

Customers expect real-time software updates. As DevOps becomes the engine for delivering business value, continuous innovation is needed. And this has to begin at the start of every project.

Better Software Magazine
[interview]

Identify Bottlenecks in Your Agile and DevOps Processes: An Interview with Tanya Kravtsov

Summary:

In this interview, Tanya Kravtsov, a director of QA at Audible, explains why identifying bottlenecks is so critical when you’re turning to agile and DevOps, as well as how automating manual processes can lead to better quality.

In this interview, Tanya Kravtsov, a director of QA at Audible, explains why identifying bottlenecks is so critical when you’re turning to agile and DevOps, as well as how automating manual processes can lead to better quality.

About the author

Fun with Enterprise iOS Apps

Can building an enterprise app be fun? Not “fun” in the sense of “if this is fun, we’re having it”—but actual, joyful, enthusiastic fun? Join Joe Keeley to explore how to find fun in the development lifecycle of iOS apps in enterprise environments, and (not coincidentally) how to deliver...

StickyMinds is a TechWell community.

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