JavaScript unit testing with Jasmine
- 2. Agenda • Jasmine Overview • Folder structure • Conventions • Jasmine plugins • Test code cases o RequireJs configuration o Mock considerations o Mock Ajax o Mock JayData (datajs) • Example of code failure discovery • Selenium runner
- 3. Jasmine Overview • http://pivotal.github.io/jasmine/ • Suite = describe • Spec = it • Expect and matchers • beforeEach, afterEach • Spies • Async operations • SpecRunner • Test results
- 4. Folder structure • The tests root folder is under “WWW” folder. • Spec runners HTML files are in the root of the tests folder. • Folders: o lib – hold Jasmine source files. o specs – holds all specs. • cafe • login • pb o mocks – hold all mock objects • modules – hold all mock modules that corresponds to source modules. • responses – hold mock responses objects. • objects – hold any other mock object. o helpers – hold any helper objects.
- 5. Conventions • Spec runner html files are in the root of the tests folder • Spec file name = <module>.spec.js • Responses file name = <module>.responses.js • Mock module name same as source module name • Use the require map id “src” for mock files with source dependencies. see “testmockspbmodulesdb.j”
- 6. Jasmine plugins • jasmine-html • jasmine-jquery • mock-ajax
- 7. Test code cases • RequireJs configuration • Mock considerations • Mock Ajax • Mock JayData (datajs)
- 8. Example of code failure discovery • Missing reject case for loading deferred object in plans.js
- 9. Selenium runner • Selenium can run the jasmine unit tests in build.
- 10. End