GitLab / Quality Department

No description provided.

Quality department Group Conversation Highlights for 2022-05-23

Just a short introduction on how Contract testing is executed.

No description provided.

No description provided.

No description provided.

https://about.gitlab.com/handbook/engineering/quality/performance-indicators/

No description provided.

No description provided.

No description provided.

No description provided.

Showing how functional testing of large merge request work and how to execute them.

Nick Westbury (Sr. SET for Gitaly) demonstrates Gitaly Failover on our 50K reference architecture.

No description provided.

The Quality Department training on calendar time management https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/441

No description provided.

Quality Department March 2021 Key Review Prep

End to End Test Pipeline Failure Debugging using Pry

Intended as an extension of existing videos:

Quality Team: Failure Triage Training - Part 1
https://www.youtube.com/watch?v=Fx1DeWoTG4M&list=PL05JrBw4t0KpZUzlEnvlvBtf_NwShU_ot&index=18 (36 min)

Quality Team: Failure Triage Training - Part 2
https://www.youtube.com/watch?v=WeQb8GEw6PM&list=PL05JrBw4t0KpZUzlEnvlvBtf_NwShU_ot&index=17 (34 min)

A 3 minute overview on how to diagnose a spike in bug mean time to close KPI using the shared dashboard

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

This video is a quick demonstration of how to use the GitLab QA orchestration tool to run our end-to-end tests against a self-managed instance.

Example of command used:

gitlab-qa Test::Instance::Any EE:13.6.2-ee http://gitlab.test -- qa/specs/features/browser_ui/3_create/merge_request/create_merge_request_spec.rb

For more info see:

GitLab QA README: https://gitlab.com/gitlab-org/gitlab-qa/-/blob/master/README.md
GitLab QA Scenarios: https://gitlab.com/gitlab-org/gitlab-qa/-/blob/master/docs/what_tests_can_be_run.md
E2E info for GitLab developers: https://docs.gitlab.com/ee/development/testing_guide/end_to_end/
Orchestrated end-to-end tests at GitLab - Part 1: https://youtu.be/wWC7r3l0u1Y
Orchestrated end-to-end tests at GitLab - Part 2: https://youtu.be/U8zCle_Up6I
How to run an end-to-end test interactively (debugging): https://youtu.be/SO2U8gpLSeM
Quality Department Handbook: https://about.gitlab.com/handbook/engineering/quality/

In this video, GitLab Senior Software Engineer in Test Sanad Liaquat talks about Orchestrated end-to-end tests and how to run them. He also discusses the code briefly especially the Test Scenarios, the Components and how gitlab-qa calls the Test Scenarios in the /qa directory of the GitLab project.

Deck: https://docs.google.com/presentation/d/15F7kUyHxGuudJoMzqytzw5L9ApiyzQ5aQ0apId7dVo8/edit?usp=sharing

This is the first video in a two part series. The second video can be found here: https://youtu.be/U8zCle_Up6I

In this video, GitLab Senior Software Engineer in Test, Sanad Liaquat talks in detail about the different steps involved in writing orchestrated end-to-end tests including how to run the tests on local against the GDK and on CI before merging the MRs, how to publish a new version of the gitlab-qa gem and where to add CI jobs for new test scenarios.

Deck: https://docs.google.com/presentation/d/1e_Pkw2OubI_L1eJDrvjKCNo6g-9eDXILLfNmfiXf8xM/edit#slide=id.p1

This is the second video in a two part series on Orchestrated end-to-end tests. The first video can be found here: https://youtu.be/wWC7r3l0u1Y

No description provided.

No description provided.

Tanya Pazitny and Kyle Wiebers troubleshooting Quad Planning Dashboard

This is a discovery and scoping discussion about how we can improve the project import process with sample data that can benefit both the quality performance tests and customer-facing demos with rich data. The quality team has rake tasks that use the Faker package to generate large quantities of sample data and the Customer Success team uses a custom built Demo Designer UI application and database that then uses the GitLab API to import the created records into a GitLab instance.

The mutual outcome of this discussion is the creation of a "demo-data-as-code" approach using YAML or JSON that is sequenced similar to how CURL calls to the API would be. This allows different ways to create the demo data with different tools but a common output that can then be parsed by GitLab's project import and future group import abilities.

Learn more in the issue.
https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/7397.

Participants:
Mek Stittri (Director of Quality Engineering)
Jeff Martin (Sr Demo Systems Engineer - Customer Success)
Kyle Wiebers (Quality Engineering Manager, Engineering Productivity)

Demo of multi-modal test code. This demo shows how we can change out end-to-end tests to test both the API and UI in the same test file. This has the advantage of running faster and still gives us the flexibility to choose if we want to prioritize speed or to test the UI.

Link to issue: https://gitlab.com/gitlab-org/gitlab/-/issues/212390
Link to demo code: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/27964/diffs

CORRECTION: it should be 'export ELASTIC_URL="http://localhost:9200"' at time index 2:40

No description provided.

In this call Sid and Mek discuss the pain points in digesting the information in the Scaling and Availability page.

No description provided.

In this video we went over the department list of projects and roadmap page.
https://about.gitlab.com/handbook/engineering/quality/project-management/
https://about.gitlab.com/handbook/engineering/quality/roadmap/

Incident report details in https://gitlab.com/gitlab-com/gl-infra/production/issues/1498
RCA issue https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/8729
Feature issue https://gitlab.com/gitlab-org/gitlab/issues/36709

Kyle Wiebers, Quality Engineering Manager, Engineering Productivity at GitLab, gives an overview of how we use Insights at GitLab to monitor trends in workflow, bugs, merge requests and more.

Walkthrough of the tool and how to set it up

In this video, we walk through some parts of the GitLab QA framework that is used for writing end-to-end tests for the GitLab application.

Demo from Quality Team Pt. 2 meeting on 2019-11-14

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

No description provided.

An informal chat demoing how the Quality team is using some great GitLab features to document their roadmap. https://about.gitlab.com/handbook/engineering/quality/roadmap/

This is a part of an on-going series aiming to train team members on the triage process and the automated tooling we have at GitLab.

No description provided.

In this video, Mek and Walmyr are showing how to use Gmail filters to organize your inbox.

Mek's filter export: https://drive.google.com/file/d/1vm_psZOXjYZ9ulKYmdMqrTk435KcR1DL/view?usp=sharing

No description provided.

Beginning of discussion by quality team on how we quickly respond to failing quality pipelines and quarantine necessary tests for further investigation.

Follow up discussion by quality team on how we investigate failing quality pipelines using the original containers tests were executed on.

In this video, our Dan Davison Sr. Test Automation Engineer gives a demo on how we implemented dynamic locator validation in our Ruby Page Objects.

In this video, our Sanad Liaquat Sr. Test Automation Engineer gives a demo on how we use Artillery.io to generate load for Performance Tests.

No description provided.