Closed flore77 closed 8 years ago
Looks good, except for failing tests.
Seems like this will need an update as well: https://github.com/js-reporters/js-reporters/pull/90/files#diff-27a1c86133de4310373decfdad200a91R19
Seems like this will need an update as well: https://github.com/js-reporters/js-reporters/pull/90/files#diff-27a1c86133de4310373decfdad200a91R19
This will be solved in #90, it will be rebased on the master after this pr will be merged.
Good to land? :smiley:
I set jasmine to the last working version until a version with the fix will be published.
This solves the adding of the jasmine adapter in a node env.
We cannot pass the
jasmine.env
to the reporter, we must pass in thejasmine
object, which is a NodeJS helper overjasmine-core
. We must use thejasmine.addReporter
and not directlyjasmine.env.addReporter
, because then it will enter on this branch and jasmine will exit and kill the process. Using thejasmine.addReporter
has some internal logic that holds from exiting.Now the adapter has some extra logic to differentiate btw a node env and a browser env. Unfortunately we cannot test the browser part, because currently the tests are running only in a node env.