Skip to content
This repository has been archived by the owner on Oct 3, 2023. It is now read-only.

Convert another configuration test to a unit test #29

Closed
cyrille-artho opened this issue Feb 1, 2019 · 3 comments
Closed

Convert another configuration test to a unit test #29

cyrille-artho opened this issue Feb 1, 2019 · 3 comments

Comments

@cyrille-artho
Copy link
Owner

This is useful in particular to find issues with static fields that do not get reset when re-running run (from a test harness) instead of main as a process. The same issue may appear (much more likely/often) with Main.run in Modbat.

@cyrille-artho
Copy link
Owner Author

This seems to work, but please remove the redundant test Choose00-2 now and use instead a test of the new setWeight models.

cyrille-artho added a commit that referenced this issue Feb 20, 2019
Unit test and partial integration of new features (weight, invocation): #26, #28, #29, #32
@cyrille-artho
Copy link
Owner Author

cyrille-artho commented Feb 20, 2019

We need one more configuration test to close this issue. There are several Modbat tests that presumably cover configuration issues, but no smaller tests for only the configuration.
The best way to have another test is to migrate an existing test (from bin/test.sh) and remove it there.
The current test should also be reviewed and removed from bin/test.sh. Log files that are no longer needed should also be removed.

@cyrille-artho
Copy link
Owner Author

This issue is subsumed by issue #55.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant