QUnit Vs. Jasmine and TDD Vs. BDD

15,428
  1. BDD and TDD are not mutually exclusive. See Liz Keogh's post

  2. Behavior testing should be understandable by business stakeholders. Unit testing is typically intended to be understood by technical team members (developers, testers etc.). For examples of how to make unit tests more readable you should look at the GOOS book (although the examples are Java not Javascript).

    Also, if you try to cover all test paths using BDD, your business people will get bored and stop caring.

  3. Have a look at Cucumber-JS (a port of Cucumber).

Share:
15,428
Mims H. Wright
Author by

Mims H. Wright

I'm a freelance software developer in Los Angeles. My work focuses primarily on RIAs and games using Flash and Flex although I've been exploring other platforms such as iPhone and XNA (for XBox).

Updated on August 10, 2022

Comments

  • Mims H. Wright
    Mims H. Wright almost 2 years

    I've been looking at two libraries for doing unit tests on the front-end.

    • QUnit - http://qunitjs.com/

    • Jasmine - http://jasmine.github.io/

      1. Jasmine is clearly more BDD focused than QUnit although I could see doing BDD with QUnit by describing the tests in a behavior-oriented way. Both of them are able to run assertions on units of code so I think they're both unit tests. Is BDD mutually exclusive from TDD or is it all in how you write it?

      2. Is unit testing necessary if you're doing behavior testing? Seems like if you cover all user stories, you don't really need to know the details of the testable units.

      3. Are there any other testing frameworks you like? Are there other tests besides unit tests that are good for devs to do on the front-end?