You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this commit removes nightly tests completely
because we don't need nightly tests anymore.
nighlty tests were added to avoid rate limiting
issue but as we moved to GHE we don't have rate
limit issue anymore.
Signed-off-by: Zaki Shaikh <zashaikh@redhat.com>
Copy file name to clipboardExpand all lines: test/README.md
-23Lines changed: 0 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -152,28 +152,6 @@ To clean up stale test projects (older than 7 days) left from previous runs:
152
152
153
153
If you need to update the golden files in the end-to-end test, add the `-update` flag to the [go test](https://pkg.go.dev/cmd/go#hdr-Test_packages) command to refresh those files. First, run it if you expect the test output to change (or for a new test), then run it again without the flag to ensure everything is correct.
154
154
155
-
## Running nightly tests
156
-
157
-
Some tests are set as nightly which mean not run on every PR, because exposing rate limitation often.
158
-
We run those as nightly via github action on kind.
159
-
160
-
You can use `make test-e2e-nightly` if you want to run those manually as long
161
-
as you have all the env variables set.
162
-
163
-
If you are writing a test targeting a nightly test you need to check for the env variable:
164
-
165
-
```go
166
-
if os.Getenv("NIGHTLY_E2E_TEST") != "true" {
167
-
t.Skip("Skipping test since only enabled for nightly")
168
-
}
169
-
```
170
-
171
-
and maybe add to the test-e2e-nightly Makefile target to the -run argument :
172
-
173
-
```bash
174
-
-run '(TestGithub|TestOtherPrefixOfTest)'
175
-
```
176
-
177
155
## Continuous Integration (CI) with GitHub Actions
178
156
179
157
Our E2E tests are automatically run as part of our CI pipeline using GitHub Actions. This section explains how the CI process works, the components involved, and how to troubleshoot or extend it.
@@ -363,7 +341,6 @@ To add new provider tests:
363
341
1. Create test files following the existing patterns
364
342
2. Ensure proper naming convention to match the test category filters
365
343
3. Update environment variables if needed
366
-
4. For nightly-only tests, include the check for `NIGHTLY_E2E_TEST`
0 commit comments