Book Image

Learning jQuery 3 - Fifth Edition

By : Jonathan Chaffer, Karl Swedberg
Book Image

Learning jQuery 3 - Fifth Edition

By: Jonathan Chaffer, Karl Swedberg

Overview of this book

If you are a web developer and want to create web applications that look good, are efficient, have rich user interfaces, and integrate seamlessly with any backend using AJAX, then this book is the ideal match for you. We’ll show you how you can integrate jQuery 3.0 into your web pages, avoid complex JavaScript code, create brilliant animation effects for your web applications, and create a flawless app. We start by configuring and customising the jQuery environment, and getting hands-on with DOM manipulation. Next, we’ll explore event handling advanced animations, creating optimised user interfaces, and building useful third-party plugins. Also, we'll learn how to integrate jQuery with your favourite back-end framework. Moving on, we’ll learn how the ECMAScript 6 features affect your web development process with jQuery. we’ll discover how to use the newly introduced JavaScript promises and the new animation API in jQuery 3.0 in great detail, along with sample code and examples. By the end of the book, you will be able to successfully create a fully featured and efficient single page web application and leverage all the new features of jQuery 3.0 effectively.
Table of Contents (23 chapters)
Title Page
About the Authors
About the Reviewer
Customer Feedback

Organizing tests

QUnit provides two levels of test grouping named after their respective function calls: QUnit.module() and QUnit.test(). The module is like a general category under which the tests will be run; the test is actually a set of tests; the function takes a callback in which all of that test's specific unit tests are run. We'll group our tests by the chapter topic and place the code in our test/test.js file:


QUnit.test('Child Selector', (assert) => {

QUnit.test('Attribute Selectors', (assert) => {


Listing A.1

It's not necessary to set up the file with this test structure, but it's good to have some overall structure in mind. In addition to the QUnit.module() and QUnit.test() grouping, we have to tell the test how many assertions to expect. Since we're just getting organized, we need to tell the test that there aren't any assertions yet (assert.expect(0)) in order for the tests...