@@ -1575,24 +1575,28 @@ The last method generates a nested hierarchy of dynamic tests utilizing
15751575include::{testDir}/example/DynamicTestsDemo.java[tags=user_guide]
15761576----
15771577
1578- [[writing-tests-uris- test-source-examples ]]
1579- ===== URI Test Source Examples
1578+ [[writing-tests-dynamic-tests-uri- test-source]]
1579+ ==== URI Test Sources for Dynamic Tests
15801580
1581- The JUnit Platform provides `TestSource`, a representation of the source of a test
1582- or container used to navigate to its location by IDEs and build tools.
1581+ The JUnit Platform provides `TestSource`, a representation of the source of a test or
1582+ container used to navigate to its location by IDEs and build tools.
15831583
1584- Test sources can be constructed using URIs :
1584+ Test sources for dynamic tests can be constructed from URIs.
15851585
1586- - `ClasspathResourceSource`
1587- Use the `classpath` scheme, for example: `classpath:/test/foo.xml?line=20,column=2`
1586+ `ClasspathResourceSource` ::
1587+ Use the `classpath` scheme -- for example, `classpath:/test/foo.xml?line=20,column=2`.
15881588
1589- - `DirectorySource` and `FileSource`
1590- Use file system paths .
1589+ `DirectorySource` ::
1590+ Use file system path .
15911591
1592- - `MethodSource`
1593- Use the `method` scheme and the fully-qualified-method-name ex
1594- `method:org.junit.Foo#bar(java.lang.String, java.lang.String[])`. Please refer to the Javadoc for
1595- `DiscoverySelectors.selectMethod(String)` for the supported formats for a FQMN.
1592+ `FileSource` ::
1593+ Use file system path.
1594+
1595+ `MethodSource` ::
1596+ Use the `method` scheme and the fully qualified method name (FQMN) -- for example,
1597+ `method:org.junit.Foo#bar(java.lang.String, java.lang.String[])`. Please refer to the
1598+ Javadoc for `DiscoverySelectors.selectMethod(String)` for the supported formats for a
1599+ FQMN.
15961600
15971601
15981602[[writing-tests-declarative-timeouts]]
0 commit comments