click icon indicating copy to clipboard operation
click copied to clipboard

Add e2e completion testing

Open AndreasBackx opened this issue 7 months ago • 4 comments

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.

AndreasBackx avatar May 14 '25 21:05 AndreasBackx

Ideally the solution would also easily support testing locally. But CI is would be the minimum.

Rowlando13 avatar Jul 08 '25 03:07 Rowlando13

The solution must support testing locally and in CI. Having differences between the two is not a good idea.

davidism avatar Jul 08 '25 04:07 davidism

@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.

Rowlando13 avatar Jul 09 '25 00:07 Rowlando13

argcomplete uses pexpect.

davidism avatar Jul 09 '25 00:07 davidism