FLUID-6139: Add code coverage and run browser tests as part of "npm test"...

Metadata

Source
FLUID-6139
Type
Improvement
Priority
Minor
Status
Closed
Resolution
Fixed
Assignee
Antranig Basman
Reporter
Tony Atkins [RtF]
Created
2017-03-01T08:03:13.612-0500
Updated
2024-07-22T09:15:50.172-0400
Versions
N/A
Fixed Versions
N/A
Component
  1. Testing Infrastructure

Description

Currently, infusion only runs the node tests when npm test is run. This PR updates the test configuration to:

  1. Run the browser tests as well using gpii-testem
  2. Collect code coverage for both node and browser tests.

Comments

  • Tony Atkins [RtF] commented 2017-03-01T08:50:31.425-0500

    @@Antranig Basman, predictably, I am having problems using gpii-testem as a dev dependency. the "fluid.require" within that package fails with the old "dedupe" warning. I am hoping there is some way around this other than moving gpii-testem into the new monorepo concept.

  • Tony Atkins [RtF] commented 2017-03-10T10:09:30.610-0500

    @@Antranig Basman, the PR with your dedupe fix and my own work on providing test coverage reports using gpii-testem is ready for review here:

    https://github.com/fluid-project/infusion/pull/822

  • Tony Atkins [RtF] commented 2017-07-03T06:18:39.486-0400

    @@Antranig Basman (and @@Cindy Li) I was hoping @@Cindy Li could pick this up, as she handled the comparable universal pull very well. Thoughts?