Skip to main content

User Stories and Acceptance Criteria.

Image
By

 How to develop and Document the Acceptance Criteria in an Agile Environment.

Verify With 3C's:

The Three Cs of a user story (Card, Conversation, Confirmation) include the acceptance criteria. Collaborate and confirm that all stakeholders have a shared understanding of the criteria during conversations and discussions.

Link to User Stories:

Clearly link each acceptance criterion to the corresponding user story. This helps in traceability and understanding the context in which the criteria apply.

Collaborative Definition:

Involve key stakeholders, including the product owner, development team, and sometimes end-users, in the discussion and definition of acceptance criteria. This ensures a shared understanding of what needs to be delivered.

USER STORIES

These are short, simple descriptions of a feature or functionality from an end-user perspective.

Examples.1

 User Stories:

As a frequent traveller, I want to be able to convert currency so that I can quickly understand the equivalent amount in the local currency of the country I'm visiting.

Acceptance Criteria:

1.Given I am on the currency conversion page,

2.When I enter an amount in my home currency (e.g., USD),

3.And select a target currency (e.g., EUR),

4.Then I should see the equivalent amount in the target currency displayed on the screen.

Acceptance Criteria:

1.Given I am on the currency conversion page,

2.When I enter an amount in my home currency (e.g., USD),

3.And select a target currency (e.g., EUR),

4.Then I should see the equivalent amount in the target currency displayed on the screen.

2.1 As a customer, I want to be able to track my orders to see the status of my purchases.

Acceptance Criteria:

2.1.When logged in: When a user is logged in, they should have a “My Orders” section visible in the navigation bar.

2.2 Order History: In the “My Orders” section, the user should see a list of all their past orders, displaying order number,date, and status (e.g., processing, shipped, delivered).

2.3 Order Details: Clicking on an order should display detailed information, including items purchased, quantity, price, and shipping details

2.4 Order Status Updates: The order status should update in real-time. For example, if an order changes from processing to shipped, the status should reflect this change immediately.

2.5 Email Notifications: Users should receive email notifications for order status changes. Emails should include a summary of the status change and a link to view details on the website.

Who Defines and responsibility?

  1. Product Owner:
    • The Product Owner is responsible for defining and prioritizing user stories and acceptance criteria. They work closely with stakeholders to ensure that the development team understands the requirements and expectations.
  2. Development Team:
    • The development team, including developers and testers, uses acceptance criteria to guide the implementation and testing of user stories. Acceptance criteria serve as the basis for creating test cases to ensure that the user story meets the specified requirements.
  3. Quality Assurance (QA) Team:
    • QA professionals use acceptance criteria to design test scenarios and cases. They perform testing based on these criteria to verify that the functionality works as intended and meets the user's expectations.
  4. Stakeholders:
    • Various stakeholders, including end-users, customers, and business representatives, may be involved in reviewing, and validating acceptance criteria. Their feedback is valuable for ensuring that the delivered product aligns with their needs and expectations.

And BA , Scrum master , END customer also have a their presence in that process and choices are depends on Organization practices and follows.


How Acceptance Evolved from Test cases?

Test cases provide step-by-step instructions on how to test each acceptance criterion. They include preconditions, the specific actions to be taken (when), and the expected outcomes (then). Test cases are more granular and focus on the technical aspects of validating the software.

Each test case should be mapped back to the specific acceptance criterion it is validating. This mapping ensures traceability and helps in understanding which tests correspond to which user story requirements.

Testers, along with the development team, take the acceptance criteria and further refine them into detailed test cases. Each acceptance criterion may be broken down into multiple test cases to cover different scenarios, edge cases, and conditions.

Steps to Validate and Verify Acceptance Criteria:

  1. Define Clear Acceptance Criteria:
    • Ensure that acceptance criteria are well-defined, clear, and measurable. They should provide a basis for testing and validation.
  2. Collaborate with Stakeholders:
    • Engage stakeholders, including end-users, to review and confirm acceptance criteria. This collaborative process helps in refining and ensuring a shared understanding of expectations.
  3. Create Detailed Test Cases:
    • Develop detailed test cases based on the acceptance criteria. Each test case should cover a specific aspect of the acceptance criteria, including different scenarios and edge cases.
  4. Execute Acceptance Testing:
    • Conduct acceptance testing to validate that the software meets the user's expectations. This involves executing the test cases in a real-world environment with actual end-users whenever possible.
  5. Feedback and Iteration:
    • Collect feedback from stakeholders during acceptance testing. Iterate on the acceptance criteria and test cases based on this feedback to address any discrepancies or improvements.

 

 

 

 

 

 

 


Comments

Post a Comment

Popular posts from this blog

Had you to design test cases for a complex feature. What factors did Tester consider, and how did prioritize test scenarios?

By
  Take an instance as new application has integrated into existing applications(i,e., Running on real time )Customer want to integrate their application into third party vendors in order to let the customer order their needs through our created app itself. Factors Consisdered : Error Handling , Functional Requirements , Edge cases , Non-Functional Parameters . Transaction Flow Flow1: Customer Land on third party vendors app and start picking their items. Flow2 : Picked Items has to go Cart Page and can see number of items added by visually. Flow3: Once click to checkout , it will allow the user to input their card details and processing transaction. Flow4:Once Transactions done, newly created app show the details of the order and online tracking number . Prioritize scenerios based on the Business Emergency and needs ,well in briefly communicate to team members to identify the Critical paths and prioritize the that test suite first and Start  the execution based on what need to...
Post a Comment
Read more

Static and Non-Static

By
  What is the purpose of the static keyword in Java? The static keyword is used to declare class-level variables and methods . They belong to the class rather than instances of the class and can be accessed using the class name. can we use the static keyword for package level access? In Java, the static keyword is not used for controlling access levels. The static keyword is primarily used to define class-level members, such as variables and methods, that are associated with the class itself rather than with instances of the class. The concept of access levels, on the other hand, is controlled by access modifiers. public class MyClass {     public static int publicStaticVariable = 10;     static int packagePrivateStaticVariable = 20; // package-private by default     private static int privateStaticVariable = 30; } To summarize, while static is used to define class-level members, access modifiers (public, protected,...
Post a Comment
Read more

Pre conditions and Post conditions in Test Ng.

By
Pre conditions and PostConditions in Test Ng. Vision of Preconditions and Postconditions: 👉 Ensuring Test Isolation: By using preconditions and postconditions, you ensure that each test method is executed in isolation, with a clean and consistent state. 👉Promoting Reusability: Setup and teardown tasks defined in preconditions and postconditions can be reused across multiple test methods, promoting code reuse and reducing redundancy. 👉Maintainability: Clearly defined preconditions and postconditions enhance the maintainability of test code. Changes or additions to the setup and cleanup logic can be made centrally in these annotated methods. TestNG PreConditions and PostConditions flow.   Before Suite (once) Before Test (once for each <test> in the suite) Before Class (once for each class with test methods in the <test> ) Before Method (before each test method) Test method execution After Method (after each test method) After Class (after all test methods in ...
Post a Comment
Read more