testing

Testing tools, testing philosophy & methodology...
anmonteiro 2016-07-14T21:22:49.000049Z

@bensu: wondering if the doo Node.js runner can find modules in node_modules

anmonteiro 2016-07-14T21:23:03.000050Z

I’m not having any luck with Boot currently

anmonteiro 2016-07-14T21:23:40.000051Z

it worked in Lein but can’t get it to work with Boot even after adding node_modules to the fileset

2016-07-14T21:36:46.000052Z

@anmonteiro: I’m not sure. node_modules works with relative paths. lein-doo respects that since you usually call it from a root dir that has both project.clj and node_modules. Then it works.

anmonteiro 2016-07-14T21:37:32.000053Z

@bensu: right, I got that working. But I’m trying that in a boot project and the concept is different because it relies on filesets

anmonteiro 2016-07-14T21:38:10.000054Z

and filesets are not directly mapped to the project tree

2016-07-14T21:38:41.000055Z

then I can’t help you much. there are a couple of tickets (CLJS-JIRA) around calling the compiler with different relative paths (by @martinklepsch and me) which might help you see what the problem is

2016-07-14T21:39:29.000056Z

I would talk to @crisptrutski since he has done all the related work.

anmonteiro 2016-07-14T21:39:53.000058Z

@bensu: yeah, I’ve also seen those tickets a while ago, but I’m not having that problem. IIRC they are about :target :nodejs and the path for the preamble or something

anmonteiro 2016-07-14T21:40:24.000059Z

thanks for your help anyway, I’ll keep diggging

2016-07-14T21:41:38.000060Z

final idea, read boot-cljs-test source to find how he adds runner.js to the file-set. If he preserves the relative paths, then you can use the same thing to add node_modules and that should work

anmonteiro 2016-07-14T21:42:29.000061Z

@bensu: cool, I’ll try that first

anmonteiro 2016-07-14T21:44:37.000063Z

I should note that I’m using boot-cljs-test

anmonteiro 2016-07-14T21:45:02.000064Z

so I definitely want to put node_modules where runner.js can read them