change macro format

This is both a better way to express multiple tests, and a signal to users that
something has changed.

Author: sunshowers

Cargo.lock

@@ -35,6 +35,9 @@ include_dir = { version = "0.7.4", optional = true }
 libtest-mimic = "0.8.1"
 walkdir = "2.5.0"
 
+[dev-dependencies]
+trybuild = "1.0.101"
+
 [target.'cfg(unix)'.dev-dependencies]
 camino-tempfile = "1.1.1"
 fs_extra = "1.3.0"
@@ -44,7 +47,7 @@ name = "example"
 harness = false
 
 [[test]]
-name = "run_example"
+name = "integration"
 harness = true
 
 [features]

Cargo.toml

@@ -36,10 +36,15 @@ name = "<test target name>"
 harness = false
 ````
 
-2. Call the `datatest_stable::harness!(testfn, root, pattern)` macro with the following
-   parameters:
+2. Call the `datatest_stable::harness!` macro as:
 
-* `testfn` - The test function to be executed on each matching input. This function can be one
+````rust,ignore
+datatest_stable::harness! {
+    { test = my_test, root = "path/to/fixtures", pattern = r"^.*/*" },
+}
+````
+
+* `test` - The test function to be executed on each matching input. This function can be one
   of:
 
   * `fn(&Path) -> datatest_stable::Result<()>`
@@ -67,7 +72,13 @@ harness = false
   `&str`, or a function call that returns a `String`.
 
 The three parameters can be repeated if you have multiple sets of data-driven tests to be run:
-`datatest_stable::harness!(testfn1, root1, pattern1, testfn2, root2, pattern2)`.
+
+````rust,ignore
+datatest_stable::harness! {
+    { test = testfn1, root = root1, pattern = pattern1 },
+    { test = testfn2, root = root2, pattern = pattern2 },
+}
+````
 
 ### Relative paths
 
@@ -101,10 +112,10 @@ fn my_test_utf8(path: &Utf8Path, contents: String) -> datatest_stable::Result<()
     Ok(())
 }
 
-datatest_stable::harness!(
-    my_test, "path/to/fixtures", r"^.*/*",
-    my_test_utf8, "path/to/fixtures", r"^.*/*",
-);
+datatest_stable::harness! {
+    { test = my_test, root = "path/to/fixtures", pattern = r"^.*/*" },
+    { test = my_test_utf8, root = "path/to/fixtures", pattern = r"^.*/*" },
+}
 ````
 
 If `path/to/fixtures` contains a file `foo/bar.txt`, then:
@@ -134,9 +145,9 @@ fn my_test(path: &Path, contents: Vec<u8>) -> datatest_stable::Result<()> {
     Ok(())
 }
 
-datatest_stable::harness!(
-    my_test, include_dir!("tests/files"), r"^.*/*",
-);
+datatest_stable::harness! {
+    { test = my_test, root = include_dir!("tests/files"), pattern = r"^.*/*" },
+}
 ````
 
 You can also use directories published as `static` items in upstream crates:
@@ -153,9 +164,9 @@ fn my_test(path: &Utf8Path, contents: String) -> datatest_stable::Result<()> {
     Ok(())
 }
 
-datatest_stable::harness!(
-    my_test, &FIXTURES, r"^.*/*",
-);
+datatest_stable::harness! {
+    { test = my_test, root = &FIXTURES, pattern = r"^.*/*" },
+}
 ````
 
 In this case, the passed-in `Path` and `Utf8Path` are **relative** to the
@@ -186,9 +197,9 @@ fn my_test(path: &Utf8Path, contents: String) -> datatest_stable::Result<()> {
     Ok(())
 }
 
-datatest_stable::harness!(
-    my_test, &FIXTURES, r"^.*/*",
-);
+datatest_stable::harness! {
+    { test = my_test, root = &FIXTURES, pattern = r"^.*/*" },
+}
 ````
 
 In this case, note that `path` will be relative to the **crate directory**