Functional Testing Tools

Given valid and invalid inputs, traditional equivalence testing strategy identifies test cases as:

• VALID inputs: one value from each valid class

  • weak equivalence class testing
  • each input in these test cases will be valid

• INVALID inputs: test case w\/one invalid value and remaining values are valid

  • a single failure should cause the test case to fail

Functional Test Example

‘Mocha’ Module as example for Testing Framework Tool

Framework: JavaScript framework running on NodeJs (server-side platform), the browser(client side)

Asynchronous & Synchronous Code: Mocha tests run serially

Assertion Modules:

• should.js BDD style shown throughout these docs

• expect.js expect() style assertions

• Chai expect(), assert() and should-style assertions

• better-assert C-style self-documenting assert()

• unexpected “the extensible BDD assertion toolkit”

Dynamic Tests

Interfaces and reporters

API testing Example

SDK Test Case

Unit Testing: stub functions, independent test

Client side test: Uses the browser to run tests

White Box Test: Uses code test coverage reports

API Testing

Functional Testing

Unit Testing: dependent

Server-side Test: REST protocol: http requests

Black Box Test