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: end_to_end_tests/generated_code_live_tests/README.md
+1-2
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ These are end-to-end tests which run the code generator command, but unlike the
5
5
Each test class follows this pattern:
6
6
7
7
- Use the decorator `@with_generated_client_fixture`, providing an inline API spec (JSON or YAML) that contains whatever schemas/paths/etc. are relevant to this test class.
8
-
- The spec can omit the `openapi:`and `info:` blocks, unless those are relevant to the test.
8
+
- The spec can omit the `openapi:`, `info:`, and `paths:`, blocks, unless those are relevant to the test.
9
9
- The decorator creates a temporary file for the inline spec and a temporary directory for the generated code, and runs the client generator.
10
10
- It creates a `GeneratedClientContext` object (defined in `end_to_end_test_helpers.py`) to keep track of things like the location of the generated code and the output of the generator command.
11
11
- This object is injected into the test class as a fixture called `generated_client`, although most tests will not need to reference the fixture directly.
0 commit comments