summaryrefslogtreecommitdiff
path: root/test/end-to-end/cli
AgeCommit message (Collapse)Author
2025-02-14end-to-end: Add add-to-cas --resolve-special test...Paul Cristian Sarbu
...that checks if symlinks are treated the same as in just-mr.
2025-01-22Add test verifying git cas is taken into accountKlaus Aehlig
2025-01-09just build: add new option -pKlaus Aehlig
... allowing to print the unique artifact built (if any). This allows convenient inspection of the build result of targets that define precisely one artifact.
2024-12-06Log: report outputs of failed actions by defaultKlaus Aehlig
Some actions are allowed to fail, typically tests. By reporting the output of failed such actions early, the user can already have a look at those artifacts, typically a test log, while the build is still going on.
2024-09-23Reorder dependencies and remove duplicates in OSSMaksim Denisov
2024-08-28Add basic sanity check on the default outputKlaus Aehlig
2024-08-26Add test to check that we ignore Git magic names in treesPaul Cristian Sarbu
2024-08-26install-cas --archive: Fix empty directories not added to archivePaul Cristian Sarbu
Also add empty directory in test script to ensure we don't regress in the future. While there, fix some typos.
2024-08-21tests: use newly defined test suiteKlaus Aehlig
... so that linting information gets propagated properly.
2024-06-25describe: also describe "configure" targets in more detailKlaus Aehlig
Most built-in rules are just described by their name, assuming they are known to the user anyway. One exception, however, are "export" targets, as those serve as interfaces to (logical) repositories and hence is supposed to have a documentation of the target itself. Over time, however, "configure" targets have evolved to become internal interfaces (maybe even for an external target), e.g., to provide default values and hence make better use of the actual export target. Therefore it is desirable to provide a bit more information when asked to describe a "configure" target. - As "configure" targets have a fixed set of keys, adding a "doc" field is a conservative extension; this can be useful to give an overview what the target is about. - An important information of a "configure" target is the target that is configured. While this, in general, is an expression, in the typical cases, the description is very short (a literal target name, or a variable). So we can afford to show the definition.
2024-06-03test: Use own installed just and just-mr targets...Paul Cristian Sarbu
...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.
2024-04-24just analyse: add --dump-result command line optionAlberto Sartori
The result of the analysis is a JSON object containing the keys `"artifacts"`, `"runfiles"`, and `"provides"`. This JSON object, by default, is logged. However, it might be useful to process the data contained in it, while, for example, developing new rules. This patch adds a new command line option (`--dump-result`), reserved to the subcommand `analyse`, to dump the analysis result to the given file or stdout (if `-` is given).
2024-04-12Target analysis: report short names of targets when describing a conflictKlaus Aehlig
Configured targets, by design, cannot distinguish between a value not occuring in the configuration and occuring there with value null. Therefore, to understand the conflict, we can as well drop all the null values of the target configuration when reporting it.
2024-04-10Add end-to-end test verifying restricted console loggingKlaus Aehlig
2024-04-05Add test verifying origin reporting in case of conflictsKlaus Aehlig
2024-03-28Add a test verifying the reproducibility of the archiveKlaus Aehlig
2024-02-13Add test that also for trees in the git cas we can follow pathsKlaus Aehlig
For a user `just install-cas` will show an entry without revealing where it found it---as it is content-addressable, it does not matter. Therefore, verify that accessing paths of a tree object also works regardless of where the tree is stored.
2024-02-05end-to-end tests: inherit pathKlaus T. Aehlig
... 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.
2024-01-24Add a test verifying that just-mr reports the correct tool namesKlaus Aehlig
... regardless of the names chosen during packaging.
2023-12-14just analyse: support dumping the provides map of a targetKlaus Aehlig
2023-12-12Tests: Verify copy overwrite of symlink with fileOliver Reiche
2023-11-13test: Verify unlink of symlinksOliver Reiche
2023-08-11Add basic end-to-end test for build -PKlaus Aehlig
... also verifying that we can look into tree outputs
2023-08-08Add a test verifying the overwrite property of install and install-casKlaus Aehlig
Verify that install and install-cas do not overwrite and instead replace existing files. This behaviour is less surprising for the user in the presence of hard links.
2023-06-05Add a test verifying that no working directory is neededKlaus Aehlig
2023-05-24Split off tests into a separate logical repositoryKlaus Aehlig
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.
2022-10-12Add copyright and license notice to all source and header filesKlaus Aehlig
Signed-off-by: Goetz Brasche <goetz.brasche@huawei.com>
2022-08-19main: honor configuration for target_file nameKlaus Aehlig
... also when determining default module or target.