search

fluid-lab / gamepad-navigator

GSoC 2020 project
Other
8 stars 10 forks source link

Add code coverage reporting. #2

Open the-t-in-rtf opened 4 years ago

the-t-in-rtf commented 4 years ago

Once we have code and tests, we should follow best practice and add code coverage reporting using a tool like nyc.js. This should be called as part of the npm test script definition and as part of our CI builds.

the-t-in-rtf commented 4 years ago

gpii-testem handles a lot of this for you, but the approach used there was based on an example from the testem docs, you might also choose to implement your own depending.

duhrer commented 10 months ago

I made a pass at this, but paused and parked the work in a branch because:

  1. There were unique and tricky issues with Testem not closing at the end of a test run.
  2. fluid-testem did not seem to be picking up the directory configuration and writing the reports somewhere that could be monitored.
  3. It was obvious in reviewing the partial report that there was an awful lot of code (especially in the background and main input mapper) that can't be tested unless we bring in something like webdriver.