Test Case Template - intive/patronage21-qa GitHub Wiki

Steps for a non-BDD test case

  1. Make sure you are in right project - intive - Patronage 2020/21 (00991643)
  2. To create a test case click on the "Test" located in the top menu navigation and choose "Create a test" as below.

  1. Summary: start with the module name, then add [A] for the automated test or [M] for the manual one. Next, write the TC title after the "–". sign. Remember that the name/title for the test case should be simple and clear for developers and QA team. Exemplary summary: BASKET_[M]_IP2-30_Verify_deleting_items_from_the_basket.

  2. Choose component/s by pressing down to select or typing to get a list of possible.

  3. Write down description as clear as you can, like it is shown below: Test case description Use the release date if you don't have the release number of the app. Remember that not all sections need to be filled every time. E.g. if you don't need to specify the environment, don't use the "Environment" section.

  4. Add the priority to the test case, using only priorities listed below: Priorities

  5. Add labels – remember about writing them in lowercase. In the "Labels" text area write:

  • technological group that the TC is related to (java, js, android)
  • name of the app module that the TC is related to: e.g. users_list (remember to use "_" instead of the space bar which is not allowed in the "Labels" section
  • manual or automatic – to specify what type of test case it is
  • qa_ready – if the functionality is implemented by the technology group
  1. Add an attachment if it'll help to better understand the expected result of a TC.
  2. From the "Linked issues" dropdown list select "Tests" and select/write the number of the story/task/subtask this TC tests.
  3. "Assignee" set as "Unassigned".
  4. Epic Link set as "QA".
  5. Create test steps for the test case which includes the following information for each test step:
  • Test step - Description of the test step/action that needs to be performed for this individual step.
  • Expected Result - The expected result after performing the action for this individual step. Remember that you don't have to fill the "expected result" for every test step if you think it is not necessary but you always have to fill the expected result to the last test step. Test steps
  1. Click on the "Create" button.
  2. Find created test in backlog, right click on it and choose "Tests QA".

Steps for a BDD test case – create after PRs but BEFORE merging to the branch master!

  1. Make sure you are in right project - intive - Patronage 2020/21 (00991643)
  2. To create a test case click on the "Test" located in the top menu navigation and choose "Create a test" as below.
  3. Summary: The title should look exactly the same as the corresponding scenario title from the repository. Remember that the name/title for the test case should be simple and clear for developers and QA team. Exemplary summary (for API BDD test): USER_SEARCH_[/api/users]_[GET]_1_IP2-90_Searching_for_the_existing_user_by_name_surname_or_username
  4. Choose component/s by pressing down to select or typing to get a list of possible.
  5. Write down description as clear as you can. Important things to remember:
  • One Feature file in repository can have many scenarios. Remember that one scenario from Feature file equals one test case in Zephyr
  • If your Feature file in repository contains Background, you have to copy this Background to each test case description in Zephyr (after App info). For exemplary Description section see below: BDD TC Description Use the release date if you don't have the release number of the app. Remember that not all sections need to be filled every time.

  1. Add the priority to the test case, using only priorities listed below: Priorities

  2. Add labels – remember about writing them in lowercase. In the "Labels" text area write:

  • technological group that the TC is related to (java, js, android)
  • name of the app module that the TC is related to: e.g. users_list (remember to use "_" instead of the space bar which is not allowed in the "Labels" section
  • manual or automatic – to specify what type of test case it is
  • coded - if for this test case step_definitions in VS have been already made (this label can be inserted whenever code is ready)
  • qa_ready – if the functionality is implemented by the technology group
  1. Add an attachment if it'll help to better understand the expected result of a TC.
  2. From the "Linked issues" dropdown list select "Tests" and select/write the number of the story/task/subtask this TC tests.
  3. "Assignee" set as "Unassigned".
  4. Epic Link set as "QA".
  5. Don't fill the test steps.
  6. Click on the "Create" button.
  7. Find created test in backlog, right click on it and choose "Tests QA".