-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Minor
-
Resolution:
Fixed
-
Affects Version/s:
None
-
Fix Version/s:
None
-
- Aside from today's cascade of tickets, QA will assess the tickets as they trickle in and return to the PO with questions/feedback as soon as possible.
- Features with complicated technical setups should be marked appropriately in the description or comments. QA will request a demo or follow-up meeting if necessary.
- Functional tests are the responsibility of the devs, but if there is a feature that could benefit from Rainforest or other manual regression tests, please flag the ticket.
If tickets are unflagged, QA will validate the devs' functional tests and request changes if necessary.
- Mandatory documentation fields can be filled in with URLs to the doc.nuxeo.com-content branch on Github and Github READMEs if no other documentation is prepared.
- Tickets should be created well in advance – if incomplete, a draft tag can be added to the ticket.
- [Suggested by Alain after the meeting] Since the due dates can change greatly over time, a ready tag can be added once the feature is completely ready to be tested.
- For UI/UX improvements that aren't earth-shattering, no QAFEAT ticket is necessary, an email with the devs' JIRA references will suffice. If needed, QA will create our own tickets to update any tests that might break as a result of the improvement.
- Due to limited staff and other QA responsibilities it is already clear that not everything can be tested in time – use ticket severity levels and communicate effectively so that we can choose our battles wisely.
- QAFEAT tags on bugs/improvements found during testing.
