Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. We are using TestRail application for test case editing, assignments and execution tracking. https://foliotest.testrail.io
    1. Watch the following  short videos to get familiar with the application:
      1. https://www.gurock.com/testrail/videos/introduction-projects - length 4:45 min
      2. https://www.gurock.com/testrail/videos/suites-test-cases - length 6:49 min
      3. https://www.gurock.com/testrail/videos/test-runs-results  - length 10:50 min
      4. https://www.gurock.com/testrail/videos/issue-defect-integration - length 4:37 min
    2. Go to the Bug Fest test plan and review test cases for your respective modules: https://foliotest.testrail.io/index.php?/suites/view/21&group_by=cases:section_id&group_order=asc
    3. Add new test cases and sections if needed.
    4. JIRA filter with all stories closed since Q1 release deadline.  This is roughly all the new stuff added since last time: 
      Jira Legacy
      serverSystem JIRA
      jqlQueryfilter=11403
      counttrue
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    5. Add test cases to R15 test run on the following page: https://foliotest.testrail.io/index.php?/runs/edit/15/1&group_by=cases:section_id&group_order=asc
    6. All test cases should be reviewed/added before 5/15. It is also possible to add/remove test cases during test run. 
  2. Folio URL to use: TBD
  3. Credentials: folio/folio. Please use this login to create a user with desired permissions that you will use for testing. Don't use "folio" user to run test scenarios.
  4. Defects: 
    1. We are not going to use Bug Fest Jira project. Please create defects in appropriate JIRA projects. 
    2. Use mandatory label bugfest_q2.1.2019 for all logged defects.
    3. Link to instructions how to create recordings on Mac if you are Windows user - feel free to use screen capture of your choice. 
  5. Slack channel - "bug-fest"
  6. Bug triage - we'll be triaging bugs daily to make sure that P1 and P2 bugs treated with the proper urgency and fixed before Q2.2 is out.
  7. Retrospective meeting will be scheduled after the BF week.
  8. List of participants:

...