PHASE 4: [Feedback + Discussion] Monthly Release + Maintenance Alignment - Post Launch

Summary

Lorem ipsum odor amet, consectetuer adipiscing elit. Sagittis pretium amet; efficitur efficitur fames mi ultrices morbi. Nisi hendrerit adipiscing malesuada cubilia luctus etiam purus. Vivamus sodales quis velit nostra habitasse, est libero. Massa dapibus luctus faucibus penatibus ultricies elit et commodo. Vel inceptos ad lacinia nibh habitasse lobortis eros lectus.

Sagittis facilisi non eros pulvinar malesuada luctus. Montes sed potenti id habitasse elit eu efficitur per. Venenatis nisi arcu proin risus ridiculus tempus ornare? Congue justo erat malesuada fermentum, tristique luctus metus. Torquent venenatis montes sollicitudin lacinia cursus interdum. Augue feugiat aliquam vitae parturient nibh, urna metus. Malesuada posuere ante nunc, suspendisse fusce id.

Pre-requisite

Add any steps to be performed before end to end testing can begin

  • Set a milestone / timeframe for the test session issue to inform all the DRIs about the upcoming testing session.
  • Dev leaders identify a DRI to participate in the testing session.
  • Ensure all testers have the right access/permissions in all our applications (i.e. GitLab, docs, etc.) for testing purposes.
  • All DRIs have reviewed issue in full and read applicable information below
  • Ensure all system DRIs have reviewed the new test scenarios and approved the changes.
  • Technical Writing Staff Engineer: @handle
  • Localization Engineer (Senior+): @handle
  • Technical Writing (Manager +): @handle
  • Localization (Manager+): @handle
  • Spartan Vendor: @handle
  • Communicate an estimated time for testing completion for DRIs

Potential Test Cases

Scenario # Task Test Case Scenario Expected Outcome UX sign-off

What to look out for

  • Sagittis facilisi
    • Example: Congue justo erat malesuada fermentum, tristique luctus metus. Torquent venenatis montes sollicitudin lacinia cursus interdum. Augue feugiat aliquam vitae parturient nibh, urna metus.
  • Lorem ipsum odor
    • Example: Vel inceptos ad lacinia nibh habitasse lobortis eros lectus.
  • Montes sed potenti
    • Example: Venenatis nisi arcu proin risus ridiculus tempus ornare

Known issues / bugs

  • Known bug list mattis condimentum odio curae euismod felis mus eros.
  • Gravida dui mus dictumst
  • Mattis condimentum odio curae euismod felis mus eros. Magna aliquet ut lacinia in facilisi litora. Congue facilisis lacus nisi est eu maximus. Turpis rutrum velit penatibus est luctus sapien morbi.
  • Current UI for language selection will be updated in Q1 (see gitlab.com)
  • Tellus imperdiet hac interdum primis dolor tellus aptent dictum. Habitasse nostra phasellus scelerisque fusce dapibus rhoncus vel curabitur.

🐛 Please use the Bug template for reporting bugs.

User-facing features that not yet implemented

  • gitlab.com
  • Version-specific behavior (gitlab.com)
  • Tellus imperdiet hac interdum primis dolor tellus aptent dictum. Habitasse nostra phasellus scelerisque fusce dapibus rhoncus vel curabitur.
  • Sed ut ipsum pellentesque dictum congue accumsan maecenas dictumst (see: gitlab.com)

Out of scope for this project

  • Significant visual design changes
  • Translations

Next steps in the project

We'll continue working through [this epic] (gitlab.com)

How to provide feedback

Before you start, please be sure to follow applicable action steps listed above and only provide one piece of feedback per thread. Below are the action steps to follow:

  • Check the known issues.
  • Review + check potential use test cases for clarity and accuracy
  • Review comments and/or feedback threads on this issue
  • If the feedback is not already covered in a known issue or feedback thread, open a new child issue on this issue. The DRI will respond and close the thread by either answering the question or opening a new backlog issue or bug in the project.
  • Open child item for any concern areas or areas that need additional support

Sign-offs

Once all scenarios have passed validation, stakeholders will provide final sign-off below

  • Technical Writing Staff Engineer: @handle
  • Localization Engineer (Senior+): @handle
  • Technical Writing (Manager +): @handle
  • Localization (Manager+): @handle
  • Spartan Vendor: @handle
Edited by Oleksandr Pysaryuk