MR: Pending <!-- NOTE: For context on MR heading, see: https://handbook.gitlab.com/handbook/engineering/development/dev/create/remote-development/index.html#relationship-of-issues-to-mrs --> ## Description NOTE: This is a followup from [this comment](https://gitlab.com/gitlab-org/gitlab-web-ide/-/issues/6#note_2372260527) on https://gitlab.com/gitlab-org/gitlab-web-ide/-/issues/6+s. The Workspaces E2E/QA specs do not actually test any behavior from within the workspace. Building on work done for the Web IDE integration testing in https://gitlab.com/gitlab-org/gitlab-web-ide/-/issues/6+s and other issues, we could leverage this for workspaces too. E.g., opening the terminal in VS Code, and asserting on things specified in the devfile, like filesystem mounts, postStart scripts, file/env secret settings, etc. ## Acceptance criteria TODO: Fill out (required) - [ ] [Describe what must be achieved to complete this issue.] - [ ] [If applicable, please provide design specifications for this feature/enhancement.] - [ ] [If applicable, please list any technical requirements (performance, security, database, etc.)] ## Implementation plan TODO: Fill out or delete (optional) [Provide a high-level plan for implementation of this issue, including relevant technical and/or design details.] <!-- NOTE: Feel free to expand with more sections and headers as needed --> <!-- DO NOT TOUCH BELOW -->