Age | Commit message (Collapse) | Author |
|
This test uses a file repository at "." with the "to_git" pragma.
Now, if we build the tool to be tested in debug mode, the sources
end up in the test's action directory. If we take the work dir
of the simulated use case top level, all these sources end up
unnecessarily in the workspace root of the test repo. Avoid this
overhead by moving to a subdirectory.
|
|
While there, remove tray cat whitesapce and redetermine the working
directory instead of relying on the environment.
|
|
|
|
... verifying that indiections are correctly taken into account.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
... so that linting information gets propagated properly.
|
|
...which do not stage also the debug source and header files (while
in debug mode), as this is unnecessary bloat in the tests.
As the tool-under-test and mr-tool-under-test targets should be
used instead of the regular install targets also in the various
extra rules in end-to-end and utils, move their definition in the
outmost test TARGETS file.
|
|
... in particular that of the absent pragma which is addressed both,
in imports as well as in deduplication.
|
|
... to generic actions, in order to not rely on "standard paths"
being pulled in.
|
|
... i.e., the values for "mirror" and "inherit env"
|
|
... for test actions, by setting an appropriate local launcher. In
this way, the tests can also be run on systems where sh does not
pull in enough paths to have all the "usual" tools available.
|
|
... verifying that deduplication does not modify the analysis
result.
|
|
This allows better separation and, in particular, repositories
needed only for tests do not have to be provided for building the
tools. This also better documents which dependencies are only needed
for testing.
|
|
... and, in particular, do not read any rc files for just-mr
the user might have.
|
|
|