Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel7

...

Task

Environment

Team Member

Dev testing

Dev

Dev

Manual QA test, automated test

{Test?}

Dev and QA

{ACC?}

Dev and QA

Playwright

Dev

Dev

ACC = current release

QA = next release

When ready for next release, we will send it to ACC.

Tickets

  1. Switch endpoints for test environment.

  2. Playwright - top of tech investment backlog - should include next sprint

Sprint decision-makers

Task

Team Member

Whether or not a bug or UI change suggestion will be added to the backlog

...

  • Acceptance criteria is complete

  • Unit test is complete

  • {Automated testing is complete}

  • Documentation for security groups

  • Dev has tested in QA, ACC and prod (if possible)

  • Dev sends screenshot of new UI work, or other items for which feedback is needed, to PO during development process for sign-off. Do not need to send screenshot for bug fixes.

  • No other sign-off is necessary as PO has seen screenshots, walk-through and review

  • When a story is done, and anything around it is tested so it is shippable

...

Testing - brainstorming only

Discussion with Grace - April 4

Bugs addressed during the sprint. Leave some space for bug testing during the sprint

...

  • How to track modifications to backlog items. E.g. when testing, if something needs to be added, what should we do?

Discussion with Ashiq

PO and users:

  • test in ACC

  • They can test on the first day of the next sprint - will will give them a list of what we completed and they can test if they can, if not, that is ok - maybe 1 hr of testing for them

  • Dev - send a screenshot of new UI before the functionality is built to get feedback from PO via email. Do not need to send screenshots for things such as bugs, and FR translations. Only things we need feeback on.

  • PO walkover - two days before the end of sprint - 15-30 min to take a quick look if screenshots are not enough - flexible. PO may not need it every week.

    • Can show him work still in progress

  • Users can test in test environment if they wish after sprint review. We can give them a few bullet points of what we worked on. Either at end of review or first day of sprint.

...

How would we work with dev’s only to write test cases?

Discussion with Ashiq

QA free from manual testing

...