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
Copy file name to clipboardExpand all lines: docs/testing.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ This project uses a combination of unit tests and end-to-end (e2e) tests to ensu
7
7
- Unit tests are located alongside implementation, with filenames ending in `_test.go`.
8
8
- Currently the preference is to use internal tests i.e. test files do not have `_test` package suffix.
9
9
- Tests use [testify](https://github.com/stretchr/testify) for assertions and require statements. Use `require` when continuing the test is not meaningful, for example it is almost never correct to continue after an error expectation.
10
-
- Mocking is performed using [go-github-mock](https://github.com/migueleliasweb/go-github-mock) or `githubv4mock` for simulating GitHub rest and GQL API responses.
10
+
- Mocking is performed using the in-repo HTTP handler-map helpers (e.g. `MockHTTPClientWithHandlers`, `mockResponse`) for GitHub REST, and `githubv4mock` for simulating GitHub GraphQL API responses.
11
11
- Each tool's schema is snapshotted and checked for changes using the `toolsnaps` utility (see below).
12
12
- Tests are designed to be explicit and verbose to aid maintainability and clarity.
0 commit comments