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
The current layout of the tests directory is overly complicated and has confusing folder names (e.g. outputs inside of an inputs root folder).
The complexity of this structure is expected to increase over time.
Suggested solution:
move test and verification data next to the tests, where applicable (see 2.) Pros:
easier to write new tests
easier to understand how a test works and where its inputs come from
Cons:
mixes code with assets
for global inputs (models, .linx/y files that are used by different test modules), a global testassets folder makes sense. naming has to be chosen carefully.
The text was updated successfully, but these errors were encountered:
Issue
The current layout of the
tests
directory is overly complicated and has confusing folder names (e.g.outputs
inside of aninputs
root folder).The complexity of this structure is expected to increase over time.
Suggested solution:
move test and verification data next to the tests, where applicable (see 2.)
Pros:
Cons:
for global inputs (models,
.linx/y
files that are used by different test modules), a globaltestassets
folder makes sense. naming has to be chosen carefully.The text was updated successfully, but these errors were encountered: