Skip to main content
5 votes

Should code reviewer read user story COAs?

Of-course, understanding the goal of an user-story before coding review gives a lot of context. In an Scrum team I would expect all team-members to already understand the acceptance criteria as ...
Niels van Reijmersdal's user avatar
4 votes
Accepted

How to deal with too many test cases?

"The value of any practice depends on its context" N-wise testing is a technique, not a silver bullet to solve any problem. It's your responsibility as a professional to analyze how to best ...
João Farias's user avatar
2 votes

Using Excel for acceptance tests?

the answer to your first question is YES. You can definitely use Excel for creating acceptance tests. There are different types of acceptance testing: User Acceptance test Operational Acceptance test ...
Aalok's user avatar
  • 1,732
2 votes

Should code reviewer read user story COAs?

What I believe: In future, if someone looks at some block of code and feels WTF, then Code Reviewer is responsible more than implementer. This belief is not SCRUM. In SCRUM, the team is responsible, ...
Bryan Oakley's user avatar
2 votes

Should code reviewer read user story COAs?

As mentioned in comments, SCRUM is a process/methodology for executing functional work and not in the weeds on what "proper" work is/isn't. That being said there are certain checkpoints that need to ...
mutt's user avatar
  • 1,693
2 votes

What issues will arise from testing both API and UI in the same story

Some issues you will run into are: co-ordination of who tests what determining who tests what parts of security determining the feedback mechanisms for each changes in one area that affect the other ...
Michael Durrant's user avatar
1 vote

Shouldn't the User Story status be updated during the sprint in case of issues?

There is no "best practice in Agile". Key values and principles of Agile Software Development focus on how people interact and collaborate to deliver working software frequently. Different ...
Thomas Owens's user avatar
  • 1,601
1 vote

How to determine test coverage on a Protractor/Jasmine project

First, I think this question is less about code coverage -- "a measure used to describe the degree to which the source code of a program is executed when a particular test suite runs" -- and ...
Lee Jensen's user avatar
  • 2,280
1 vote

What issues will arise from testing both API and UI in the same story

combining API and UI Since a user story describes a feature and features could consist of UI and API changes, I guess this is pretty natural and happens all the time on different teams. API and UI ...
pavelsaman's user avatar
  • 4,548

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