How to create a test scenario that coverage all basic functions in correct way? Also the template should look like a test suit (containing all of test case)

I design the checklist by categorizing some test scenarios, but the trouble is that in test scenarios must cover all cases (both positive and negative). It don't make sense if we put 2 kinds of cases in one scenarios right ?. Also, the template It should distinguish with other templates of test case. Do any one have experience to design a template suggest some template for me ?

My template just like below:

ID Scenarios Check points Result (Pass/Fail…) Bug ID Note
1.1 User can log and 1. Min: 8
save working time 2. Max: 24
with valid format 3. DEC FOR 1: #.#
including decimal places 4. DEC FOR 2: #.##
5. DEC FOR 3: #.##
6. ,,,,,

3 Comments

  1. Thanh Huynh

    @duong.it1987,

    I’m not sure I understand your questions.

    Re: “the trouble is that in test scenarios must cover all cases (both positive and negative)”
    > I don’t know why a test scenario *must* cover all positive and negative cases? A scenario is simply a user story to use your system. Of course users can follow positive/negative cases but I dont know why you need to cover both in a scenario? Why don’t you just split them into 2 scenarios? I may mis-understand your questions, can you clarify more?

    Re: “Do any one have experience to design a template suggest some template for me ?”
    > My suggestion is do not worry too much about template. The best template is the one you and your team agree and find they work.

    -Thanh

  2. duong.it1987

    Thanks a. I figured out how to make it now. My idea is that I will group all cases (both positive and negative) in one scenario, and split 1 case into many checkpoints.

  3. Thanh Huynh

    @duong.it1987,

    Good to know that you found solution for your problem.
    Feel free to go back here and ask question if you have any.

Leave a Reply

Your email address will not be published. Required fields are marked *

© 2024 AskTester

Theme by Anders NorenUp ↑