test(test-support): ✅ test unknown resource type creation in fake()

This originally came out of some code formatting causing a decrease in
code coverage. Rather than bypass the nuissance, I decided to find some
lines that were missed and test them. I discovered however that jest's
coverage report (at least for `test-support`) shows the wrong line
numbers. This appears to be an issue with `esbuild-jest`[0] so I suspect
other packages will need their Jest configs updated as well even though
the use case is pretty small.

[0]: aelbore/esbuild-jest#79

packages/test-support/jest.config.cjs

@@ -1,7 +1,16 @@
+/** @type {import('esbuild-jest').Options} */
+const esbuildOptions = {
+  // Setting `sourcemap` to `true` is needed[0] to correctly report line numbers
+  // in Jest's built-in coverage reporting.
+  //
+  // [0]: https://github.com/aelbore/esbuild-jest/issues/79
+  sourcemap: true,
+};
+
 /** @type {import('jest').Config} */
 const config = {
   transform: {
-    "^.+\\.tsx?$": "esbuild-jest",
+    "^.+\\.tsx?$": ["esbuild-jest", esbuildOptions],
   },
 };
 

packages/test-support/r4b/fakes.test.ts

@@ -3,6 +3,16 @@ import { DomainResource } from "fhir/r4";
 import { fake } from "./fakes";
 
 describe("fakes", () => {
+  it("throws an `Error` when attempting to generate an unrecognized resource type", () => {
+    const unrecognizedResourceTypeName = `BonfhirSpringTestExampleStructThingy`;
+
+    const generatingAnUnknownResourceType = () =>
+      // @ts-expect-error as this explicitly tests using an invalid type
+      fake(unrecognizedResourceTypeName);
+
+    expect(generatingAnUnknownResourceType).toThrowError(Error);
+  });
+
   it.each(DomainResourceTypes)("generate fakes for %s", (resourceType) => {
     const resource = fake(resourceType as ResourceType);
     expect((resource as DomainResource).text?.div).not.toBeFalsy();