Skip to main content

Article on Dev and Testing schedules during an iteration

This is a good article addressing developing features and QA testing them during the same iteration. Chris offers a good example process. I like the comments that followed because you see different points of views regarding the topic. This brings to light some of the issues with Dev and QA cohesion.

I think the example Chris provides makes sense but I also sympathise with the QA person explaining the issues of retesting changing features. IMHO, I think QA has to catch up with development in "agile" thinking. Developers know code is going to change and it will change a lot. With CI, Unit Testing and refactoring, the features evolve over time. QA needs to follow the same pattern in Agile environments. They are not retesting features, they are testing. Features are not half complete, they are not done. (Done means a feature is developed, tested, and accepted) QA should work closer with developers and should us continuous testing (CT) throughout the iteration. Then, at the end of the iteration the whole team does internal acceptance testing.

One key issue with CT is team size. One QA person cannot do CT with 6 developers. I think an effective ratio should be created that can balance the output of dev to the input of QA.

I like the idea of developers writing the automated test that are identified by QA. This is a good checks and balance system.

http://edgehopper.com/qatesting-in-an-agile-environment/

Comments

Post a Comment

Popular posts from this blog

2020 State of DevSecOps by Accurics

 This is an excellent report for all IT Pros and Engineers.   Highlights: Storage is most impacted solution Open security groups or network configuration Secrets are not so secret Unused resources are not secure. Take a look at these.  Look again.  These are not highly skilled problems.  They just need guidelines and proactive management.  The article uses policy as code as a solution for many of the problems.  I will drill into each of these more in the future.  I wanted to get the awareness out first and then, come back to solutions.  
Post a Comment
Read more

Learn Anti-Leadership from Basecamp

 There are many different articles out there and Twitter comments about the Basecamp drama.  I am not going to post any here because it might seem biased depending on the article.  Google them yourself.  In short, Basecamp made a policy to not allow political discussions at work.  Coinbase did this previously too and applauded Basecamp for it.   Apparently, for years there has been a list of funny customer names at floating around Basecamp.  This list or even the knowledge that Basecamp had a list, was disturbing to some employees.  Also, some employees tried to start a Diversity and Inclusion practice.  Despite how much the founders of Basecamp promoted DI, they didn't feel they were being taken serious.  They felt the company was only about the founders and not about employees.    If this isn't enough, the founders debated and even called out employees for their comments regarding the topics, publicly.  This is my s...
Post a Comment
Read more

Cloud Ops: The New IT for the Cloud Era

Over the past few months of interviewing and researching dozens of companies—particularly small to mid-sized SaaS businesses—one pattern keeps emerging: the desire to stand up a Cloud Operations (Cloud Ops) organization. It makes sense on the surface. Cloud is now the infrastructure of choice, so naturally, someone needs to “own” it. But what’s unfolding in practice often misses the mark. Many companies are attempting to solve growing cloud complexity by taking all their DevOps, SRE, and platform engineering talent and consolidating them into a Cloud Ops team. The idea? Share them across product teams so no one gets overwhelmed. If that sounds familiar, it should. It’s the same centralization tactic used by traditional IT for decades. And it's creating the same problems. When Cloud Ops Becomes Old IT in Disguise Here’s the playbook we’re seeing: Move DevOps, SRE, and Ops into a central Cloud Ops team. Let them handle infrastructure, CI/CD, monitoring, and cloud securit...
Post a Comment
Read more