Enhanced/Expanded Testing
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 25
- Forks
- 67
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 2
Description
Description
Testing in the Framework is achieved via ~large system tests, not by modular unit tests. The contents of these system tests is diverse, and has expanded over time, so it's not clear what/where/how things are being tested.
Unit testing is not practical for most of the tests we need, so how do we design a testing harness that is manageable and extendible.
Solutions
It was discussed that at the very least we should document what is being tested in our existing systems tests, and to continue to do so going forward. Maybe this is enough?
Ultimately, Capgen will be embedded within several modeling systems, providing much more coverage testing than our system tests, but relying on application testing is not a great idea IMO.
Thoguhts?
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by inventorying the existing system tests and documenting what each currently covers. A complete outcome would define whether that documentation is sufficient or specify a manageable, extensible testing harness for the framework.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100