#85: Ensure the milena/tests/ hierarchy follows milena/mln/'s one -----------------------+---------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: task | Status: new Priority: critical | Milestone: Olena 1.0 Component: Milena | Version: 1.0 Resolution: | Keywords: -----------------------+---------------------------------------------------- Description changed by freling:

Old description:

source:trunk/milena/mln/ and source:trunk/milena/tests/ shall be parallel, with some exceptions (for instance, the reproducing the sub- hierarchy of source:trunk/milena/mln/core into source:trunk/milena/tests/core might be overkill).

Moreover :

• File names should match.
• Create a script to detect discrepancies (possibly supporting a list of

exceptions) between files names in `milena/mln/` and `milena/tests/`.

New description:

source:trunk/milena/mln/ and source:trunk/milena/tests/ shall be parallel, with some exceptions (for instance, the reproducing the sub-hierarchy of source:trunk/milena/mln/core into source:trunk/milena/tests/core might be overkill).

Moreover : * File names should match. * Create a script to detect discrepancies (possibly supporting a list of exceptions) between files names in `milena/mln/` and `milena/tests/`.

You can run 'check_source_has_test.sh path/to/mln path/to/tests' in source:trunk/build-aux/ in order to see which source does not have an associated test.

--