@@ -40,12 +40,6 @@ cat > test-applications/my-new-test-application/.npmrc << EOF
40
40
@sentry-internal:registry=http://localhost:4873
41
41
EOF
42
42
43
- # Add a gitignore that ignores lockfiles
44
- cat > test-applications/my-new-test-application/.gitignore << EOF
45
- yarn.lock
46
- package-lock.json
47
- EOF
48
-
49
43
# Add a test recipe file to the test application
50
44
touch test-applications/my-new-test-application/test-recipe.json
51
45
```
@@ -56,7 +50,7 @@ To get you started with the recipe, you can copy the following into `test-recipe
56
50
{
57
51
"$schema" : " ../../test-recipe-schema.json" ,
58
52
"testApplicationName" : " My New Test Application" ,
59
- "buildCommand" : " yarn install --no -lockfile" ,
53
+ "buildCommand" : " yarn install --pure -lockfile" ,
60
54
"tests" : [
61
55
{
62
56
"testName" : " My new test" ,
@@ -71,7 +65,9 @@ The `test-recipe.json` files follow a schema (`e2e-tests/test-recipe-schema.json
71
65
fields:
72
66
73
67
- The ` buildCommand ` command runs only once before any of the tests and is supposed to build the test application. If
74
- this command returns a non-zero exit code, it counts as a failed test and the test application's tests are not run.
68
+ this command returns a non-zero exit code, it counts as a failed test and the test application's tests are not run. In
69
+ the example above, we use the ` --pure-lockfile ` flag to install depencies without modifiying the lockfile so that
70
+ there aren't any changes in the git worktree after running the tests.
75
71
- The ` testCommand ` command is supposed to run tests on the test application. If the configured command returns a
76
72
non-zero exit code, it counts as a failed test.
77
73
- A test timeout can be configured via ` timeoutSeconds ` , it defaults to ` 60 ` .
0 commit comments