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?
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?