Skip to content

Commit

Permalink
chore: Update testing.md (#1595)
Browse files Browse the repository at this point in the history
Update testing.md

Co-authored-by: Edgar R. M <edgar@meltano.com>
  • Loading branch information
pnadolny13 and edgarrmondragon authored Apr 10, 2023
1 parent 1867c2b commit 10a17a4
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ The Meltano SDK test framework consists of 4 main components:
1. A runner class (`TapTestRunner` and `TargetTestRunner`), responsible for executing Taps/Targets and capturing their output.
1. A suite dataclass, containing a list of tests.
1. A test template classes (`TapTestTemplate`, `StreamTestTemplate`, `AttributeTestTemplate` and `TargetTestTemplate`), with methods to `.setup()`, `.test()`, `.validate()` and `.teardown()` (called in that order using `.run()`).
1. `get_tap_test_class` and `get_target_test_class` factory methods. These wrap a `get_test_class` factory method, which takes a runner and a list of suits and return a `pytest` test class.
1. `get_tap_test_class` and `get_target_test_class` factory methods. These wrap a `get_test_class` factory method, which takes a runner and a list of suites and return a `pytest` test class.

## Example Usage

Expand Down Expand Up @@ -130,7 +130,7 @@ Once you have created some tests, add them to a suite:

```python
my_custom_tap_tests = TestSuite(
type="tap", tests=[TapCLIPrintsTest]
kind="tap", tests=[TapCLIPrintsTest]
)
```

Expand Down

0 comments on commit 10a17a4

Please sign in to comment.