11.2.1 QA Issue
Process
A Release manager with the help of a Quality engineer will populate the Merge Requests tested section. The information is taken from our Automated QA task generation script. The documentation can be found at: https://gitlab.com/gitlab-org/release/docs/blob/master/general/qa-issue-generation.md
Each engineer then validates and checks off each of their assigned QA task(s).
- Check off each Merge Request changes that you've tested successfully and note any issues you've created and check them off as they are resolved.
- If a problem is found:
- Create an issue for it and add a sub bullet item under the corresponding validation checklist task. Link the issue there.
- Add the severity label
- Raise the problem in the discussion and tag relevant Engineering and Product managers.
- If a regression is found:
- Create an issue for it
- Add the severity label and the regression label
- Raise the regression in the discussion and tag relevant Engineering and Product managers.
General Quality info can be found in the Quality Handbook.
Deadline
- The deadline to which the first release candidate (RC1) moves on from staging environment is 24 hours after the deploy to staging completes.
- The deadline to which subsequent release candidates moves on from staging environment is 12 hours after the deploy to staging completes.
Note: For Release Managers, for each release candidate, update the time here to reflect the latest release candidate deploy.
QA testing on staging.gitlab.com should be completed by 2018-08-22 13:01 UTC. After this deadline has passed, Release Managers will proceed with the canary and production deployment.
Merge Requests tested in 11.2.1
Example:
@Engineer1
| Apply notification settings level of bacons to all child bacons ~Discussion ~groups subgroups@Engineer2
| Resolve "Timeout searching group bacons" ~Discussion backend ~bug database ~groups issues ~performance@Engineer3
| Nonnegative meatball weights in issuable sidebar short ribs Deliverable ~Discussion backend direction frontend issues
- Found problem, does not work because... LINK_ISSUE_HERE
@Engineer4
| Moving rev-list pastrami bacons to Lfs Prosciutto ~Platform backend ~lfs
Create ~"Create"
uncategorized ~"uncategorized"
-
@stanhu | Eliminate unnecessary and duplicate system hook fires ~"memory usage" ~"performance" production request -
@stanhu | Fix broken Git over HTTP clones with LDAP users ldap regression:11.2
Automated QA for 11.2.1
If the last Daily staging QA
pipeline was run for 11.2.1,
you can just report the result in this issue.
Otherwise, start a new Daily staging QA
pipeline by clicking the
"Play" button and wait for the pipeline to finish.
Finished in 17 minutes 24 seconds (files took 0.72132 seconds to load)
27 examples, 1 failure
Failed examples:
rspec ./qa/specs/features/project/fork_project_spec.rb:3 # Project fork can submit merge requests to upstream master
If there are errors, create a new issue for each failing job (you can
use the "New issue" button from the job page itself), in the
https://gitlab.com/gitlab-org/quality/staging project and mention
the @gl-quality
group.
/cc @gl-quality