Is your feature request related to a problem? Please describe.
Regrettably, MMEDs automated testing code coverage is much lower than we would like. Some tests that have been planned have been commented out of the testing files due to their not working quite right. With the large changes coming to MMEDs, especially with issues like #385 and its associates, it will be more important than ever that it is robustly tested.
Describe the solution you'd like
Repair/complete partially existing tests, add host of relevant tests that do not yet exist.
Additional context
I'm looking at trying to separate studies and sequencing runs, and I'm getting very worried that with how integrated this system is to the entirety of MMEDs, these changes will have unexpected ramifications that we may not notice until too late due to low code coverage.
Is your feature request related to a problem? Please describe. Regrettably, MMEDs automated testing code coverage is much lower than we would like. Some tests that have been planned have been commented out of the testing files due to their not working quite right. With the large changes coming to MMEDs, especially with issues like #385 and its associates, it will be more important than ever that it is robustly tested.
Describe the solution you'd like Repair/complete partially existing tests, add host of relevant tests that do not yet exist.
Additional context I'm looking at trying to separate studies and sequencing runs, and I'm getting very worried that with how integrated this system is to the entirety of MMEDs, these changes will have unexpected ramifications that we may not notice until too late due to low code coverage.