Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Verify:Testing Group

Vision

We provide confidence in software through the delivery of meaningful, actionable automated testing results in GitLab.

Mission

The Verify:Testing Group provides automated testing integration into GitLab. We aim to allow software teams to be able to easily integrate many layers of testing into their GitLab CI workflow including:

We want software teams to feel confident that the changes they introduce into their code are safe and conformant.

Team Members

The following people are permanent members of the Verify:Testing group:

Person Role
Daniel Cipoletti Frontend Engineering Manager, Verify
Dimitrie Hoekstra Product Designer, Verify (CI)
Nadia Udalova UX Manager, Release and Verify
Juan J. Ramirez Senior Product Designer, Verify
Lorie Whitaker Senior UX Researcher, Release and Verify & Enablement
Marcel Amirault Technical Writer, Verify
Miranda Fluharty Frontend Engineer, Verify:Testing
Ricky Wiens Backend Engineering Manager, Verify:Testing
Scott Hampton Frontend Engineer, Verify:Testing
Zeff Morgan Senior Software Engineer in Test, Verify:Testing
James Heimbuck Senior Product Manager, Verify:Testing
Drew Cimino Backend Engineer, Verify:Testing
Erick Bajao Senior Backend Engineer, Verify:Testing
Maxime Orefice Backend Engineer, Verify:Testing

Stable Counterparts

The following members of other functional teams are our stable counterparts:

Person Role
Dimitrie Hoekstra Product Designer, Verify (CI)
Cheryl Li Backend Engineering Manager, Verify:Continuous Integration
Zeff Morgan Senior Software Engineer in Test, Verify:Testing
Tiffany Rea Software Engineer in Test, Verify:Continuous Integration
James Heimbuck Senior Product Manager, Verify:Testing
Thao Yeager Senior Product Manager, Verify:Continuous Integration
Darren Eastman Senior Product Manager, Verify:Runner
Juan J. Ramirez Senior Product Designer, Verify
Marcel Amirault Technical Writer, Verify

Technologies

Like most GitLab backend teams we spend a lot of time working in Rails on the main GitLab app. Familiarity with Docker and Kubernetes is also useful on our team.

Our Repositories

How we work

Workflow

Unless specifically mentioned below, the Verify:Testing group follows the standard engineering and product workflows.

Meetings

We meet on a weekly cadence for two separate meetings. Typically we conduct both of these meetings sequentially.

Testing Group Weekly Meeting

This synchronous meeting is to discuss anything that is blocking, or notable from the past week. This meeting acts as a team touchpoint.

Testing Group Refinement Meeting

This synchronous meeting is to refine and triage the current and next milestone's issues. In this meeting we should be: discussing priority, sizing issues, estimating the weight of issues, keeping track of our milestone bandwidth and removing issues appropriately.

Async Daily Standups

We use geekbot integrated with Slack for our daily async standup. The purpose of the daily standup meeting is to keep the team informed about what everyone is working on, and to surface blockers so we can eliminate them. The standup bot will run at 10am in the team members local time and ask 2 questions:

  1. What will you do today?
  2. Anything blocking your progress?

Release planning issue

We use a release planning issue to plan our release-level priorities over each milestone. This issue is used to highlight deliverables, capacity, team member holidays, and more. This allows team members and managers to see at a high-level what we are planning on accomplishing for each release, and serves as a central location for collecting information.

Definition of Ready

Before the team will accept an issue into a milestone for work it must meet these criteria:

Definition of Done

GitLab has a documented Definition of Done for contributions to GitLab. We will follow that standard for our own definition of done.

How to work with us

On issues

Issues worked on by the testing group have a group label of ~"group::testing". Issues that contribute to the verify stage of the devops toolchain have the ~"devops::verify" label.