Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recreate legacy vscode-ui tests within new e2e framework #2586

Open
sagerb opened this issue Feb 11, 2025 · 0 comments · May be fixed by #2590
Open

Recreate legacy vscode-ui tests within new e2e framework #2586

sagerb opened this issue Feb 11, 2025 · 0 comments · May be fixed by #2590
Assignees

Comments

@sagerb
Copy link
Collaborator

sagerb commented Feb 11, 2025

The specs implemented within the vscode-ui test the following:

  1. (test/vscode-ui/test/specs/error-err-config.spec.ts): Confirm that errors in a config are displayed correctly (missing title).
  2. (test/vscode-ui/test/specs/error-no-config_creds.spec.ts): Confirm that the error is displayed when the associated config is not found for the selected deployment
  3. (test/vscode-ui/test/specs/fastapi.spec.ts): Create a deployment successfully for the fastapi-simple example, where the project is not nested under a subdirectory in the workspace. (test/sample-content/fastapi-simple) - opened VSCode directly into fastapi-simple subdirectory.
  4. (test/vscode-ui/test/specs/nested-fastapi-configuration.spec.ts): Create a deployment successfully for the fastapi-simple example, where the project is nested under a subdirectory in the workspace. (test/sample-content/fastapi-simple) - opened VSCode into the upper sample-content subdirectory.
  5. (test/vscode-ui/test/specs/nested-fastapi-deployment.spec.ts): Create a nested deployment for the fastapi-simple example, verify all of the sections and status, and successfully deploy to server.

These tests need to be covered within the new framework.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant