microsoft / microsoft/vscode-java-test
Aggregation of Runtimes for a Testclass
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 340
- Forks
- 173
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 18
Description
Version
0.39.0
Description
When a test class runs independent tests, the testing panel on the left displays the execution times for each test as well as an aggregated sum for the complete test class, which is fine.
When the test class includes a static setup method to create a class fixture, tagged with Unit5's @BeforeAll , the execution for setting up the fixture is not taken into account for the whole class, which still only sums up the execution times for each individual tests. This may lead to some unexpected results, where the test panel displays a test class execution time sum < 1s, whereas the creation of the fixtures already requires > 10s.
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 by tracing how the testing panel aggregates individual test runtimes into the test-class total, then follow the handling of static @BeforeAll setup fixtures. Reproduce the discrepancy with a fixture that takes longer than its tests, and consider the work done when the class total includes that setup duration and a regression test covers it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100