Hi All
I am porting a pretty large app from AMD to using Browserify v3.
I have been able to compile the project successfully, but now turn my
attention to testing. Ideally, I'd like to take advantage of the bundling
ability so I could have simply:
/build/bundle.js
/build/bundle-specs.js
However the paths from the 'spec' files presume the path of the file where
their respective systems-under-test are found.
This _seems_ like I would be therefore need to --require
every-file-contributing-to-my-bundle so that they are exported for use in
other bundles on the page.
This is okay since I am using the JS API, not the command line tool, but I
wonder if this is the best way to do this.
Does it matter too much if I just 'require' (export from the bundle) every
path in my app code? I assume the bundle.js would be larger but that isn't
too grave a concern.
Or would it be better to simply package the entire things, specs and app
code, into a single bundle and test that?
If it matters, we are using testem (converting from karma) for our runner
and here is the directory structure for our app:
/feature1
-- feature1.js
-- |
-- /tests
----feature1-spec.js
/feature2
-- feature2.js
-- |
-- /tests
---- feature2-spec.js
Any advice or experience on how others work with browserify both in browser
and CI/testing environments where this kind of separation is desirable
would be helpful.
Thanks!
mike
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
