GitLab / Verify:Testing Speed Runs

Today we talked about our new category of Review Apps and Kyle walked us through a use case where the Failed Test counter has been helpful but the workflow is still clunky (then he recorded a video).

Review Apps Direction Page: https://about.gitlab.com/direction/verify/review_apps/
Kyle's Video: https://youtu.be/HvCCOUI8ZGo

Quick run through of the new feature to display Code Quality violation data in the Merge Request Changes Tab. For information about how to setup Code Quality please reference this video (https://www.youtube.com/watch?v=4pJcrvZfGQU) or the documentation link below.

Documentation: https://docs.gitlab.com/ee/user/project/merge_requests/code_quality.html
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/267612

Speed run explaining the Group Code Coverage Data feature.

Documentation: https://docs.gitlab.com/ee/user/group/repositories_analytics/#current-group-code-coverage

Feedback issue: https://gitlab.com/gitlab-org/gitlab/-/issues/231515

Speed run of the repeat failed test counter introduced in 13.8 showing how to see if a failed test has failed and how often on the default branch in the past.

Release Post: https://about.gitlab.com/releases/2021/01/22/gitlab-13-8-released/#repeat-failed-test-counter

https://gitlab.com/gitlab-org/gitlab/-/issues/33743

In this video I show how to setup the Code Coverage calculation on a simple Java project to be used as a Project Badge, display in a Merge Request and use with a simple bash file in a compare job.

This sample project can be found here: https://gitlab.com/jheimbuck_gl/java-code-coverage

The blog on how to publish code coverage reports to GitLab pages can be found here: https://about.gitlab.com/blog/2016/11/03/publish-code-coverage-report-with-gitlab-pages/

This is a demo to show how to configure a review app through the .gitlab-ci.yml file