登录查看更多内容

点击“继续加入或登录”，即表示您同意遵守领英的《用户协议》、《隐私政策》及《Cookie 政策》。

Last updated on 2024年7月26日

How do you test user stories?

由人工智能和领英社区提供技术支持

User stories are short and simple descriptions of a feature or a function from the perspective of a user. They are the building blocks of agile methodologies, such as Scrum and Kanban, that help teams deliver value to customers. But how do you test user stories to ensure they meet the acceptance criteria and the quality standards? In this article, you will learn some practical tips and techniques to test user stories effectively and efficiently.

本文章的要点总结

Set precise acceptance criteria:

Define clear and testable conditions using the Given-When-Then format or a checklist. This ensures everyone understands the expectations and the story is considered complete only when these criteria are met.### *Adopt a testing pyramid approach:Balance testing efforts across unit, integration, and end-to-end tests. This method helps in efficiently covering all aspects of functionality, interactions, and user journeys for comprehensive verification.

本摘要由 AI 和以下专家提供支持

1 Define clear and testable acceptance criteria

The first step to test user stories is to define clear and testable acceptance criteria that specify the expected behavior and outcomes of the feature or function. Acceptance criteria are the conditions that must be met for the user story to be considered done and accepted by the customer. They should be written in a simple and concise language, using the Given-When-Then format or a checklist. For example, given a user is logged in, when they click on the profile button, then they should see their personal information and settings.

添加您的观点

Jennifer Simpson

Stoic Scrum Master | LinkedIn Top Voice for Agile Methodologies
举报内容
You might also consider using the phrase "done when" along with the checklist format. This helps to easily communicate to the developer that this user story "will be done when" all of the bulleted items are complete. If your team struggles with scope creep or gold plating user stories, you can highlight items that are "out of scope" in the done when/acceptance criteria. Using the login example from above, you could highlight that "seeing the user's photo/avatar is out of scope of this user story".

已翻译

赞
Jennifer Simpson

Stoic Scrum Master | LinkedIn Top Voice for Agile Methodologies
举报内容
You might also consider using the phrase "done when" along with the checklist format. This helps to easily communicate to the developer that this user story "will be done when" all of the bulleted items are complete. If your team struggles with scope creep or gold plating user stories, you can highlight items that are "out of scope" in the done when/acceptance criteria. Using the login example from above, you could highlight that "seeing the user's photo/avatar is out of scope of this user story".

已翻译

赞
Jennifer Simpson

Stoic Scrum Master | LinkedIn Top Voice for Agile Methodologies
举报内容
You might also consider using the phrase "done when" along with the checklist format. This helps to easily communicate to the developer that this user story "will be done when" all of the bulleted items are complete. If your team struggles with scope creep or gold plating user stories, you can highlight items that are "out of scope" in the done when/acceptance criteria. Using the login example from above, you could highlight that "seeing the user's photo/avatar is out of scope of this user story".

已翻译

赞
Jennifer Simpson

Stoic Scrum Master | LinkedIn Top Voice for Agile Methodologies
举报内容
You might also consider using the phrase "done when" along with the checklist format. This helps to easily communicate to the developer that this user story "will be done when" all of the bulleted items are complete. If your team struggles with scope creep or gold plating user stories, you can highlight items that are "out of scope" in the done when/acceptance criteria. Using the login example from above, you could highlight that "seeing the user's photo/avatar is out of scope of this user story".

已翻译

赞

2 Use a testing pyramid approach

The second step to test user stories is to use a testing pyramid approach that balances the different types and levels of testing. The testing pyramid is a model that illustrates how to allocate testing resources and efforts across unit tests, integration tests, and end-to-end tests. Unit tests are the most granular and fast tests that verify the functionality of individual components or modules. Integration tests are the intermediate tests that check the interactions and dependencies between components or modules. End-to-end tests are the most comprehensive and slow tests that simulate the user journey and the system behavior from start to finish.

添加您的观点

Sri Phani Krishna Chinnapuvvula

Seasoned Digital Transformation Leader & Enterprise Agile, DevSecOps, SRE Coach | Driving Digital Excellence in Global Enterprises | Proven Success Enterprise Integration, Enterprise Architecture, Engineering Mgmt.
举报内容
For effective User Story testing: 1. Clear Precise Acceptance Criteria with common understanding 2. Feed acceptance criteria and NFR into the test case automation 3. Eliminate any flaky tests 4. Automate the test process 5. Balanced approach of Shift-left and Shift-Right testing approach.

已翻译

赞

3 Apply test-driven development or behavior-driven development

The third step to test user stories is to apply test-driven development (TDD) or behavior-driven development (BDD) practices that integrate testing into the development process. TDD and BDD are agile methodologies that involve writing tests before writing code, following a red-green-refactor cycle. TDD focuses on writing unit tests that define the expected functionality of the code, while BDD focuses on writing acceptance tests that define the expected behavior of the system. Both TDD and BDD help teams create testable and maintainable code, reduce defects, and improve quality.

添加您的观点

Taina Sabino

Product Owner | Scrum Master | Leading SAFe | PSPO I
举报内容
I believe that is good to mention that even thought the PO is responsible for writing the TDD for example, is impossible for the PO to cover everything. Thats why I love the refinements section, because the team together with the PO can refine the user story and add the test scenarios that are missing.

已翻译

赞

4 Perform exploratory testing and usability testing

The fourth step to test user stories is to perform exploratory testing and usability testing that complement the automated and scripted tests. Exploratory testing is a creative and intuitive testing technique that involves exploring the system without predefined test cases, looking for bugs, risks, and opportunities for improvement. Usability testing is a user-centric testing technique that involves observing and collecting feedback from real or representative users, evaluating how easy, efficient, and satisfying the system is to use. Both exploratory testing and usability testing help teams discover unexpected issues, validate user needs, and enhance user experience.

添加您的观点

5 Review and refine user stories and tests

The final step to test user stories is to review and refine user stories and tests based on the feedback and results of the testing activities. Testing is not a one-time event, but a continuous and iterative process that requires collaboration and communication among the team members, the customer, and the stakeholders. Reviewing and refining user stories and tests help teams ensure that they deliver value, meet quality standards, and align with customer expectations.

添加您的观点

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

添加您的观点

Taina Sabino

Product Owner | Scrum Master | Leading SAFe | PSPO I
举报内容
I strongly recommend writing in the user stories the DOD (Definition of Done) and DOR (Definition of Ready), this will make the user story clear to understand when the story will be considered ready for the developer and done for the user.

已翻译

赞

Agile Methodologies

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

查看全部

How do you test user stories?

1

2

3

4

5

6

1 Define clear and testable acceptance criteria

2 Use a testing pyramid approach

3 Apply test-driven development or behavior-driven development

4 Perform exploratory testing and usability testing

5 Review and refine user stories and tests

6 Here’s what else to consider

Agile Methodologies

给文章评分

感谢您的反馈

更多Agile Methodologies相关文章

更多相关阅读内容

How do you test user stories?

1

2

3

4

5

6

1 Define clear and testable acceptance criteria

2 Use a testing pyramid approach

3 Apply test-driven development or behavior-driven development

4 Perform exploratory testing and usability testing

5 Review and refine user stories and tests

6 Here’s what else to consider

Agile Methodologies

给文章评分

感谢您的反馈

查看其他技能