Lines Matching full:suite
11 recursive search to find the test suite for each item, but then we only do a
29 delegated to each test suite. This could take a couple forms:
31 * We could resolve to test suites, then fully load each test suite, then have
32 a fixed process to map input specifiers to tests in the test suite
33 (presumably based on path-in-suite derivations). This has the benefit of
35 loading the entire test suite.
38 suite. This would allow formats that anticipate large test suites to manage
44 2. Consider move to identifying all tests by path-to-test-suite and then path to
45 subtest, and don't use test suite names.
47 Currently the test suite name is presented as part of test names, but it has
50 represented each test suite by the path to its suite, then it would allow more
67 certainly have to load the suite before we can query it for what options it
77 test suite options. For example, we could require something like::
87 infrastructure and format or suite specific options.
163 * Create an explicit test suite object (instead of using the top-level
