FY21-Q4 KR: Build test tooling to reproduce transient issues => 92%

Requirements

• New set of end-to-end tests that can run in CI and against local GDK
• The test itself repeats actions that are known to be flaky e.g.
  • Create suggestion and apply suggestion x10 times, do line 1 and crawl down to line 10 on a file
  • Enable merge trains, refresh page 10x and ensure that MR is not stuck => gitlab-org/gitlab#35562 (closed)
• This new test will throttle memory of browser under test
• Boring solution iterating on top of the existing QA framework.

As such the next steps would be:

• Work on option to throttle chrome memory for a select suite - We already have the capability to simulate slow network as mentioned here
• Create Transient Bugs Detector TestSuite - Add new suite of tests above - Use the Page Objects in the QA framework and add create a new set of test for the below mentioned scenarios. https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/759 => 75%, Job to simulate slow connections - done, first test is completed
  • Setup a CI job which runs these tests with slow connection simulators.
  • Create suggestion and apply suggestion x10 times, do line 1 and crawl down to line 10 on a file in review
  • Enable merge trains, refresh page 10x and ensure that MR is not stuck
• Allow running of tests against GDK https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/761
• Add documentation and communicate for development team in WG to use https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/762 => documentation added, communication - yet to do => 50%