exports points to module.exports but not the other way around

[goatslacker]

Related to GH-22

I noticed this bug while I was writing the failing test

Basically, this line has to be context.module.exports and cannot be context.exports

This is because context.exports = context.module.exports but when context.module.exports is assigned, it doesn't reflect in context.exports

Solution: wrap the code using Module.wrap and pass in module.exports as exports and module as module

edit:

err...just realized you can't wrap the code since that's just the way coveraje works. Hmmmm

[WolfgangKluge]

Can't reproduce.
I added a test here 107d56b

edit: now I got it... change inside test runner...
edit 2: no - still can't reproduce - I had a typo in my extended test case first ;)

[goatslacker]

I'll add a failing test

[goatslacker]

So I know coveraje works without wrapping the node code (instead exporting all vars into the context) but I think that approach is broken. Node should function like node, where the code is wrapped and everything returned is via module.exports or exports

This will add some inconsistency so perhaps it's best to split up into a different function -- like cover.coverNode ??

[WolfgangKluge]

OK, confirmend now. Sorry, I just didn't get it ;)

Hope we find another solution...