-
Notifications
You must be signed in to change notification settings - Fork 292
Added test plan for TypeSpec extension #5552
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
base: main
Are you sure you want to change the base?
Conversation
deb90af
to
f01671f
Compare
Create image Add files via upload Update create-typespec-project-test-plan.md Create generate-client-code-from-typespec-test-plan.md Add files via upload Update generate-client-code-from-typespec-test-plan.md Create generate-openapi3-from-typespec-test-plan.md Add files via upload Update generate-openapi3-from-typespec-test-plan.md Update generate-openapi3-from-typespec-test-plan.md Create generate-server-stub-from-typespec-test-plan.md Add files via upload Update generate-server-stub-from-typespec-test-plan.md Add files via upload Create import-typespec-from-openapi3-test-plan.md
Update generate-server-stub-from-typespec-test-plan.md Update create-typespec-project-test-plan.md Create typespec-extension-basic-features-test-plan.md Add files via upload Update typespec-extension-basic-features-test-plan.md Update typespec-extension-basic-features-test-plan.md Add files via upload Update create-typespec-project-test-plan.md Update generate-client-code-from-typespec-test-plan.md Update generate-openapi3-from-typespec-test-plan.md Add files via upload Update generate-server-stub-from-typespec-test-plan.md Update import-typespec-from-openapi3-test-plan.md Update create-typespec-project-test-plan.md Update generate-client-code-from-typespec-test-plan.md Update generate-openapi3-from-typespec-test-plan.md Add files via upload Update generate-client-code-from-typespec-test-plan.md Add files via upload Update typespec-extension-basic-features-test-plan.md Update typespec-extension-basic-features-test-plan.md Update generate-client-code-from-typespec-test-plan.md Update generate-openapi3-from-typespec-test-plan.md Update create-typespec-project-test-plan.md Add files via upload Update generate-openapi3-from-typespec-test-plan.md
@microsoft-github-policy-service agree company="Microsoft" |
packages/typespec-vscode/test/manual/create-typespec-project-test-plan.md
Outdated
Show resolved
Hide resolved
packages/typespec-vscode/test/manual/create-typespec-project-test-plan.md
Outdated
Show resolved
Hide resolved
packages/typespec-vscode/test/manual/create-typespec-project-test-plan.md
Outdated
Show resolved
Hide resolved
packages/typespec-vscode/test/manual/create-typespec-project-test-plan.md
Outdated
Show resolved
Hide resolved
packages/typespec-vscode/test/manual/typespec-extension-basic-features-test-plan.md
Outdated
Show resolved
Hide resolved
packages/typespec-vscode/test/manual/import-typespec-from-openapi3-test-plan.md
Outdated
Show resolved
Hide resolved
packages/typespec-vscode/test/manual/generate-client-code-from-typespec-test-plan.md
Outdated
Show resolved
Hide resolved
packages/typespec-vscode/test/manual/generate-openapi3-from-typespec-test-plan.md
Outdated
Show resolved
Hide resolved
packages/typespec-vscode/test/manual/generate-from-typespec-test-plan.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Talking with the team
- this is still a lot of images which when I look at it provide very little value but add size to this repo, they just show basic vscode UI and folder structure which could just be very well be described with a few words and be easier to maintain
- manual test are still a nightmare to deal with and put a lof of extra work on us as well
- There is already quite a few prs in progress that are changing things
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually we are making some progress in the ui-automation and we may go to that approach directly. A quick question, does our CI machine have UI? or are we able to have some machine with UI in CI so that we will be able to run these UI test in CI? thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't the ui run headless, windows is super slow in ci and Linux doesn't.
None of the other ui test we have have any issues
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where are these ui test? We would like to have a look into them
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is 2(3 if you include the azure repo)
- packages/playground-website
test:e2e
script that runs playwright - packages/typespec-vscode itself that runs the basic browser smoke test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cool, thx! @msyyc , could you help to double check these tests and see whether there is anything our ui-test can leverage? thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copy that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://github.com/vitest-dev/vscode/tree/main/test-e2e vitest vscode extension also has a bunch of ui test, also running with playwright+ vitest
All changed packages have been documented.
|
Hi @@xiaohua899. Your PR has had no update for 30 days and it is marked as a stale PR. If it is not updated within 30 days, the PR will automatically be closed. If you want to refresh the PR, please remove the |
fix #5444
Description
Added four test scenarios test plan to TypeSpec Extension:
@RodgeFu and @msyyc for notification.