In automated testing, separate unit tests from longer verification tests
Open
enhancement
testing
- Dominant language
- MATLAB
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
At some point we will want to run verification tests that may take a long time. Let's create a structure for that to happen separately from unit tests that are meant to run very quickly.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files or tests. Start by inspecting the repository's existing automated and unit-test layout, then determine how long-running verification tests should be separated. Done means the repository has a clear separate structure while quick unit tests remain independently runnable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- matlab
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100