Hot answers tagged

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
40 votes

What is your approach to low-priority bugs?

Some opinionated points from my experience, doing mostly development and operations with only a bit of QA and support, for the past few decades. Make of them as you will. I don't think it matters if ...
user avatar
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
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
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
20 votes
Accepted

Do we use/need test cases in Agile?

Maybe you do and maybe you don't. First determine what you want to accomplish, then decide on how you are going to do it. Blanket statements saying YES or NO are useless. It really depends on the ...
user avatar
  • 1,412
19 votes

What is your approach to low-priority bugs?

There is a third way, a middle of a road way, if you wish: don't polute the backlog with many low priority bugs, but group them in an epic or a story that might hold them. So, instead of having 20 low ...
user avatar
  • 4,079
14 votes
Accepted

Will implementing Agile generally improve code quality?

Tl;DR: Yes, it should if you practice technical excellence. Sadly often it doesn't. The current most popular Agile framework Scrum mainly focuses on process quality and project communication. If you ...
user avatar
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

What is your approach to low-priority bugs?

I go with reject and move-on. The downside is that other folks and new folks will keep discovering the bug 'anew' and have to remember them in their head. Which sounds like a huge problem. In ...
user avatar
13 votes

What is your approach to low-priority bugs?

You deal with them the same way as any other bug report. Review the bug and decide what (if anything) to do about it. If you decide to do nothing, tag it in the bug database with "won't fix" ...
user avatar
  • 261
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
9 votes

Do we use/need test cases in Agile?

Yes, in agile we do need test cases. Based on stories, we create test scenarios, and based on test scenarios, we create test cases. Because at the end of the sprint, we have to perform our test ...
user avatar
  • 2,093
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

How to measure productivity in agile testing?

The short version: If you're trying to measure productivity on an individual basis you're doing software development wrong. The longer version: Productivity, especially on an individual level, is ...
user avatar
  • 30.8k
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

How to plan both manual & automated testing in 2 weeks sprint?

There are a few questions to unpack in there. First, when to start testing in a 2-week sprint: as soon as possible. Many experienced Scrum teams focus on getting one or two backlog items to a ...
user avatar
  • 738
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

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

What is your approach to low-priority bugs?

Personally, I ask the other team members if such and such a problem is something we even want to deal with. If we agree it's not, I don't bother opening a new bug because obviously no one cares and I ...
user avatar
  • 4,328
7 votes

What is your approach to low-priority bugs?

I suggested this in the comments but figure it works just as well as an answer: Keep the low priority bugs around, especially things that aren't hard to fix in principle. Use them as onboarding ...
user avatar
  • 171
6 votes

Agile Tester vs Traditional Tester...........?

I'd suggest you start by taking a look at some of the related questions and their answers, particularly this one and this one. Also, if you don't have Crispin and Gregory's Agile Testing, get it. ...
user avatar
  • 30.8k
6 votes

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

My team struggles with a similar issue having multiple input streams, that are running on different iteration/sprint cycles into a common product. We tried testing in the dev int area for each team ...
user avatar
6 votes

Do we use/need test cases in Agile?

Agile: Understand, Agile is methodology which defines the ways and activities to be carried out for software development It does not eliminate the core step of development and testing process Surely ...
user avatar

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