Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

The DevOps Zone - Best of the Week (Apr. 5-12)

DZone's Guide to

The DevOps Zone - Best of the Week (Apr. 5-12)

· DevOps Zone
Free Resource

Download the blueprint that can take a company of any maturity level all the way up to enterprise-scale continuous delivery using a combination of Automic Release Automation, Automic’s 20+ years of business automation experience, and the proven tools and practices the company is already leveraging.

In case you missed it, here is a curated list of the best posts from the past week of The DevOps Zone. This week: 3 skills every tester should have, is 100% code overage possible?, why manual testing is still necessary, looking for the constraint in software development, and finally we ask whether continuous delivery is riskier.

1. 3 Technical Skills Every Tester Should Have

Across the board, there is a variety of knowledge that testers are required to have no matter what type of business they are working for or what industry they are in.

2. 100% Code Coverage Possible?

What I’m suggesting here is that if you change your perspective from one of, “this is a ridiculous idea” to “this is a challenge to be met” or “this is an opportunity to learn”, or even (to address a specific comment that started this post) “I get to make my application more bug free.” you may find that the boredom leaves.

3. Why Manual Testing is Still Necessary

While more organizations are pursuing agile environments, this does not mean that they are completely abandoning familiar processes. Manual testing may not be an optimal choice for all cases, but there are some instances where a human evaluator is necessary for maintaining the quality of the program. By understanding manual testing's strengths, QA teams can leverage it more effectively and reap benefits on top of their automation efforts.

4. Where is the Constraint in Software Development?

The constraint is our limited understanding of what is valuable. We EXPLOIT it by creating feedback loops based on small increments; smaller increments create more opportunities to understand where the value lies, which in turn limits wasted programming effort. Then we SUBORDINATE to it by not planning or designing too much in advance; that would build up WIP — not of plans or design per se, but of guesses.

5. Is Continuous Delivery Riskier?

I read an article in CIO magazine “Three Views on Continuous Delivery“. Here is my response to the article: "If Continuous Delivery “strikes fear into the heart of CIOs” they are missing some important points..."

Download the ‘Practical Blueprint to Continuous Delivery’ to learn how Automic Release Automation can help you begin or continue your company’s digital transformation.

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}