Revamp testing - reorg, DRY etc.
Reorganize tests to be better organized, remove duplication.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Malini Kamalambal
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(kgriffs) I'm in favor of merging most of our "unit" tests with the functional tests (DRY). Let's not get hung up on pedantic test definitions, but just focus on test coverage more from the end-user perspective (black-box testing). At the end of the day, that is what really matters anyway. If we have a bunch of lower-level tests, that creates more churn and maintenance, since whenever any internal interface or behavior has even a minor change, we have to go update the white-box test(s) for that. We may have a handful of other tests that we have to do simply because it is too hard to provoke some edge cases through the front door, so to speak. But those should be the exception, not the rule.
See also:
* https:/
* https:/
