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

The Nexus Suite is uniquely architected for a DevOps native world and creates value early in the development pipeline, provides precise contextual controls at every phase, and accelerates DevOps innovation with automation you can trust. Read how in this ebook.

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..."

The DevOps Zone is brought to you in partnership with Sonatype Nexus.  See how the Nexus platform infuses precise open source component intelligence into the DevOps pipeline early, everywhere, and at scale. Read how in this ebook

Topics:

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

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

{{ parent.tldr }}

{{ parent.urlSource.name }}