61 votes

Exactly how are BDD, TDD, ATDD, Kanban and Scrum different from a waterfall approach?

I've seen TDD/BDD/ATDD used interchangeably with Scrum/Kanban/Agile, so the confusion is understandable. Here's my take on the differences: Waterfall is a software development methodology where each ...
user avatar
  • 30.8k
33 votes

Should QA ask developers for requirements?

No. Requirements should be originated from a single point. Your developers might misunderstand something so that you'll be testing not what your stakeholders require but what your developers ...
user avatar
  • 11.4k
28 votes

Why are Fibonacci numbers used for estimating effort?

Fibonacci series is just one example for estimation efforts. Some teams also use series as below: 1, 2, 5, 8, 20, 40, 100, .... 1, 2, 4, 8, 16, 32, 64, .... The idea is to use an exponential ...
user avatar
  • 1,795
27 votes
Accepted

When should QA be testing during a sprint? (Agile)

Define a definition of done that includes testing. Define which testing effort is minimal needed to get the work done. Time boxed exploratory testing session for each story, just after coding is done ...
user avatar
27 votes
Accepted

QA gets all the work at the end of the sprint

Get the whole team to work on the problem. Given the arrangement you've discussed clearly the team needs to look at options to resolve this. The problem itself seems fairly endemic in all of the ...
user avatar
23 votes

Why are Fibonacci numbers used for estimating effort?

They reflect that the degree of uncertainty grows as you look further out and at bigger tasks with more dependencies. For example, today you can be reasonably confident about how much effort is needed ...
user avatar
20 votes

How to tackle a huge bug backlog?

This is very common. There are basically 3 parts to the problem: Measure. Track stats to know when the backlog is getting worse or improving, week to week Identify. Figure out what things ...
user avatar
18 votes
Accepted

How do you determine that your project's quality has increased over time?

A good starting point is to define what quality means in your context. And then find out ways how to measure it. It seems you want to measure something without saying what that something is. Having ...
user avatar
  • 4,328
17 votes
Accepted

Can Agile make a tester more Dis-empowered

For starters, Agile is not an actor. One doesn't "work with Agile", "uses Agile", or things of this sort. Also, Agile doesn't act, it "doesn't do/make things". Agile is a mindset described in the ...
user avatar
  • 9,949
14 votes
Accepted

How bug prioritization works in agile projects vs non agile

A generic answer is: It's contextual; the team and stakeholders (which is who understand better the context) should work towards finding a good way - and periodically analysis its efficacy and improve ...
user avatar
  • 9,949
13 votes

How to tackle a huge bug backlog?

In addition to Michael Durrant's excellent answer and the equally good comments, I'd suggest you consider a few things: If you have not already done so, devote some time to analysis of your bug ...
user avatar
  • 30.8k
13 votes

What can be done if requirements are changing continuously in Agile?

From my experience - Faster feedback and more testing (in the form of automated tests ideally). If behaviour doesn't change but code is refactored often, then behaviour of system should be covered by ...
user avatar
  • 1,412
13 votes

Can Agile make a tester more Dis-empowered

It can work both ways, it depends on the situation In some companies Agile is bunch of buzzwords used to cover the fact that waterfall and command and control are really what's going on. In other ...
user avatar
11 votes
Accepted

How to manage test automation project with agile methodology when we have no control over the software we are testing

There is no single "correct" answer here, but there are several things your team can do to deal with this situation. I'm going to assume that you have no problems with the estimation and sprint cycle ...
user avatar
  • 30.8k
10 votes

Exactly how are BDD, TDD, ATDD, Kanban and Scrum different from a waterfall approach?

The difference between Waterfall methodology and an iterative methodology (agile, Scrum, etc.) is that Waterfall requires each step of a defined process be performed to completion in a particular ...
user avatar
10 votes
Accepted

Are there specific coding guidelines for test automation?

Summary of Code Quality Guidelines for Automation Code Prioritize english readability for descriptions and code Each test has an assertion at the end of the test Consider mocking and stubbing ...
user avatar
9 votes

How to test the REST API's effectively ( Complete )?

I really like this question, it's something I've thought about a lot. Validation response codes and a JSON body is a good start, but like you said, there's a lot more that can be done. I built an API ...
user avatar
9 votes
Accepted

How to ensure 100% coverage of requirements in test cases?

As testing is a never ending process we can never assume that 100 % test cases have been prepared, we can only minimize the risk of shipping the product to a client. Complete testing is impossible ...
user avatar
  • 552
9 votes
Accepted

What can be done if requirements are changing continuously in Agile?

Before answering this question, I would like to explain Why requirements are changing continuously in any Development Cycles: People change their minds for many reasons and do so on a regular ...
user avatar
8 votes

What is the difference between Gold bug and Latent bug?

Latent Bug : A latent bug is a bug which is present in the system from previous iterations or release (in your scenario Sprint 1). They are either low priority bugs, which either went undetected or ...
user avatar
  • 3,540
8 votes

Exactly how are BDD, TDD, ATDD, Kanban and Scrum different from a waterfall approach?

Kate's answer is great, but I want to throw in my 2 cents for differentiating TDD/BDD/ATDD. TDD is writing tests first and letting those tests drive the development of your application. This ...
user avatar
  • 187
8 votes
Accepted

Will writing unit tests block developers from coding?

The TDD cycle is more a development cycle for a developer, to quote James Shore, The Art of Agile, Test-Driven Development chapter: Programmers new to TDD are often surprised at how small each ...
user avatar
8 votes

Is checking web content for typos and spelling mistakes part of QA or testing?

I'm always on the lookout for grammar and spelling errors - purely because we're here to assure quality, and typo's aren't professional. It's usually not the developer's fault because they just copy +...
user avatar
  • 2,442
8 votes

QA gets all the work at the end of the sprint

Great Communication Brings Great Results Being last in line, QAs keep facing this repetitively. QA should proactively communicate delays and respective risks to stakeholders. I’ve never seen any agile ...
user avatar
  • 1,795
7 votes

QA in an Extreme Programming Agile Environment

The short version: regardless of the development methodology, your role is to provide information about the overall quality of the application. You do that via testing anything that isn't included in ...
user avatar
  • 30.8k
7 votes

Exactly how are BDD, TDD, ATDD, Kanban and Scrum different from a waterfall approach?

Kanban and Scrum are Agile process frameworks and therefor have short iterative development cycles as compared to the longer separate phases of waterfall projects. Agile projects focus on getting a ...
user avatar
7 votes

Lack of focused testing

When working with agile (or any methodology) I would suggest making your testers part of the team, rather having a separate QA team which is isolated from all the work. (This also means sitting the ...
user avatar
  • 353
7 votes

In what phase, QC Testing and UAT happens in Agile projects?

First, Agile projects, in general, has no defined phases like "Explore"or "Adapt". I suppose these terms come from some specific flavor of agile. In ideal Agile world, UAT will happen immediately ...
user avatar
7 votes

Is manual regression testing an technical debt for agile teams aiming for continuous delivery?

There are an awful lot of variables to consider here. But here are some points all the same. Manual Testing vs Automated Testing This point alone is probably worthy of a book and is one of the most ...
user avatar
7 votes
Accepted

Area of responsibility of a test manager within the agile process?

One of the foundation principles of the Agile Manifesto is self-organizing teams: The best architectures, requirements, and designs emerge from self-organizing teams. PS: It includes processes ...
user avatar
  • 9,949

Only top scored, non community-wiki answers of a minimum length are eligible