Ensure all GET Tests work

[jeromegv]

Agreed we will use a better test framework, waiting for answer from Ahbishek's friend. Suggestions from Taneem: Jasmine or Zombie

[abhishekbh]

Found it: http://vowsjs.org/

Please consider it and let me know what you think.

I can being installing this tomorrow if this is fine.

[jeromegv]

There is nodeunit as well https://github.com/caolan/nodeunit

Found this: http://stackoverflow.com/questions/7254025/node-js-unit-testing

And this: http://stackoverflow.com/questions/5370222/unit-testing-framework-for-node-js-that-specifically-supports-testing-async-code

To be honest, I don't think my knowledge in unit testing is good enough to know what library would work best with our typical use cases..

On Sun, Jun 3, 2012 at 8:37 PM, Abhishek Bhatnagar < reply@reply.github.com

wrote:

Found it: http://vowsjs.org/

Please consider it and let me know what you think.

I can being installing this tomorrow if this is fine.

---

Reply to this email directly or view it on GitHub:

https://github.com/thesentinelproject/threatwiki_node/issues/7#issuecomment-6090516

Jérôme Gagnon-Voyer | Technology Analyst jerome@thesentinelproject.org | Skype: jeromegagnonvoyer

[abhishekbh]

Hmm, yeah there are like 30 popular frameworks at the moment.

I'd vote to vows for two reasons that I read online:

• It has a "watcher", which can auto run tests on code change
• This auto translates into it fitting well into a continuous integration server which I was thinking we setup in a few months.
• Apparently it can return test results in JUnit style XML, which fits in with point #2. It can become part of a larger framework.

Apparently most of the other features these guys share are the same.

[abhishekbh]

Yeah, so I heard back Zombie for frontend, Vows for backend.

I'm with okay with this path. Any objections?

[jeromegv]

All good

Le 2012-06-04 à 20:02, Abhishek Bhatnagar reply@reply.github.com a écrit :

Yeah, so I heard back Zombie for frontend, Vows for backend.

I'm with okay with this path. Any objections?

---

Reply to this email directly or view it on GitHub: https://github.com/thesentinelproject/threatwiki_node/issues/7#issuecomment-6114712

[abhishekbh]

Okay, added vows.

For this iteration, we should probably only write tests in vows right? With this thinking I added only vows for now.

Did you want to split up the work in vows? We essentially have to write a test for every function the API provides. Did you want to take two files and I take the other two?

[jeromegv]

Sure

Le 2012-06-06 à 00:47, Abhishek Bhatnagar reply@reply.github.com a écrit :

Okay, added vows.

For this iteration, we should probably only write tests in vows right? With this thinking I added only vows for now.

Did you want to split up the work in vows? We essentially have to write a test for every function the API provides. Did you want to take two files and I take the other two?

---

Reply to this email directly or view it on GitHub: https://github.com/thesentinelproject/threatwiki_node/issues/7#issuecomment-6142953

[jeromegv]

Did you get started on something? Where should we put those test files? Not sure where to start, especially if you started on your side

[jeromegv]

starting some basic implementation, with Tobi to do the API calls, used this to help out to start: https://gist.github.com/1117455