LFS Testing Review
Through customer interactions, we have found a series of problems using LFS-related features with Geo. Some of these problems have been specific to Geo (gitlab-org/gitlab#10286 (closed) and gitlab-org/gitlab#32696 (closed)) and others have been general to GitLab (gitlab-org/gitlab#36628 (closed) and gitlab-org/gitlab#20042 (closed)).
Geo is a feature connected to data-retention and we need to be in a position where we can demonstrate that it is solid. So I would like to propose a type of audit where we review the tests in place for LFS-related features, and I think we need to cover both the base GitLab features and the Geo-enabled ones.
The types of tasks I have in mind are:
-
Confirm that the test cases we have are useful and valid -
Determine if there are any other tests needed to cover the base use cases -
Work with Backend Engineers to list edge cases in functionality and cover these with automated tests -
Work with Support Engineers to understand any LFS-related support queries that have escalated into bugs and determine if these should be covered by automated tests
The end result of this audit should be that:
- We have confidence in the test coverage for use cases and edge cases
- We can share that confidence with customers through some sort of coverage report