summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJesse Duffield <jessedduffield@gmail.com>2022-12-20 22:54:00 +1100
committerJesse Duffield <jessedduffield@gmail.com>2022-12-20 22:54:00 +1100
commit186b7197e48ef42cf409ae8dd4946432fedc40f2 (patch)
treef4a0f4d1a329bc7dfbb270af115a60dbebf81772
parent6ec88ce8ba3e357e727766dc73edb269d84a4fc2 (diff)
clean up some integration test stuff
-rw-r--r--.gitignore6
-rw-r--r--pkg/integration/README.md2
2 files changed, 3 insertions, 5 deletions
diff --git a/.gitignore b/.gitignore
index 9e9059b19..a1a0ebe21 100644
--- a/.gitignore
+++ b/.gitignore
@@ -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
diff --git a/pkg/integration/README.md b/pkg/integration/README.md
index c4d233d07..3c75792ed 100644
--- a/pkg/integration/README.md
+++ b/pkg/integration/README.md
@@ -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