Show old tests / tests that don't get changed with code

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Release notes

Problem to solve

We know that old tests / tests that aren't updated when the mapped code is can cause failures in CI.

As a developer, I want to know if a test is "old" or hasn't been updated when the mapped code has, so that I can spot areas of tech debt that may cause bugs later.

Intended users

• Sasha (Software Developer) - who wants to know why a test continues to fail when the code looks bug free.
• Simone (Software Engineer in Test) - Who is looking for areas to do exploratory testing.
• Delaney (Development Team Lead) - Who wants to know which areas of a project are likely to house tech debt so that they can proactively review/fix before dealing with escaped defects

User experience goal

The user should be able to see a list of tests that haven't been modified in X days/weeks/some amount of time relative to the project or the mapped code in the UI so they can find tests that are likely to fail/can be removed.

Proposal

• This could be a report at the start or even a .csv download of test, days since modification, failures L14, mapped code, days since last modification.
• Add the data to the GitLabUI as a support in the quality report (hot spots?) and a full report or data view somewhere.
• Eventually add the API for test data
• Add tracking for views of the report/download/API Requests

Further details

Permissions and Security

Documentation

• Documentation for the new feature and what it requires -> test report upload and if mapping is part of the functionality a mapping file.

Availability & Testing

Available Tier

• Premium/Silver

What does success look like, and how can we measure that?

Acceptance Criteria

• A user can find the list and identify the test updated the longest time ago in the interface/in a downloaded file that can be sorted (yes another .csv download)
• Users of Projects with mapped tests (future functionality) can find the list above but finds code/test pairs with longest amount of time between test and code update.

What is the type of buyer?

The Team Lead/Director is most likely to be focused on this problem and buy the project level view to gain awareness.

Is this a cross-stage feature?

No.

Links / references

• Add .json map file support to tff