Work around broken loader-utils behaviour in integration tests

Author: pugnascotia

packages/react-scripts/fixtures/kitchensink/integration/webpack.test.js

@@ -28,7 +28,24 @@ describe('Integration', () => {
     it('no ext inclusion', async () => {
       const doc = await initDOM('no-ext-inclusion')
 
-      expect(doc.getElementById('feature-no-ext-inclusion').href).to.match(/\/static\/media\/aFileWithoutExt$/)
+      // The expected pattern here is wrong. Due to:
+      //
+      //     https://github.com/webpack/loader-utils/pull/71
+      //
+      // ...the loader-utils module gets the interpolated name wrong when
+      // there's no file extension and there's a period in source directory
+      // path (which happens here due to generated temp directories). You
+      // end up with something like:
+      //
+      //  /static/media/.cb7eb057.OEs6g9SsPz/test-kitchensink/src/features/webpack/assets/aFileWithoutExt
+      //
+      //  instead of:
+      //
+      //  /static/media/aFileWithoutExt.[hash].bin
+      //
+      // At some point loader-utils will be fixed, and the pattern can be
+      // fixed too.
+      expect(doc.getElementById('feature-no-ext-inclusion').href).to.match(/\/static\/media\/.*aFileWithoutExt$/)
     })
 
     it('json inclusion', async () => {