Test Engineering team
Test Engineering team in Test Platform sub-department
Common Links
| Category | Handle |
|---|---|
| GitLab Team Handle | @gl-quality/tp-test-engineering |
| Slack Channel | #test-engineering-team |
| Team Boards | Team Board |
| Issue Tracker | quality/team-tasks |
Engineers in this team support the product sections supported by the Core Development and Expansion Development Department.
Team members
Engineering Manager: Ksenia Kolpakova
| S.No | Department | Section | Stage | SET Counterpart |
|---|---|---|---|---|
| 1 | Core Development | Dev section | Create | Jay McCure |
| 2 | Core Development | Dev section | Plan | Désirée Chevalier |
| 3 | Core Development | CI section | Verify | Tiffany Rea, Joy Roodnick |
| 4 | Core Development | CI section | Package | Tiffany Rea |
| 5 | Core Development | CD section | Deploy | - |
| 6 | Expansion Development | Sec section | Secure | Will Meek |
| 7 | Expansion Development | Sec section | Govern | Harsha Muralidhar |
| 8 | Expansion Development | Fulfillment section | Fulfillment | Valerie Burton |
| 9 | Expansion Development | Fulfillment section | Fulfillment | Richard Chong |
| 10 | Expansion Development | Data Science section | ModelOps | - |
| 11 | Expansion Development | Data Science section | AI-powered | Ramya Authappan |
- FYI - There are no hiring plans for SETs in FY25.
OKRs
Every quarter, the team commits to Objectives and Key Results (OKRs). The below shows current quarter OKRs and is updated regularly as the quarter progresses.
Here is an overview of our current Test Engineering OKRs.
How we work
Project management
Iterations
- We plan our work in 2 weeks long iterations
- We maintain and regularly update Test Engineering team board. This board reflect the actual status of the ongoing work
Issue weights
We estimate every task during iteration planning. Our weighting strategy is based on Test Platform Weighting
| Weight | Description | Approximate time | Example issues |
|---|---|---|---|
| 1 | Trivial | ~1 hour | TBD |
| 2 | Small | ~0.5-1 day | TBD |
| 3 | Medium | ~3 days | TBD |
| 5 | Large | ~1 week | TBD |
| 8 | X-Large | ~2 weeks | TBD |
| 13+ | XXL | »2 weeks | TBD |
- Approximate time estimate - is time spent actively working on the issue: from design to requesting the review
- It is not manadatory to create Trivial tasks
- Consider breaking down Large tasks into smaller items
- XL and XXL tasks has to be broken down into smaller tasks and might require creating Spike issue first
Last modified March 25, 2024: Update Test Engineering team page - adding info about iterative work and issue weighting, fix links (
9a04f34d)
