redhat-developer / redhat-developer/vscode-quarkus
Unit Testing Very Slow with VSCode
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 79
- Forks
- 31
- Avg merge
- 12h 51m
- Merged PRs (30d)
- 6
Description
Hi Team,
We use cmder in windows and after some followup was able to run the applicaiton fine in vscode.
Details at https://gist.github.com/debu999/042e33b556fd253f5f28e43559c0af21 May be something can be added to have a debug quarkus app with cmder might help others.
Regarding Unit Testing our applicaiton uses the following
- MongoDB
- Kogito
- Kafka
- Elastic Search
- OIDC
- GraphQL
- Rest APIs
Test suite have roughly 650 tests and takes ~ 2min in intelij.
In VSCODE it takes a lot more than that. Just for 1 test case takes 3min.
Is there anything to fix for the testing. Any VMArgs/Env etc.
There is no docs anywhere to test in java. Help on it. VSCode testing is unusuable.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked gist and the VSCode testing setup, then reproduce the difference between IntelliJ and VSCode using the reported Java application and test suite. Compare the runtime of one test and the full suite; done means identifying a specific configuration or tooling cause and documenting a verified improvement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, graphql, java, kafka, mongodb, vscode
- Domain
- developer-experience, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100