Skip to content

Ensure test coverage for all paths in the trials_controller

What does this MR do and why?

To enable some of the refactorings called out by &10009 (closed) and plans seen in #393969 (closed) we need to ensure we have full flow testing at a feature spec(e2e) level.

  • We also will be looking to enable the specs to be as readable as possible as a way to reference as documentation a little easier.
  • We favor duplication and readability of the entire trial creation process over DRYness.
  • Remove duplicate tests once we have covered them in our new tests.
  • Move fully frontend dependent tests to the frontend as possible to get cheaper testing.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #393968 (closed)

Edited by Doug Stull

Merge request reports