DX: introduce `_CANVAS_E2E_TESTS: true` to improve development velocity and reduce CI cost
>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3557842. --> Reported by: [wim leers](https://www.drupal.org/user/99777) Related to !325 >>> <h3 id="overview">Overview</h3> <p>I'm often working on MRs that touch only low-level pieces of the back-end, and would never cause any e2e test failure. Most recent examples: <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/canvas/-/work_items/3541361" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/canvas/-/work_items/3541361</a></span>, <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/canvas/-/work_items/3557612" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/canvas/-/work_items/3557612</a></span>.</p> <p>Sometimes "never" is too strong, but it'd be pointless to run e2e tests all the time during early development. <strong>So I find myself &hellip;&nbsp; manually canceling e2e tests. &#128517;</strong></p> <p>Potential follow-up: automatically set this to <code>false</code> in a draft MR?</p> <h3 id="proposed-resolution">Proposed resolution</h3> <p>Introduce</p> <pre>&nbsp; # Enable Canvas contributors to change this from `true` to `false` to disable e2e tests.<br>&nbsp; # (Useful when early in an MR and/or developing low-level functionality that is unlikely to affect e2e tests.)<br>&nbsp; _CANVAS_E2E_TESTS: true</pre><h3 id="ui-changes">User interface changes</h3> <p>None.</p>
issue