Keeping Quality in DevOps – Neotys Testing Roundup

1. Keeping Quality in DevOps

Before DevOps, it was common for companies to deploy changes to production as a large batch in what many of us called the “big bang” approach, which would occur on a quarterly or bimonthly basis. Batching many changes together seemed like a good idea back then because we didn’t want to inconvenience our users any more than was absolutely necessary.

Unfortunately, big-bang deploys also typically had too many moving parts and were packed with risk, often resulting in systems outages. By automating the entire application build, package, and deployment, we managed to support changes to production much more frequently.

Too often however, the QA and testing team cannot keep up with the need to verify and validate changes. DevOps may be able to deliver changes to production, but the rest of the team may not be able to handle continuous deployments.

Check out more on continuous testing here.

2. What are the questions to be asked before thinking of software Automation

Automation is a complex activity in itself. What are some of the relevant questions to be asked before we think of automation? For example:

  • Why do you need to automate?
  • What do you need to automate?
  • What do you gain by automating?
  • Would it cost more to automate than to do it by hand?

3. Scrum Versus Kanban: An Interview with Cory Foy

In this interview, Cory Foy speaks about his presentation at Agile Development & Better Software Conference East, why choosing Scrum or kanban is similar to climbing a mountain, how organizational change is all about experimentation, and why companies should use Innovation Games.

Read the full transcript of this interview with Cory.

4. Are You Listening? Say Something!

James Bach is tired of hearing the simplistic advice about how to listen one must not talk.

“That’s not what listening means. I listen by reacting. As an extravert, I react partly by talking. Talking is how I chew on what you’ve told me. If I don’t chew on what you say, I will choke or get tummy aches and nightmares. You don’t want me to have nightmares, do you? Until you interrupt me to say otherwise, I charitably assume you don’t.”

James presents an alternative theory of listening; one that does not require passivity. He shows how this theory is consistent with the “don’t talk” advice if you consider that being quiet while other people speak is one heuristic of good listening, rather than the definition or foundation of it.

How does this relate to testing? James claims that listening is itself a testing process. It must be, because testing is how we come to comprehend anything deeply. Testing is a practice that enables deep learning and deeply trusting what we know.

Read James’s post here, and add your own 2 cents.

Leave a Reply

Your email address will not be published. Required fields are marked *