<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=421669) </details> <!--IssueSummary end--> ## Problem statement The current e2e test only captures the happy path i.e. creation of a workspace followed by termination as cleanup. Now that RD support capture/reporting of applier errors, perhaps additional specs can be added to the e2e tests to simulate/verify this case as well ## Acceptance Criteria - [ ] An additional e2e spec that sets up the system such that creation of a workspace results in an applier error in Gitlab Agent. This error should be eventually be visible in the UI and the workspace should have its `actual_state` set to `Error`. The test could then be cleaned up by terminating the workspace until its not longer visible in the workspaces list - [ ] If possible, the new e2e spec should be locally runnable ## Technical Requirements - [ ] Verify that an applier error can be consistently be induced in Gitlab Agent. One way could be to create a valid devfile yaml for the test workspace and then override it in the DB with an invalid value before Gitlab Agent is set up - [ ] Create a new e2e spec that verifies that applier errors can be successfully reported by Gitlab Agent to the rails service ## Design Requirements NA ## Impact Assessment There should be no impact as this should be only a spec ## User Story NA