Lines Matching refs:test

3 Learn about test finders and how to create a new test finder class.
6 1. [Test Finder Details](#test-finder-details)
7 2. [Creating a Test Finder](#creating-a-test-finder)
9 ## <a name="test-finder-details">Test Finder Details</a>
11 A test finder class holds find methods. A find method is given a string (the
13 A ```TestInfo``` object holds the test name, test dependencies, test runner, and
14 a data field to hold misc bits like filters and extra args for the test.  The
15 test finder class can hold multiple find methods. The find methods are grouped
16 together in a class so they can share metadata for optimal test finding.
18 the test configs for the ```TFIntegrationFinder```.
20 **When should I create a new test finder class?**
22 If the metadata used to find a test is unlike existing test finder classes,
24 file name patterns, a special file in a dir to indicate it's a test, etc. The
25 default test finder classes use the module-info.json and specific dir paths
28 ## <a name="creating-a-test-finder">Creating a Test Finder</a>
30 First thing to choose is where to put the test finder. This will primarily
31 depend on if the test finder will be public or private. If public,
37 > add the path of where the test finder lives into ```$PYTHONPATH```. Same
43 the find methods from your test finder class. Take a look at
46 Define the find methods in your test finder class. These find methods must
54 Final bit is to add your test finder class to ```test_finder_handler```.