mirror of
https://github.com/jesseduffield/lazygit.git
synced 2025-05-11 12:25:47 +02:00
clean up some integration test stuff
This commit is contained in:
parent
6ec88ce8ba
commit
186b7197e4
2 changed files with 3 additions and 5 deletions
6
.gitignore
vendored
6
.gitignore
vendored
|
@ -42,11 +42,7 @@ test/integration/*/used_config/
|
|||
test/integration/*/expected/**/hooks/
|
||||
test/integration/*/expected_remote/**/hooks/
|
||||
|
||||
test/integration_new/**/actual/
|
||||
test/integration_new/**/used_config/
|
||||
# these sample hooks waste too much space
|
||||
test/integration_new/**/expected/**/hooks/
|
||||
test/integration_new/**/expected_remote/**/hooks/
|
||||
test/integration_new/**
|
||||
|
||||
oryxBuildBinary
|
||||
__debug_bin
|
||||
|
|
|
@ -61,6 +61,8 @@ The name of a test is based on its path, so the name of the test at `pkg/integra
|
|||
|
||||
You can pass the KEY_PRESS_DELAY env var to the test runner in order to set a delay in milliseconds between keypresses, which helps for watching a test at a realistic speed to understand what it's doing. Or you can pass the '--slow' flag which sets a pre-set 'slow' key delay. In the tui you can press 't' to run the test in slow mode.
|
||||
|
||||
The resultant repo will be stored in `test/integration_new`, so if you're not sure what went wrong you can go there and inspect the repo.
|
||||
|
||||
### Running tests in VSCode
|
||||
|
||||
If you've opened an integration test file in your editor you can run that file by bringing up the command panel with `cmd+shift+p` and typing 'run task', then selecting the test task you want to run
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue