# QA

# Release schedule

  • Monday: perform "Bug Day" and testing Beta release.
  • Tuesday: testing both Patch release and Beta release.
  • Wednesday: releasing both Patch release and Beta release.

# Releasing features

  • Developer who is responsible for the feature performs a short Demo for both @cs-team and @dev-team.
  • Developer writes a small doc about the feature:
    1. What issue did the customer have?
    2. How did we solve it?
    3. What must customers know about the fix or the feature?
  • Project Lead merges the feature to the next beta release.

# Testing workflow

  • Project Lead creates a thread in #announcement and invites @dev-team.
  • @dev-team checks their bug-fixes on a patch-staging.
    • If an issue is found, it must be fixed immediately.

For Beta releases only:

  • Project Lead creates a thread in #announcement and invites @cs-team.
  • @cs-team checks all the changes.
    • If you find an issue, create a "Bug Task" in Jira. Be sure to use a specified version in a Fix versions field.

# How to write bug-reports

We use a template with two simple sections:

BACKGROUND
Some special settings or user permissions. Maybe a specific browser version.


SCENARIO
1. First step.
2. Second step.
3. ...
4. Actual result and what was expected.

BACKGROUND section can be ommited if everything is set by default.

Last Updated: 4/21/2021, 10:31:52 AM