Repository navigation
Add e2e completion testing #2917
Description
Activity
Ideally the solution would also easily support testing locally. But CI is would be the minimum.
The solution must support testing locally and in CI. Having differences between the two is not a good idea.
@davidism I agree. I just don't know that that exists so I was hesitant to demand it as an initial requirement because we don't have anything. Do you have any ideas for direction.
argcomplete uses pexpect.
Currently it's a bit hard to know whether our completions actually work end-to-end. Whether when it's all installed, that we actually get the completions we're expecting in our API. It would be nice if we added some way that we could test this. This would've been helpful in #2846.
We might be able to use scrut to create a test for it. My team created this tool for our work and it basically allows you to easily create E2E tests. If you can make autocompletions show by running a command on the commandline, you can very easily make a scrut test out of that.