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
My application is a Node REST-like API, with the application running in the same process as the test runner. I would imagine that instrumenting code coverage for the more typical Cucumber use case -- feature tests with Selenium browser automation -- would be difficult because the SUT runs in a different process from the runner. However I suppose JSDom could possibly work instead of Selenium for getting code coverage from tests.
The text was updated successfully, but these errors were encountered:
FYI. I'm using coffee-coverage with CucumberJS as the test runner. This worked fine for me with a small hack to get around a CucumberJS issue.
My application is a Node REST-like API, with the application running in the same process as the test runner. I would imagine that instrumenting code coverage for the more typical Cucumber use case -- feature tests with Selenium browser automation -- would be difficult because the SUT runs in a different process from the runner. However I suppose JSDom could possibly work instead of Selenium for getting code coverage from tests.
The text was updated successfully, but these errors were encountered: