summaryrefslogtreecommitdiff
path: root/test/e2e/config.go
diff options
context:
space:
mode:
authorPaul Holzinger <paul.holzinger@web.de>2020-12-07 15:50:56 +0100
committerPaul Holzinger <paul.holzinger@web.de>2020-12-09 19:13:28 +0100
commit2870a0b0a6b94528b82df7cee57c8c6a0252fc85 (patch)
tree92f41fa56baaf9ce3393478d04b1f93e521c6582 /test/e2e/config.go
parent7caef9c497da0c2a16caf4f15152bc543dfb6008 (diff)
downloadpodman-2870a0b0a6b94528b82df7cee57c8c6a0252fc85.tar.gz
podman-2870a0b0a6b94528b82df7cee57c8c6a0252fc85.tar.bz2
podman-2870a0b0a6b94528b82df7cee57c8c6a0252fc85.zip
Add system test for shell completion
There exists a unit test to ensure that shell completion functions are defined. However there was no check about the quality of the provided shell completions. Lets change that. The idea is to create a general test that makes sure we are suggesting containers,pods,images... for the correct commands. This works by reading the command use line and checking for each arg if we provide the correct suggestions for this arg. It includes the following tests: - flag suggestions if [options] is set - container, pod, image, network, volume, registry completion - path completion for the appropriate arg KEYWORDS (`PATH`,`CONTEXT`,etc.) - no completion if there are no args - completion for more than one arg if it ends with `...]` The test does not cover completion values for flags and not every arg KEYWORD is supported. This is still a huge improvement and covers most use cases. This test spotted several inconsistencies between the completion and the command use line. All of them have been adjusted to make the test pass. The biggest advantage is that the completions always match the latest command changes. So if someone changes the arguments for a command this ensures that the completions must be adjusted. Signed-off-by: Paul Holzinger <paul.holzinger@web.de>
Diffstat (limited to 'test/e2e/config.go')
0 files changed, 0 insertions, 0 deletions