As mentioned in my previous post, I’ve been wanting to use Buster.JS as test framework for my implementation of the master thesis. After installing node, I was ready to install buster. Or so I thought. With npm (package manager for node) I tried “npm install -g buster”, which gave me an error (full output). It seemed that the module glob wasn’t available in the version buster needed.
After looking around a bit, I read about the install function in npm. So I can install specific versions easily, neat! A “npm install firstname.lastname@example.org″ later, another error occurs! It seemed that my version of node, v.0.7.0-pre, wasn’t supported by version 2.1.0 of glob. So back to node-building it was. Luckily, v6.0 is its own branch, enabling me to easily switch with “git checkout v6.0″.
Ok, “./configure” next! Hmmm, seems that I didn’t have OpenSSL installed. Me being a noob, I installed the wrong package, but luckily I found a piece that helped me on the right path. Right, “sudo apt-get install libssl-dev” it is.
Now installing node went peachy, and with that also glob. And then, finally, I could install buster! npm install -g buster was the magic words, and so I was ready to start testing! Or so I thought…
To check if the program ran as intended, I cloned buster-args as it was used as an example on Node testing on buster.js.org. I ran into “Error: cannot find module ‘buster’”. As I was new to both node, npm and buster, I really had no idea where I’d gone wrong, so I posted an issue at github/busterjs.
I also joined #buster@freenode. First I merely watched for activity, and as it started I posted my questions to get a quicker response. The authors were very helpful, and soon made it clear that I hadn’t linked the project. Running npm link in the project I wanted to test, and voilà! A beautiful and informative output stood before me. Nice!
Now I’m going to implement into my own framework, so wish me luck ^\_^