Skip to content

"Go to test" button in merge request review

Problem to solve

When reviewing an MR I'm very often jumping between a class and then the test for that class but it takes me some time to find the test in the side bar and vice versa.

Intended users

User experience goal

Proposal

Some IDEs have a shortcut to simply jump to the test which matches the class/file you are looking at. Usually this is done by file name convention. For example in Ruby you just take the file name and look for the same file name with _spec.rb instead of .rb on the end inside the spec/ directory. This is a heuristic but it works well enough to be useful.

In VIM for example there are plugins that know about file name conventions to jump between "alternate" files which are pairs of class and test files since this is a very common workflow especially in TDD.

Further details

This was @cablett's awesome idea noted when doing some code review about how she misses this feature of Ruby Mine while doing code review.

Permissions and Security

Documentation

Availability & Testing

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

What is the type of buyer?

Is this a cross-stage feature?

Links / references