Follow-up from "Add documentation about frontend test categories to frontend guide"

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

• Close this issue

The following discussion from gitlab-ce!21344 should be addressed:

• @iamphill started a discussion: (+1 comment)

  It tests that bundle works correctly yes. But how can we be certain that other JavaScript isn't interfering with the component? How can we be certain that it works correctly with the API rather than it being mocked? If we mock the API call & a backend engineer changes the response slightly, how can we be sure the feature still works?

  If we use rspec to fully test the feature, from login to sign out, we can be 100% certain that the feature works nicely in a GitLab environment. If we just test a single JS bundle we can't be certain of this & if we end up mocking all the API calls, we still can't be certain that something else isn't messing with our code.

  If engineers don't understand rspec then they should reach out for help. Plenty of people at GitLab are good at writing these tests and would be willing to help.

  edit: I see a section below about feature tests. So if we do feature tests, what benefit do we get with testing the page bundle? 🤷