📋
QASpace-CaseStudies
  • Home
  • Test Strategy
    • Vision of Quality
      • Good Test Coverage
      • ISO 29119 Certification
      • Date Internationalization Format
      • Localization Testing
      • Test Management
      • Creating TestCase
  • How to Test
    • How to write good TestCase?
      • Tips on Testing
      • Pair Testing
      • UserStory to TestCases
      • Optimising the development flow in a Scrum team
      • Rate/Prioritise bug tickets
  • Exploratory Testing
    • Exploratory Testing
      • Creating Test Charters
      • Test Charters
      • Velocity was too high
  • Agile
    • Implementing Scrumban
      • Breakdown Task
      • Common work across teams
      • Sustainable QA process in the organization
  • Philosophy of Testing
    • Brainstorming
  • Metrics
    • Risk Analysis
      • Testing Outsource
      • How to measure Quality?
  • Automation
    • AI-Automation
      • Software through the lens of AI
      • SAP/Salesforce Automation
      • Mobile Automation
      • Solve by automating the GUI?
      • Improve Skill-sets
      • Coding Skills
      • Working in BDD
      • Value of Test Automation
      • UI/API automation asset
      • TDD VS BDD
      • Selenium vs Cypress
      • An important consideration of Test Automation journey
      • Balance Test Automation Development
      • Automation is no longer providing value
      • Define AI in test automation
      • Unique Locators
      • Best Practices as QA, QA Lead, and Automation Engineer
      • Making friends with Imposters
  • Survey/Polls
    • Is QA really a Gatekeeper?
  • Performance
    • Performance Testing
      • Client-Side Performace
Powered by GitBook
On this page

Was this helpful?

  1. How to Test
  2. How to write good TestCase?

UserStory to TestCases

Ministry of Testing

Case Study:

Can anyone point me to an 'ideal' or most comprehensive User Story for a simple Login Screen you have encountered, please? Any screenshots or links or doc files are welcome after removing the confidential info. Trying to help someone with 'how to have a complete flow from user story to test cases'. I have things in mind but a real example would be a quick help.

-- Anonymous

Recommendation 1:

So basically a User Story is in the format: As a user, I should be able to login into the system so that I can access the dashboard. Now, there are things that help to define the user story and helps to identify the Definition of Done while developing a particular functionality. Hence, the acceptance criteria for the above user Story might be: Acceptance Criteria:

  1. Login Form should be present with Email and Password Fields

a. Valid email should be entered b. Valid password should be entered "You can add your validation criteria too"

  1. Login Button should be present in the form.

  2. provide the link to the design of the Login Form so that developer can design the form based on the mockup.

Now, talking about the Test cases, your tests cases are written against the acceptance criteria which are requirements for that functionality.Add Positive, Negative and Edge cases in your test cases. Some Test Scenarios would be:

  1. Verify user with a valid email and valid password can login

  2. Verify user with invalid email and invalid password cannot login

  3. Verify user with a valid email and invalid password cannot login and vice versa

  4. Verify that validation message is displayed clicking on Login button with empty email and password fields

Make sure you follow a proper test case format. In this way, you can continue.

-- Nischal Khadka

Reference:

PreviousPair TestingNextOptimising the development flow in a Scrum team

Last updated 4 years ago

Was this helpful?

How to Write Test Cases For a Login Page (Sample Scenarios)Software Testing Help
How to write Test Cases for a Login PageSoftware Testing Material
Logo
Logo