You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 7, 2020. It is now read-only.
I have enjoyed using your coverage plugin so far, but I've found an area where it could be improved. As I understand it, the plugin looks for .html files and instruments the tests loaded in the html file. I use Require.js throughout my application and unit tests, so I only have one SpecRunner.html, and it uses Require.js to load each of my numerous test files. The problem is that the plugin appears to count each .html file as one test, so when I run saga with TOTAL or PERTEST I get the same result. This isn't a make-it or break-it issue, but it would be nice for saga to detect AMD and recognize that each spec.js file loaded by my one .html file is a different test, and display results accordingly. Food for thought.
The text was updated successfully, but these errors were encountered:
I have enjoyed using your coverage plugin so far, but I've found an area where it could be improved. As I understand it, the plugin looks for .html files and instruments the tests loaded in the html file. I use Require.js throughout my application and unit tests, so I only have one SpecRunner.html, and it uses Require.js to load each of my numerous test files. The problem is that the plugin appears to count each .html file as one test, so when I run saga with TOTAL or PERTEST I get the same result. This isn't a make-it or break-it issue, but it would be nice for saga to detect AMD and recognize that each spec.js file loaded by my one .html file is a different test, and display results accordingly. Food for thought.
The text was updated successfully, but these errors were encountered: