Refactor karma test setup to give more informative reports.

[Zerim]

Checklist

Mark an X inside of

• [X] Did I cut my work branch off of master (don't cut new branches from existing feature brances)?
• [X] Did I follow the correct naming convention for my branch?
• [X] Is my branch focused on a single main change?
• [X] Do all of my changes directly relate to this change?
• [X] Did I rebase the upstream master branch after I finished all my work?
• [X] Did I write a clear pull request message detailing what changes I made?
• [X] Are all tests passing
• [X] Did I write new tests for new functionality?

What are the important parts of the code?

karma.conf.js and package.json.

How should this be tested by the reviewer?

Run the tests and verify that it gives a report for each test passed/failed.

Is any other information necessary to understand the files?

No.

Attach relevant screenshots (if any)