You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose a more direct structure for testing, where there are only a very limited number of "main" config directories, and various permutations for testing are not written out in more config directories, but instead manipulated directly in the Python of the test.
I am proposing a new structure for writing example tests.
Currently, we write most examples using layered config directories. For example, here we look for settings in three different directories:
activitysim/activitysim/examples/prototype_mtc/test/test_mtc.py
Lines 34 to 39 in 739c2e4
As we have more complicated testing permutations, these can get messy and hard to maintain:
activitysim/activitysim/examples/prototype_mtc_extended/test/test_mtc_extended.py
Lines 86 to 137 in 739c2e4
I propose a more direct structure for testing, where there are only a very limited number of "main" config directories, and various permutations for testing are not written out in more config directories, but instead manipulated directly in the Python of the test.
https://github.com/camsys/sandag-abm3-example/blob/6092354290a45aa4b771a8c18910b8bb4cd952de/test/test_sandag_abm3.py#L217-L239
cc @i-am-sijia @dhensle
The text was updated successfully, but these errors were encountered: