Removed curly braces around file extension in collectCoverageForm in …

[jcfilben]

…package.json to generate code coverage report with jest

Signed-off-by: Jessica Filben [email protected]

What does this PR do?

Normally jest testing is setup to display testing coverage when the command yarn test --coverage is run. However, when the command was run the coverage was not being shown. The cause of this problem is in the jest configuration settings in package.json under collectCoverageFrom. The curly braces around the file extensions need to be removed for the testing coverage to work properly.

Where should the reviewer start?

Look at the following issue explaining the curly braces problem in jest.
Relevant documentation of issue: jestjs/jest#6654
Then look at the package.json file and see the changes that were made. Test out the yarn test --coverage command.

What testing has been done on this PR?

All tests passed and I manually tested the yarn test --coverage command by opening the index.html file found in the coverage/lcov-report folder.

How should this be manually tested?

Run yarn test --coverage and open the index.html file found in the coverage/lcov-report folder to view the test coverage report.

Any background context you want to provide?

N/A

What are the relevant issues?

N/A

Screenshots (if appropriate)

How the test coverage report looks before the curly braces in collectCoverageFrom were removed:

How the test coverage report looks after:

Do the grommet docs need to be updated?

No

Should this PR be mentioned in the release notes?

No

Is this change backwards compatible or is it a breaking change?

It is backwards compatible

[ShimiSun]

I don't think the Chromatic failures are related to this change, I've rerun the build to see if anything changes.

[ShimiSun]

#4117

[ShimiSun]

Great work, thank you for your contribution!