Scenario 1: As a admin i want to verify pet owner names won't ask by IVR assistance < Pet Owner number register in PMS DB >

Description: weather user call for give IVR number while connecting IVR will check that number with PMS data base and if user number match with PMS data base IVR wont ask user name or it will ask.

Above scenario is written by myself, how can i improve myself to write good test scenarios?

  • 1
    Why you want to improve this ? Even a person like me who doesn't have a clue about the product understood what exactly the use case is. If you really want to improve, You can write the description in point of u want else it looks perfect – PDHide Jan 23 at 10:13
  • 2
    If I were given this test case, I'd just stare at it without knowing what to do. How to improve the scenario is a good question, but I'd start with the language. Really, it's important how you write, how many mistakes you make, what your grammar is. It's even more important in cases when other people will be reading it after you. I recommend starting there, it will pay off. – pavelsaman Jan 24 at 13:12

Your scenarion&description is not a test scenario to me, it is a feature description. One that is hard to read, which makes assumptions and lacks focus to be bluntly honest.

I would rewrite it in a As a ..., I want ... , So that ... user story format:

User Story 002: Automaticaly match pet owners names from PMS system

As Jack (some role) the user of the IVR assistance, (The persona)

I want pet owner names to be prepopulated if available, (The functional feature)

So that I can quickly handle phone calls without unnecessary interuptions (The value)

Acceptance Criteria:

  • IVR uses PMS database field <Pet Owner number register> for number matching

  • If number is not matched ask for the pet owner name, as described in User story 001

The persona <some role> is probably not the admin, the admin maintains the systems, probably he doesnt really care about how it functionally works. Maybe it is Jack the veterinary? I dont know your domain, but I doubt the correct persona is the admin. Also I like to use the firstname of a real person that does that action or uses the feature.

The feature is a behaviour you want to happen, you are describing something doesn't is not happening. This leaves room for interpretation what happens.

The value you do not describe the value for the persona.

Test scenarios for the feature could be:

  • Pet owner name is matched and displayed correctly
  • Pet owner name is notmatched and is asked
  • Pet owner name is asked when PMS system is down
  • Etc...

Maybe write them in Given When Then scenario style:

Scenario: name is matched and displayed correctly
  Given the pet owner name is in the PMS system
  When I open the screen for pet "Jack Russel"
  Then then the pet owner name is "Saskia"

I like the combination of a User Story, Acceptance Criteria and GivenWhenThen scenario's, because it makes our team think, communicate and colleborate on requirements and testcases.

| improve this answer | |

Writing good and effective test cases covering all the scenarios depicts how efficient a qa services company is.

Below steps can also be followed that can be beneficial to cover test scenarios.

  • If user stories are provided with acceptance criteria mentioned,then direct test cases covering those scenarios can be created.
  • After previous step, more negative and positive use cases can be created to make them a part of regression testing cycle to assure all scenarios are covered.
  • Smoke and sanity test cases can be created to assure most important functions work and they work as expected.
  • Unit test cases can be created for each module separately covering them in depth.
  • Once unit test cases are created, test cases can be created covering the integration scenarios of the different modules.
| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.