tests/std: Separate STL/MSVC internal tests and standards compliance tests
Open
Nobody has claimed this yet.
test
- Dominant language
- C++
- Stars
- 11.1k
- Forks
- 1.7k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 22
Description
The tests added by #498 under std include both STL/MSVC specific tests and tests to check standards compliance.
The two types of tests should be separated so that others can easily reuse our tests as we did with libcxx.
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 reviewing the tests added by #498 under std and identify which cover STL/MSVC-specific behavior versus standards compliance. Separate those two categories so the compliance tests can be reused similarly to the libcxx tests; completion means the two types are clearly organized apart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100