Unit Testing in JavaScript with MVC and QUnit
2 likes4,347 views
Lars Thorup presents on unit testing JavaScript applications with the MVC pattern and QUnit testing framework. He discusses testing views, controllers, models, and services. The document recommends setting up tests for each component in isolation by injecting stubs for their dependencies. Asynchronous testing is also covered, including techniques like stopping/starting to synchronize async calls in tests. The MVC pattern with dependency injection is advocated to make the code more modular and testable.
1 of 26
Downloaded 58 times
Ad
Recommended
Maven Introduction
Maven IntroductionSandeep Chawla Maven is a build tool that can manage a project's build process, dependencies, documentation and reporting. It uses a Project Object Model (POM) file to store build configuration and metadata. Maven has advantages over Ant like built-in functionality for common tasks, cross-project reuse, and support for conditional logic. It works by defining the project with a POM file then running goals bound to default phases like compile, test, package to build the project.
Android - Thread, Handler and AsyncTask
Android - Thread, Handler and AsyncTaskHoang Ngo Thread allows running code on a background thread but cannot directly update the UI. Handler allows scheduling messages and runnables to execute on a thread's message queue. AsyncTask simplifies background threading by running background work on a separate thread and publishing results on the UI thread.
Building native mobile apps using web technologies
Building native mobile apps using web technologiesHjörtur Hilmarsson This document discusses building mobile apps using web technologies like HTML, CSS, and JavaScript. It covers responsive layouts using percentages and media queries, maintainable code practices like JavaScript best practices and libraries like jQuery, offline sync using local storage and network detection, and creating multi-platform apps using PhoneGap. It also provides an example of a demo app built with Backbone.js and discusses background sync challenges.
Javascript Unit Testting (PHPBenelux 2011-05-04)
Javascript Unit Testting (PHPBenelux 2011-05-04)Tom Van Herreweghe The document provides an introduction to JavaScript unit testing using QUnit and JSTestDriver, covering setup, structure, assertions, and async testing. It details the functionalities of both QUnit and JSTestDriver, including examples, and highlights the importance of code coverage. The document also contains links for further resources and downloads related to the testing tools.
Controller Testing: You're Doing It Wrong
Controller Testing: You're Doing It Wrongjohnnygroundwork The document discusses best practices for testing Rails controllers. It recommends writing declarative tests that focus on authentication, authorization, resource presence, and responses. Shared examples should be used to DRY up tests for these "small details". Tests for "big actions" like fetching a resource can be simple. Business logic belongs in models, not controllers. ActiveModel makes it easy to extract logic out of controllers and into reusable classes. Overall, the goal is to keep controllers simple and focused on their main responsibilities by writing declarative, well-factored tests.
Focus on the outside, testing in ASP.NET MVC
Focus on the outside, testing in ASP.NET MVCRob Ashton The document discusses the challenges and pitfalls of Test-Driven Development (TDD) in ASP.NET MVC applications, sharing insights and experiences from clients who struggled with TDD implementation. It emphasizes the importance of testing architecture, the need for speed and feedback in tests, and suggests avoiding unnecessary complexity and coupling in test designs. The author advocates for a more practical approach to testing, focusing on real-world application rather than dogmatic adherence to TDD principles.
F# Eye for the C# Guy - DDD North 2013
F# Eye for the C# Guy - DDD North 2013Phillip Trelford This document discusses F# and how it compares to C#. It provides examples of how common programming tasks like defining classes, dependency injection, unit testing, mocking, and debugging are simpler in F#. F# is statically typed, functional-first, object-oriented, open source, and runs on .NET. Examples show how F# code for these tasks is shorter, easier to read, easier to refactor, and contains fewer bugs than equivalent C# code. The document promotes resources for learning more about F# and provides contact information.
JavaScript Unit Testing
JavaScript Unit TestingChristian Johansen This document discusses and compares several JavaScript unit testing tools and techniques:
1. JsUnitTest is a simple standalone tool that uses fixtures loaded in the browser but does not scale well and requires browser interaction.
2. BlueRidge is integrated with Rails and easy to set up but runs tests in non-browser environments.
3. JsTestDriver runs tests across multiple actual browsers simultaneously from the command line and scales well but currently lacks support for asynchronous tests.
ASP.NET MVC Fundamental
ASP.NET MVC Fundamentalldcphuc This document provides an overview and introduction to ASP.NET MVC 3 training. It discusses the evolution of ASP.NET, key concepts of MVC like models, views, and controllers, how MVC works, and differences between MVC and web forms. The training will build a simple ASP.NET MVC application and cover controllers, models, views, routing, and action results.
Advanced QUnit - Front-End JavaScript Unit Testing
Advanced QUnit - Front-End JavaScript Unit TestingLars Thorup The document provides an advanced overview of using QUnit for front-end JavaScript unit testing, focusing on techniques such as mocking, spying, and stubbing methods to enhance test reliability and speed. It discusses how to conduct isolation testing, avoid waiting for asynchronous processes, and efficiently handle global functions and AJAX requests within tests. Additionally, it touches upon memory leak detection and the importance of cleanup after tests to ensure accurate and performant unit tests.
Qunit Java script Un
Qunit Java script Unakanksha arora The document discusses unit testing and test-driven development. It introduces the QUnit JavaScript testing framework, describing how to write tests and assertions using its API. Key aspects covered include setting up QUnit, the test and assert functions, asynchronous testing, grouping tests into modules, and integrating automated testing with Node and Grunt.
JavaScript Test-Driven Development (TDD) with QUnit
JavaScript Test-Driven Development (TDD) with QUnitTasanakorn Phaipool This document summarizes a presentation on test-driven development with QUnit for JavaScript. It includes an agenda, explanations of TDD and the QUnit testing framework, and an example of writing tests and code for a telephone number validation function using QUnit. The document demonstrates how to set up a basic test suite with QUnit, write tests, write code to pass the tests, and refactor the code while ensuring tests continue to pass.
DDD, CQRS and testing with ASP.Net MVC
DDD, CQRS and testing with ASP.Net MVCAndy Butland This document provides an overview of a presentation on Domain Driven Design (DDD), Command Query Responsibility Segregation (CQRS), and testing with ASP.Net MVC. It introduces the presenter and gives an outline of the topics to be covered, including implementing DDD with ASP.Net MVC and Entity Framework, using a mediator pattern for CQRS, and unit testing models, queries, and commands. References are given to other authors and resources that influenced the approaches and implementations discussed in the presentation.
Understanding JavaScript Testing
Understanding JavaScript Testingjeresig This document discusses JavaScript testing and provides examples of writing tests and using testing frameworks like QUnit and JSUnit. It covers:
- Why test JavaScript code due to cross-browser issues and bugs
- Components of a test suite including tests, assertions, and a test runner
- Examples of writing basic tests with assertions and handling asynchronous tests
- Popular JavaScript testing frameworks like QUnit, JSUnit, YUITest
Laws of test automation framework
Laws of test automation frameworkvodqancr The document discusses three "laws of test automation framework":
1) Test frameworks will continue growing unless changes are made, leading to complex step definitions and refactoring issues.
2) The more complex ("messy") a test framework becomes, the more effort is required to maintain it.
3) Changes to test frameworks can cause pushback from business and technical issues like merge conflicts and build failures.
The document promotes a Model-View-Controller approach to structure Cucumber tests to improve code quality and maintainability. Declarative styles are preferable to imperative to make tests more robust to business changes. Regular monitoring, desk checks, and appropriate timing of changes can help address challenges.
CQRS на практике. В поиске точки масштабирования и новых метафор
CQRS на практике. В поиске точки масштабирования и новых метафорAlexander Byndyu Документ рассматривает практическое применение паттерна CQRS (Command Query Responsibility Segregation) и его эволюцию в контексте разработки приложений. Особое внимание уделяется разделению команд и запросов, а также подходам к реализации и event sourcing. В дополнение к теоретическим аспектам, автор приводит примеры реализации, ограничения и рекомендации по оптимизации архитектуры приложений.
Unit and integration Testing
Unit and integration TestingDavid Berliner This document discusses unit and integration testing. It begins by explaining the benefits of testing, such as reducing bugs and allowing safe refactoring. It then describes different types of tests like unit, integration, and database tests. The document focuses on unit testing, explaining how to write and organize unit tests using PHPUnit. It provides examples of test assertions and annotations. It also covers mocking and stubbing dependencies. Finally, it discusses challenges like testing code that relies on external components and provides strategies for database testing.
Model View Controller (MVC)
Model View Controller (MVC)Javier Antonio Humarán Peñuñuri The document describes the Model-View-Controller (MVC) software architectural pattern. MVC separates an application into three main components: the model, the view, and the controller. The model manages the application's data and business logic. The view displays the model's information. The controller interprets inputs from the user and updates the model and/or view accordingly. This separation of concerns makes the application modular, reusable, and maintainable.
Mvc architecture
Mvc architectureSurbhi Panhalkar The document discusses the Model-View-Controller (MVC) design pattern. MVC separates an application's logic into three main components: the model, the view, and the controller. The model manages the application's data and logic, the view displays the data to the user, and the controller interprets user input and updates the model. MVC improves separation of concerns and makes applications more modular, extensible, and testable. It is commonly used for web applications, where the server handles the model and controller logic while the client handles the view.
Behavior Driven Development with Cucumber
Behavior Driven Development with CucumberBrandon Keepers This document discusses Behavior Driven Development (BDD) with Cucumber. It provides an example feature file for adding movies to a Netflix queue. It then demonstrates how to install and use Cucumber, including defining step definitions and integrating it with Rails. The document concludes that Cucumber allows specifying and testing software behavior through plain language examples.
Automated Web Testing using JavaScript
Automated Web Testing using JavaScriptSimon Guest The document discusses automated web testing using JavaScript, highlighting various frameworks and tools such as QUnit, Selenium, Jasmine, and Protractor. It explores the differences between unit and end-to-end testing, as well as the use of headless browsers like PhantomJS for testing without a GUI. The session aims to provide insights into the benefits of JavaScript for testing and the diverse options available for creating robust web tests.
Viking academy backbone.js
Viking academy backbone.jsBert Wijnants Backbone.js is a JavaScript framework that provides structure and conventions for developing single-page web applications. It helps avoid unnecessary DOM manipulations by separating the application state from the DOM using models. Views observe changes to models and re-render the DOM accordingly. Models can be synced to a back-end API to persist data. Backbone.js uses an MVVM pattern with models representing the application state, views for rendering, and the DOM acting as the view model.
Javascript for Wep Apps
Javascript for Wep AppsMichael Puckett JavaScript frameworks allow business logic to run on the client by sending JSON data on page load rather than dynamic HTML. This allows JavaScript to set up objects and classes to make assumptions without round trips to the server, improving performance. Popular frameworks like Backbone, Ember, Angular, Knockout, and Meteor emphasize separating UI from logic, data binding, templating, and routing to enable single-page applications. Meteor stands out by using the same syntax on client and server and web sockets for automatic UI updates.
Introduction to Knockoutjs
Introduction to Knockoutjsjhoguet Knockout.js is a JavaScript MVVM framework that enables simpler and reusable frontend code with cleaner communication to the backend. It features observable view models, declarative templated views, and enables cleaner model binding compared to traditional approaches. The presentation provides an overview of Knockout.js, demonstrates basic concepts like observables and view models, and discusses best practices and resources for further learning Knockout.js.
MV* presentation frameworks in Javascript: en garde, pret, allez!
MV* presentation frameworks in Javascript: en garde, pret, allez!Roberto Messora The document discusses the differences between two popular JavaScript presentation frameworks, Backbone.js and Knockout.js, focusing on their architectural patterns: MVC and MVVM. It highlights their strengths, weaknesses, and suitability for various web application development scenarios, as well as historical context and evolution of presentation design patterns. The session also emphasizes the importance of structured organization, maintainability, and testing in client-side development.
MVC pattern for widgets
MVC pattern for widgetsBehnam Taraghi This document discusses building maintainable and extensible JavaScript applications using a modular architecture pattern. It recommends separating an application into independent modules that communicate through well-defined interfaces. Each module should live within its own "sandbox" to achieve loose coupling and allow refactoring without affecting other modules. The document then introduces the Model-View-Controller (MVC) pattern as an implementation of this modular architecture for web applications. It provides JavaScript examples of implementing MVC by defining private module areas and interfaces that modules use to communicate and pass data between each other.
Give your web apps some backbone
Give your web apps some backboneRTigger The document discusses the Model-View-Controller (MVC) pattern and how Backbone.js implements it for single-page web applications. MVC originated in the 1970s and separates an application into three responsibilities - the model manages the data, view displays it, and controller handles user input. Backbone.js provides structure for web apps using MVC concepts with a RESTful API, event system, and routing. It embraces extensibility while remaining unopinionated.
Clean Javascript
Clean JavascriptRyunosuke SATO The document discusses techniques for writing clean JavaScript code. It provides examples of code smells and improvements to address issues like attaching events from the outside, separating selection from logic, shallow scope, overwriting default behavior, and separating logic from views. The document advocates for practices like modularizing functions, separating DOM manipulation from models, and creating model objects to represent DOM elements rather than directly manipulating the DOM. It encourages learning clean JavaScript techniques to write better structured and more maintainable code.
Planbox Backbone MVC
Planbox Backbone MVCAcquisio The document discusses the migration of Model-View-Controller (MVC) architecture from the back-end to the front-end using Backbone.js, emphasizing the benefits of using JavaScript for MVC implementation. It outlines the limitations of traditional back-end MVC approaches and describes how Backbone.js facilitates a more dynamic and decoupled application structure, allowing for rapid development and better client-server interaction. Key features of Backbone.js, including models, collections, and views, are explained with code examples demonstrating their functionality.
More Related Content
Viewers also liked (14)
JavaScript Unit Testing
JavaScript Unit TestingChristian Johansen This document discusses and compares several JavaScript unit testing tools and techniques:
1. JsUnitTest is a simple standalone tool that uses fixtures loaded in the browser but does not scale well and requires browser interaction.
2. BlueRidge is integrated with Rails and easy to set up but runs tests in non-browser environments.
3. JsTestDriver runs tests across multiple actual browsers simultaneously from the command line and scales well but currently lacks support for asynchronous tests.
ASP.NET MVC Fundamental
ASP.NET MVC Fundamentalldcphuc This document provides an overview and introduction to ASP.NET MVC 3 training. It discusses the evolution of ASP.NET, key concepts of MVC like models, views, and controllers, how MVC works, and differences between MVC and web forms. The training will build a simple ASP.NET MVC application and cover controllers, models, views, routing, and action results.
Advanced QUnit - Front-End JavaScript Unit Testing
Advanced QUnit - Front-End JavaScript Unit TestingLars Thorup The document provides an advanced overview of using QUnit for front-end JavaScript unit testing, focusing on techniques such as mocking, spying, and stubbing methods to enhance test reliability and speed. It discusses how to conduct isolation testing, avoid waiting for asynchronous processes, and efficiently handle global functions and AJAX requests within tests. Additionally, it touches upon memory leak detection and the importance of cleanup after tests to ensure accurate and performant unit tests.
Qunit Java script Un
Qunit Java script Unakanksha arora The document discusses unit testing and test-driven development. It introduces the QUnit JavaScript testing framework, describing how to write tests and assertions using its API. Key aspects covered include setting up QUnit, the test and assert functions, asynchronous testing, grouping tests into modules, and integrating automated testing with Node and Grunt.
JavaScript Test-Driven Development (TDD) with QUnit
JavaScript Test-Driven Development (TDD) with QUnitTasanakorn Phaipool This document summarizes a presentation on test-driven development with QUnit for JavaScript. It includes an agenda, explanations of TDD and the QUnit testing framework, and an example of writing tests and code for a telephone number validation function using QUnit. The document demonstrates how to set up a basic test suite with QUnit, write tests, write code to pass the tests, and refactor the code while ensuring tests continue to pass.
DDD, CQRS and testing with ASP.Net MVC
DDD, CQRS and testing with ASP.Net MVCAndy Butland This document provides an overview of a presentation on Domain Driven Design (DDD), Command Query Responsibility Segregation (CQRS), and testing with ASP.Net MVC. It introduces the presenter and gives an outline of the topics to be covered, including implementing DDD with ASP.Net MVC and Entity Framework, using a mediator pattern for CQRS, and unit testing models, queries, and commands. References are given to other authors and resources that influenced the approaches and implementations discussed in the presentation.
Understanding JavaScript Testing
Understanding JavaScript Testingjeresig This document discusses JavaScript testing and provides examples of writing tests and using testing frameworks like QUnit and JSUnit. It covers:
- Why test JavaScript code due to cross-browser issues and bugs
- Components of a test suite including tests, assertions, and a test runner
- Examples of writing basic tests with assertions and handling asynchronous tests
- Popular JavaScript testing frameworks like QUnit, JSUnit, YUITest
Laws of test automation framework
Laws of test automation frameworkvodqancr The document discusses three "laws of test automation framework":
1) Test frameworks will continue growing unless changes are made, leading to complex step definitions and refactoring issues.
2) The more complex ("messy") a test framework becomes, the more effort is required to maintain it.
3) Changes to test frameworks can cause pushback from business and technical issues like merge conflicts and build failures.
The document promotes a Model-View-Controller approach to structure Cucumber tests to improve code quality and maintainability. Declarative styles are preferable to imperative to make tests more robust to business changes. Regular monitoring, desk checks, and appropriate timing of changes can help address challenges.
CQRS на практике. В поиске точки масштабирования и новых метафор
CQRS на практике. В поиске точки масштабирования и новых метафорAlexander Byndyu Документ рассматривает практическое применение паттерна CQRS (Command Query Responsibility Segregation) и его эволюцию в контексте разработки приложений. Особое внимание уделяется разделению команд и запросов, а также подходам к реализации и event sourcing. В дополнение к теоретическим аспектам, автор приводит примеры реализации, ограничения и рекомендации по оптимизации архитектуры приложений.
Unit and integration Testing
Unit and integration TestingDavid Berliner This document discusses unit and integration testing. It begins by explaining the benefits of testing, such as reducing bugs and allowing safe refactoring. It then describes different types of tests like unit, integration, and database tests. The document focuses on unit testing, explaining how to write and organize unit tests using PHPUnit. It provides examples of test assertions and annotations. It also covers mocking and stubbing dependencies. Finally, it discusses challenges like testing code that relies on external components and provides strategies for database testing.
Model View Controller (MVC)
Model View Controller (MVC)Javier Antonio Humarán Peñuñuri The document describes the Model-View-Controller (MVC) software architectural pattern. MVC separates an application into three main components: the model, the view, and the controller. The model manages the application's data and business logic. The view displays the model's information. The controller interprets inputs from the user and updates the model and/or view accordingly. This separation of concerns makes the application modular, reusable, and maintainable.
Mvc architecture
Mvc architectureSurbhi Panhalkar The document discusses the Model-View-Controller (MVC) design pattern. MVC separates an application's logic into three main components: the model, the view, and the controller. The model manages the application's data and logic, the view displays the data to the user, and the controller interprets user input and updates the model. MVC improves separation of concerns and makes applications more modular, extensible, and testable. It is commonly used for web applications, where the server handles the model and controller logic while the client handles the view.
Behavior Driven Development with Cucumber
Behavior Driven Development with CucumberBrandon Keepers This document discusses Behavior Driven Development (BDD) with Cucumber. It provides an example feature file for adding movies to a Netflix queue. It then demonstrates how to install and use Cucumber, including defining step definitions and integrating it with Rails. The document concludes that Cucumber allows specifying and testing software behavior through plain language examples.
Automated Web Testing using JavaScript
Automated Web Testing using JavaScriptSimon Guest The document discusses automated web testing using JavaScript, highlighting various frameworks and tools such as QUnit, Selenium, Jasmine, and Protractor. It explores the differences between unit and end-to-end testing, as well as the use of headless browsers like PhantomJS for testing without a GUI. The session aims to provide insights into the benefits of JavaScript for testing and the diverse options available for creating robust web tests.
Similar to Unit Testing in JavaScript with MVC and QUnit (20)
Viking academy backbone.js
Viking academy backbone.jsBert Wijnants Backbone.js is a JavaScript framework that provides structure and conventions for developing single-page web applications. It helps avoid unnecessary DOM manipulations by separating the application state from the DOM using models. Views observe changes to models and re-render the DOM accordingly. Models can be synced to a back-end API to persist data. Backbone.js uses an MVVM pattern with models representing the application state, views for rendering, and the DOM acting as the view model.
Javascript for Wep Apps
Javascript for Wep AppsMichael Puckett JavaScript frameworks allow business logic to run on the client by sending JSON data on page load rather than dynamic HTML. This allows JavaScript to set up objects and classes to make assumptions without round trips to the server, improving performance. Popular frameworks like Backbone, Ember, Angular, Knockout, and Meteor emphasize separating UI from logic, data binding, templating, and routing to enable single-page applications. Meteor stands out by using the same syntax on client and server and web sockets for automatic UI updates.
Introduction to Knockoutjs
Introduction to Knockoutjsjhoguet Knockout.js is a JavaScript MVVM framework that enables simpler and reusable frontend code with cleaner communication to the backend. It features observable view models, declarative templated views, and enables cleaner model binding compared to traditional approaches. The presentation provides an overview of Knockout.js, demonstrates basic concepts like observables and view models, and discusses best practices and resources for further learning Knockout.js.
MV* presentation frameworks in Javascript: en garde, pret, allez!
MV* presentation frameworks in Javascript: en garde, pret, allez!Roberto Messora The document discusses the differences between two popular JavaScript presentation frameworks, Backbone.js and Knockout.js, focusing on their architectural patterns: MVC and MVVM. It highlights their strengths, weaknesses, and suitability for various web application development scenarios, as well as historical context and evolution of presentation design patterns. The session also emphasizes the importance of structured organization, maintainability, and testing in client-side development.
MVC pattern for widgets
MVC pattern for widgetsBehnam Taraghi This document discusses building maintainable and extensible JavaScript applications using a modular architecture pattern. It recommends separating an application into independent modules that communicate through well-defined interfaces. Each module should live within its own "sandbox" to achieve loose coupling and allow refactoring without affecting other modules. The document then introduces the Model-View-Controller (MVC) pattern as an implementation of this modular architecture for web applications. It provides JavaScript examples of implementing MVC by defining private module areas and interfaces that modules use to communicate and pass data between each other.
Give your web apps some backbone
Give your web apps some backboneRTigger The document discusses the Model-View-Controller (MVC) pattern and how Backbone.js implements it for single-page web applications. MVC originated in the 1970s and separates an application into three responsibilities - the model manages the data, view displays it, and controller handles user input. Backbone.js provides structure for web apps using MVC concepts with a RESTful API, event system, and routing. It embraces extensibility while remaining unopinionated.
Clean Javascript
Clean JavascriptRyunosuke SATO The document discusses techniques for writing clean JavaScript code. It provides examples of code smells and improvements to address issues like attaching events from the outside, separating selection from logic, shallow scope, overwriting default behavior, and separating logic from views. The document advocates for practices like modularizing functions, separating DOM manipulation from models, and creating model objects to represent DOM elements rather than directly manipulating the DOM. It encourages learning clean JavaScript techniques to write better structured and more maintainable code.
Planbox Backbone MVC
Planbox Backbone MVCAcquisio The document discusses the migration of Model-View-Controller (MVC) architecture from the back-end to the front-end using Backbone.js, emphasizing the benefits of using JavaScript for MVC implementation. It outlines the limitations of traditional back-end MVC approaches and describes how Backbone.js facilitates a more dynamic and decoupled application structure, allowing for rapid development and better client-server interaction. Key features of Backbone.js, including models, collections, and views, are explained with code examples demonstrating their functionality.
Backbone.js slides
Backbone.js slidesAmbert Ho Backbone.js abstracts remote resources into models and collections that emit events on state changes. This allows views to bind and respond to those changes. It provides concepts like models, collections, views and controllers to deal with common problems in web development like organizing rendering of views, supporting navigation, and avoiding callback soup. By abstracting functionality, separating concerns, and decoupling code, Backbone follows best practices and theoretical definitions of frameworks.
Writing and Testing JavaScript-heavy Web 2.0 apps with JSUnit
Writing and Testing JavaScript-heavy Web 2.0 apps with JSUnitAlex Chaffee The document discusses the architectural considerations and testing frameworks for JavaScript-heavy web applications, particularly those utilizing AJAX. It covers various application architectures, testing strategies, and tools like JSUnit and Selenium for unit and integration testing, alongside practical examples. Additionally, it highlights challenges such as latency in AJAX calls and methods for effective client-server communication.
Angular js gtg-27feb2013
Angular js gtg-27feb2013Nitya Narasimhan This document introduces AngularJS, an open-source JavaScript framework maintained by Google. It discusses AngularJS's MVC architecture with declarative views bound to imperative controllers via scopes. Key concepts covered include directives, filters, services and dependency injection. The document recommends resources for learning AngularJS and offers to provide deeper dives into specific AngularJS features and techniques.
Rp 6 session 2 naresh bhatia
Rp 6 session 2 naresh bhatiasapientindia 1) The document discusses how to build modular web applications using the JavaScript frameworks Backbone.js and RequireJS. It advocates separating an application into reusable components using the Model-View-Controller (MVC) pattern and composing the interface from independent views.
2) RequireJS allows code to be split into bite-sized modules and defines dependencies between modules. This supports large-scale application development and avoids dependency issues.
3) The document provides an example of a fictitious stock trading application called Bullsfirst that demonstrates these techniques and emphasizes the importance of architecture for engaging web applications.
Codemotion 2013 - Designing complex applications using html5 and knockoutjs
Codemotion 2013 - Designing complex applications using html5 and knockoutjsFabio Franzini The document discusses tools and frameworks for building complex applications using HTML5 and JavaScript. It begins with introductions and background on the speaker. The rest of the document outlines various topics: HTML5 and its benefits, JavaScript and patterns like modularity, client-side frameworks like KnockoutJS, server-side tools like TypeScript, packaging apps with Cordova or AppJS, and demonstrates some of the frameworks.
Sugarcoating your frontend one ViewModel at a time
Sugarcoating your frontend one ViewModel at a timeEinar Ingebrigtsen This document discusses modern JavaScript development approaches like MVVM and KnockoutJS. It promotes using a ViewModel pattern to separate application logic and state from the view. This improves testability and avoids issues like tightly coupled JavaScript code. The document provides examples of building Single Page Applications with KnockoutJS, handling dependencies through AMD, and using frameworks to create composable user interfaces. Overall it advocates for test-driven development and leveraging new JavaScript capabilities for building maintainable, modular applications.
Javascript frameworks: Backbone.js
Javascript frameworks: Backbone.jsSoós Gábor 1. Backbone.js is a lightweight JavaScript framework that brings structure to client-side code through an MVC pattern.
2. It separates presentation logic from business logic by defining Models, Collections, and Views. Models represent data, Collections hold lists of Models, and Views render the UI and handle events.
3. While Backbone.js allows building single page applications quickly, code can become disorganized without its structure. The framework encourages maintainable, loosely coupled code through its MVC implementation.
Architecting non-trivial browser applications (Jazoon 2012)
Architecting non-trivial browser applications (Jazoon 2012)Marc Bächinger The document discusses architecting non-trivial browser applications. It outlines the modern web application paradigm with client-server interactions over HTTP and separating concerns between frontend and backend. The consequences of this new architecture include better user experience but also increasing complexity on the client-side. The document advocates embracing this complexity through goals like reusability, encapsulation, and separation of concerns to support sustainable development of complex JavaScript applications.
Single Page Web Applications with CoffeeScript, Backbone and Jasmine
Single Page Web Applications with CoffeeScript, Backbone and JasminePaulo Ragonha This document discusses using CoffeeScript, Backbone.js, and Jasmine BDD to build single page web applications. It begins by explaining why CoffeeScript is useful for cleaning up JavaScript code and avoiding errors. It then discusses how Backbone.js provides structure for single page apps by defining models, collections, views and routers. It notes that Backbone works well with CoffeeScript. Finally, it mentions that Jasmine BDD can be used for writing professional tests.
Single Page Applications - Desert Code Camp 2012
Single Page Applications - Desert Code Camp 2012Adam Mokan The document discusses the advantages and considerations of adopting single-page applications (SPAs), highlighting their key characteristics and deployment benefits. It emphasizes the importance of having a capable development team familiar with JavaScript and REST APIs, along with selecting appropriate frameworks and tools. It also outlines potential challenges and the need for ongoing education, refactoring, and effective workflow optimization in SPA development.
Wintellect - Devscovery - Enterprise JavaScript Development 2 of 2
Wintellect - Devscovery - Enterprise JavaScript Development 2 of 2Jeremy Likness This document summarizes a presentation on JavaScript frameworks and libraries. It discusses tools like JSLint and JSHint for code quality, jQuery for DOM manipulation, JSON and Web API for data, Twitter Bootstrap for layouts, Underscore.js for utility functions, Backbone.js for MVC, RequireJS for dependencies, Kendo UI for MVVM, and Amplify.js for pub/sub messaging. It recommends using these libraries to make code cross-browser compatible, modular, data-friendly, consistent, and decoupled.
Single Page Application
Single Page ApplicationPrasad Narasimhan The document discusses single page applications (SPAs) and how AngularJS can be used to build them. Some key points:
- SPAs load all necessary code (HTML, CSS, JavaScript) with a single page load and update dynamically without reloading the page. This provides a more desktop-like user experience.
- AngularJS supports building SPAs through features like data binding, scopes, controllers, services, and directives that help manage state and update the view.
- In an AngularJS SPA, the server handles CRUD operations and authentication through a REST API, while the client manages the UI, makes AJAX calls, and performs routing and validation.
- AngularJS
Ad
More from Lars Thorup (18)
100 tests per second - 40 releases per week
100 tests per second - 40 releases per weekLars Thorup Triggerz, a SaaS company founded in 2016, employs a continuous delivery model with 100 tests per second and 20-40 releases per week, enhancing developer feedback and user experience. The deployment strategy includes features like feature toggles and zero-downtime upgrades, allowing for rapid functionality updates and easier problem resolution. Overall, the approach requires significant initial investment in testing and automation but leads to more efficient and effective production management.
SQL or NoSQL - how to choose
SQL or NoSQL - how to chooseLars Thorup The document compares SQL and NoSQL database systems, discussing their history, differences, and use cases. It highlights key examples such as Redis, a NoSQL database known for its speed and versatility, and outlines the characteristics of typical SQL and NoSQL databases. The author emphasizes the importance of matching database systems to specific application needs and provides demos of various Redis functionalities.
Super fast end-to-end-tests
Super fast end-to-end-testsLars Thorup The document discusses the challenges of end-to-end testing, highlighting their slowness, lack of precision, complexity, and fragility compared to unit tests. It emphasizes that while unit tests are efficient and reliable, they can be misleading due to mocked dependencies. The author proposes a solution that integrates both testing methods to achieve faster, more accurate, and robust testing outcomes, demonstrated through a sample implementation using Node.js.
Extreme Programming - to the next-level
Extreme Programming - to the next-levelLars Thorup This document discusses taking extreme programming principles to the next level by turning traditional practices "up to 11". It explores several ideas for achieving faster feedback including mob programming, continuous deployment, hypothesis-driven user stories, shared product ownership, monitoring-driven development, and continuous learning. The author asks the reader to consider which ideas may work to implement in their organization this month.
Advanced Javascript Unit Testing
Advanced Javascript Unit TestingLars Thorup This document summarizes best practices for JavaScript unit testing presented by Lars Thorup. It discusses how to test asynchronous code using callbacks and promises, fake timers to test delayed behavior, mock the DOM and AJAX requests, enable cross-browser testing using Karma, and detect memory leaks between tests. Lars Thorup is a software developer who focuses on JavaScript, TDD, and continuous integration.
Unit testing legacy code
Unit testing legacy codeLars Thorup Lars Thorup's document discusses strategies for managing and refactoring legacy code by implementing unit tests to regain control over the codebase. It emphasizes the importance of characterization tests, gradual refactoring, and developing sustainable practices to improve code quality while minimizing risks. The document details a step-by-step approach to transitioning from legacy systems to modern implementations through careful testing and incremental changes.
Put "fast" back in "fast feedback"
Put "fast" back in "fast feedback"Lars Thorup The document emphasizes the importance of fast feedback in software development to enhance productivity, reduce risk, and lower the cost of change. It contrasts slow and fast feedback systems through various real-life examples and outlines criteria for achieving fast feedback, such as maintaining high unit test coverage and frequent commits. It advocates for adopting practices like test-driven development and continuous integration to promote faster, more efficient software delivery.
Database Schema Evolution
Database Schema EvolutionLars Thorup The document discusses strategies for managing database schema evolution, focusing on version control, migration automation, and development practices. It emphasizes the importance of keeping the database and application in sync, avoiding shared development databases, and utilizing tools like Flyway and Liquibase for migration management. Additionally, it outlines solutions for common issues such as failed tests, upgrade conflicts, and the need for reliable test environments.
Advanced Jasmine - Front-End JavaScript Unit Testing
Advanced Jasmine - Front-End JavaScript Unit TestingLars Thorup This document discusses advanced techniques for front-end JavaScript unit testing using Jasmine, including mocking methods, constructors, timers, and AJX requests to test code in isolation without dependencies and speed up tests. It also covers spying on events, simulating CSS transitions, using custom matchers, structuring test code, and browser-specific testing. The presenter is Lars Thorup, a software developer and coach who founded ZeaLake and teaches agile and automated testing.
Javascript unit testing with QUnit and Sinon
Javascript unit testing with QUnit and SinonLars Thorup This document discusses JavaScript unit testing with QUnit and Sinon. It introduces Lars Thorup and his background in software development, testing, and coaching. It then provides an overview of unit testing, explaining why it is beneficial and how to implement it. Finally, it demonstrates various QUnit and Sinon techniques for writing tests, including assertions, spies, stubs, mocks, asynchronous code, the DOM, and advanced mocking.
Continuous Integration for front-end JavaScript
Continuous Integration for front-end JavaScriptLars Thorup The document discusses continuous integration for front-end JavaScript, highlighting tools such as Grunt, JSHint, and Jasmine for testing and analysis. It includes example code for functions, testing strategies, and how to set up configurations in a Grunt file. Additionally, it covers code coverage metrics and integrates with Jenkins for reporting.
Automated Performance Testing
Automated Performance TestingLars Thorup Lars Thorup is a software developer and founder of Zealake, focused on automated performance testing and agile methodologies. The document discusses strategies for measuring performance, including the use of automated tests with tools like TeamCity and Jenkins, and emphasizes the importance of trend analysis for identifying performance issues. It highlights the need for ongoing inspection to maintain performance metrics and describes the performance reporting processes.
Test and Behaviour Driven Development (TDD/BDD)
Test and Behaviour Driven Development (TDD/BDD)Lars Thorup The document outlines the principles and workflows of Test-Driven Development (TDD) and Behavior-Driven Development (BDD), emphasizing their benefits in improving software design and bug detection. It discusses various types of automated tests, strategies for writing and maintaining tests, and the importance of integrating testing in the development process. Additionally, it addresses practical examples, including real-world applications and considerations for legacy code management.
Agile Contracts
Agile ContractsLars Thorup The document discusses Lars Thorup's expertise in agile software consulting and outlines a contract model that combines traditional payment structures with agile practices. It highlights three case studies showcasing the agile development process, emphasizing collaboration, flexible requirements, and incremental delivery to enhance project efficiency. The advantages of this model include cost savings, faster ROI, and shared risks and gains between clients and vendors, contingent on their respective maturity levels.
High Performance Software Engineering Teams
High Performance Software Engineering TeamsLars Thorup The document details best practices for creating high-performance engineering teams in software development, emphasizing the importance of automation, continuous integration, and collaboration between engineering and QA. Key strategies include reducing non-productive activities, enhancing testing frequency and quality, and prioritizing bug fixes. It also highlights the significance of using frameworks for automated unit and acceptance testing, as well as encouraging a culture of continuous improvement and transparency.
Elephant Carpaccio
Elephant CarpaccioLars Thorup Here are some tips for breaking down work in an agile way:
- Focus on delivering value to users. Each story and task should provide some value.
- Iterate frequently. Stories and tasks should be small enough that you can complete and release them within a sprint or two.
- Get early feedback. Small slices allow testing work sooner and adjusting based on feedback.
- Prioritize flexibility. Small slices give you options to reorder or drop work as priorities change.
- Estimate costs accurately. Tasks should take 1-5 days; if longer, may need refactoring. Consider spikes for technical challenges.
- Refactor when repetitive. If work is very similar, look for ways to simplify through ref
Automated Testing for Embedded Software in C or C++
Automated Testing for Embedded Software in C or C++Lars Thorup This document discusses automated testing for embedded C software. It introduces Lars Thorup and provides an agenda for the document. It then defines automated testing, describes the Unity testing framework for embedded C, and provides an example of how to handle dependencies in testing. It advocates for continuous integration, breaking dependencies through abstraction and injection, and explains how automated testing can improve software quality through faster development and preventing bugs.
Introduction to Automated Testing
Introduction to Automated TestingLars Thorup The document provides an introduction to automated testing, emphasizing the importance of writing tests to improve software development efficiency and design. It outlines various types of automated tests, including unit tests and system tests, and discusses best practices for integrating testing into the development process. The presentation highlights real-world examples and tools available for automated testing, advocating for a culture that prioritizes test-driven development.
Ad
Recently uploaded (20)
"Database isolation: how we deal with hundreds of direct connections to the d...
"Database isolation: how we deal with hundreds of direct connections to the d...Fwdays What can go wrong if you allow each service to access the database directly? In a startup, this seems like a quick and easy solution, but as the system scales, problems appear that no one could have guessed.
In my talk, I'll share Solidgate's experience in transforming its architecture: from the chaos of direct connections to a service-based data access model. I will talk about the transition stages, bottlenecks, and how isolation affected infrastructure support. I will honestly show what worked and what didn't. In short, we will analyze the controversy of this talk.
Connecting Data and Intelligence: The Role of FME in Machine Learning
Connecting Data and Intelligence: The Role of FME in Machine LearningSafe Software In this presentation, we want to explore powerful data integration and preparation for Machine Learning. FME is known for its ability to manipulate and transform geospatial data, connecting diverse data sources into efficient and automated workflows. By integrating FME with Machine Learning techniques, it is possible to transform raw data into valuable insights faster and more accurately, enabling intelligent analysis and data-driven decision making.
Securing Account Lifecycles in the Age of Deepfakes.pptx
Securing Account Lifecycles in the Age of Deepfakes.pptxFIDO Alliance Securing Account Lifecycles in the Age of Deepfakes
The Future of Technology: 2025-2125 by Saikat Basu.pdf
The Future of Technology: 2025-2125 by Saikat Basu.pdfSaikat Basu A peek into the next 100 years of technology. From Generative AI to Global AI networks to Martian Colonisation to Interstellar exploration to Industrial Nanotechnology to Artificial Consciousness, this is a journey you don't want to miss. Which ones excite you the most? Which ones are you apprehensive about? Feel free to comment! Let the conversation begin!
Smarter Aviation Data Management: Lessons from Swedavia Airports and Sweco
Smarter Aviation Data Management: Lessons from Swedavia Airports and SwecoSafe Software Managing airport and airspace data is no small task, especially when you’re expected to deliver it in AIXM format without spending a fortune on specialized tools. But what if there was a smarter, more affordable way?
Join us for a behind-the-scenes look at how Sweco partnered with Swedavia, the Swedish airport operator, to solve this challenge using FME and Esri.
Learn how they built automated workflows to manage periodic updates, merge airspace data, and support data extracts – all while meeting strict government reporting requirements to the Civil Aviation Administration of Sweden.
Even better? Swedavia built custom services and applications that use the FME Flow REST API to trigger jobs and retrieve results – streamlining tasks like securing the quality of new surveyor data, creating permdelta and baseline representations in the AIS schema, and generating AIXM extracts from their AIS data.
To conclude, FME expert Dean Hintz will walk through a GeoBorders reading workflow and highlight recent enhancements to FME’s AIXM (Aeronautical Information Exchange Model) processing and interpretation capabilities.
Discover how airports like Swedavia are harnessing the power of FME to simplify aviation data management, and how you can too.
Powering Multi-Page Web Applications Using Flow Apps and FME Data Streaming
Powering Multi-Page Web Applications Using Flow Apps and FME Data StreamingSafe Software Unleash the potential of FME Flow to build and deploy advanced multi-page web applications with ease. Discover how Flow Apps and FME’s data streaming capabilities empower you to create interactive web experiences directly within FME Platform. Without the need for dedicated web-hosting infrastructure, FME enhances both data accessibility and user experience. Join us to explore how to unlock the full potential of FME for your web projects and seamlessly integrate data-driven applications into your workflows.
FIDO Seminar: New Data: Passkey Adoption in the Workforce.pptx
FIDO Seminar: New Data: Passkey Adoption in the Workforce.pptxFIDO Alliance FIDO Seminar: New Data: Passkey Adoption in the Workforce
FIDO Seminar: Perspectives on Passkeys & Consumer Adoption.pptx
FIDO Seminar: Perspectives on Passkeys & Consumer Adoption.pptxFIDO Alliance FIDO Seminar: Perspectives on Passkeys & Consumer Adoption
Information Security Response Team Nepal_npCERT_Vice_President_Sudan_Jha.pdf
Information Security Response Team Nepal_npCERT_Vice_President_Sudan_Jha.pdfICT Frame Magazine Pvt. Ltd. Artificial Intelligence (AI) is rapidly changing the face of cybersecurity across the globe. In Nepal, the shift is already underway. Vice President of the Information Security Response Team Nepal (npCERT) and Information Security Consultant at One Cover Pvt. Ltd., Sudan Jha, recently presented an in-depth workshop on how AI can strengthen national security and digital defenses.
PyCon SG 25 - Firecracker Made Easy with Python.pdf
PyCon SG 25 - Firecracker Made Easy with Python.pdfMuhammad Yuga Nugraha Explore the ease of managing Firecracker microVM with the firecracker-python. In this session, I will introduce the basics of Firecracker microVM and demonstrate how this custom SDK facilitates microVM operations easily. We will delve into the design and development process behind the SDK, providing a behind-the-scenes look at its creation and features. While traditional Firecracker SDKs were primarily available in Go, this module brings a simplicity of Python to the table.
FIDO Seminar: Authentication for a Billion Consumers - Amazon.pptx
FIDO Seminar: Authentication for a Billion Consumers - Amazon.pptxFIDO Alliance FIDO Seminar: Authentication for a Billion Consumers - Amazon
Coordinated Disclosure for ML - What's Different and What's the Same.pdf
Coordinated Disclosure for ML - What's Different and What's the Same.pdfPriyanka Aash Coordinated Disclosure for ML - What's Different and What's the Same
9-1-1 Addressing: End-to-End Automation Using FME
9-1-1 Addressing: End-to-End Automation Using FMESafe Software This session will cover a common use case for local and state/provincial governments who create and/or maintain their 9-1-1 addressing data, particularly address points and road centerlines. In this session, you'll learn how FME has helped Shelby County 9-1-1 (TN) automate the 9-1-1 addressing process; including automatically assigning attributes from disparate sources, on-the-fly QAQC of said data, and reporting. The FME logic that this presentation will cover includes: Table joins using attributes and geometry, Looping in custom transformers, Working with lists and Change detection.
GenAI Opportunities and Challenges - Where 370 Enterprises Are Focusing Now.pdf
GenAI Opportunities and Challenges - Where 370 Enterprises Are Focusing Now.pdfPriyanka Aash GenAI Opportunities and Challenges - Where 370 Enterprises Are Focusing Now
From Manual to Auto Searching- FME in the Driver's Seat
From Manual to Auto Searching- FME in the Driver's SeatSafe Software Finding a specific car online can be a time-consuming task, especially when checking multiple dealer websites. A few years ago, I faced this exact problem while searching for a particular vehicle in New Zealand. The local classified platform, Trade Me (similar to eBay), wasn’t yielding any results, so I expanded my search to second-hand dealer sites—only to realise that periodically checking each one was going to be tedious. That’s when I noticed something interesting: many of these websites used the same platform to manage their inventories. Recognising this, I reverse-engineered the platform’s structure and built an FME workspace that automated the search process for me. By integrating API calls and setting up periodic checks, I received real-time email alerts when matching cars were listed. In this presentation, I’ll walk through how I used FME to save hours of manual searching by creating a custom car-finding automation system. While FME can’t buy a car for you—yet—it can certainly help you find the one you’re after!
War_And_Cyber_3_Years_Of_Struggle_And_Lessons_For_Global_Security.pdf
War_And_Cyber_3_Years_Of_Struggle_And_Lessons_For_Global_Security.pdfbiswajitbanerjee38 Russia is one of the most aggressive nations when it comes to state coordinated cyberattacks — and Ukraine has been at the center of their crosshairs for 3 years. This report, provided the State Service of Special Communications and Information Protection of Ukraine contains an incredible amount of cybersecurity insights, showcasing the coordinated aggressive cyberwarfare campaigns of Russia against Ukraine.
It brings to the forefront that understanding your adversary, especially an aggressive nation state, is important for cyber defense. Knowing their motivations, capabilities, and tactics becomes an advantage when allocating resources for maximum impact.
Intelligence shows Russia is on a cyber rampage, leveraging FSB, SVR, and GRU resources to professionally target Ukraine’s critical infrastructures, military, and international diplomacy support efforts.
The number of total incidents against Ukraine, originating from Russia, has steadily increased from 1350 in 2021 to 4315 in 2024, but the number of actual critical incidents has been managed down from a high of 1048 in 2022 to a mere 59 in 2024 — showcasing how the rapid detection and response to cyberattacks has been impacted by Ukraine’s improved cyber resilience.
Even against a much larger adversary, Ukraine is showcasing outstanding cybersecurity, enabled by strong strategies and sound tactics. There are lessons to learn for any enterprise that could potentially be targeted by aggressive nation states.
Definitely worth the read!
AI VIDEO MAGAZINE - June 2025 - r/aivideo
AI VIDEO MAGAZINE - June 2025 - r/aivideo1pcity Studios, Inc AI VIDEO MAGAZINE - r/aivideo community newsletter – Exclusive Tutorials: How to make an AI VIDEO from scratch, PLUS: How to make AI MUSIC, Hottest ai videos of 2025, Exclusive Interviews, New Tools, Previews, and MORE - JUNE 2025 ISSUE -
Creating Inclusive Digital Learning with AI: A Smarter, Fairer Future
Creating Inclusive Digital Learning with AI: A Smarter, Fairer FutureImpelsys Inc. Have you ever struggled to read a tiny label on a medicine box or tried to navigate a confusing website? Now imagine if every learning experience felt that way—every single day.
For millions of people living with disabilities, poorly designed content isn’t just frustrating. It’s a barrier to growth. Inclusive learning is about fixing that. And today, AI is helping us build digital learning that’s smarter, kinder, and accessible to everyone.
Accessible learning increases engagement, retention, performance, and inclusivity for everyone. Inclusive design is simply better design.
Information Security Response Team Nepal_npCERT_Vice_President_Sudan_Jha.pdf
Information Security Response Team Nepal_npCERT_Vice_President_Sudan_Jha.pdfICT Frame Magazine Pvt. Ltd.
Unit Testing in JavaScript with MVC and QUnit
- 1. Unit Testing in JavaScript with MVC and QUnit Lars Thorup ZeaLake Software Consulting June 14, 2011
- 2. Who is Lars Thorup? ● Software developer ● Coach: Automated testing and other agile practices ● Advisor: Assesses software projects and companies ● Founder and CEO of BestBrains and ZeaLake
- 3. Agenda ● Sample application under test ● How to use QUnit ● Asynchronuous testing ● How to use Model-View-Controller ● Assumes knowledge about JavaScript ● Assumes knowledge about unit testing
- 4. JavaScript must be tested in the browser
- 5. Example app: Collaborative Dialog ● Front end entirely in JavaScript ● Back end service methods implemented in C#
- 6. How do tests look like? ● util.test.html ● ok(actual, message) ● equal(actual, expected, message) ● same(actual, expected, message) ● deep equivalence ● raises(expected, function, message)
- 7. How to modularize tests? ● view.test.html ● module(name, fixture) ● all following tests will have this being a newly created fixture object with setup() and teardown() run before and after the test
- 8. Testing ajax ● svc.test.html ● call expect(number-of-assertions) to verify that callbacks was actually called ● call stop(timeout) before first ajax call ● call start() when test is complete ● typically inside ajax callback ● if more than one asynchronous call in one test: ● call stop() before each ● call start() in callback of each
- 9. Make your JavaScript testable ● MVC design pattern: Model - View - Controller ● Dependency injection ● Isolated testing controller view model svc
- 10. View ● view.js controller ● injected html ● load html page from the server ● html becomes directly stylable view model ● Responsibilities svc ● manipulate html ● generate html from templates ● dispatch events to listeners ● nothing more! ● References ● a set of event listeners (typically the controller)
- 11. Controller ● controller.js controller ● Responsibilities ● handle all events from the view model view ● poll model for change events if relevant svc ● convert events to commands against the model ● repaint strategy ● error handling strategy ● References ● the model (to execute commands, polling) ● the view (to do repainting)
- 12. Model ● model.js controller ● Responsibilities ● cache state to minimize round view model trips ● provide view and controller with a useful interface of the svc data model ● References ● the service proxy
- 13. Service Proxy ● svc.js controller ● Responsibilities ● provide a javascript api view model mapping of the server api ● References svc ● the physical server via ajax
- 14. Testing the view ● view.test.js test ● Inject ● controllerStub ● canvas controllerStub ● Invoke methods view ● Assert ● canvas ● controllerStub
- 15. Testing the controller ● controller.test.js test ● Inject ● viewStub controller ● modelStub ● Invoke methods viewStub modelStub ● Assert ● viewStub ● modelStub
- 16. Testing the model ● model.test.js test ● Inject ● serverStub model ● Invoke methods ● Assert svcStub ● state ● serverStub
- 17. Testing the service proxy ● svc.test.js test ● Invoke methods ● Assert ● results svc
- 18. Callbacks in JavaScript ● Ajax means asynchronous ● Server methods become asynchronous ● Model methods become asynchronous ● To return a value you must supply a callback ● Error handling ● Include in every callback
- 19. this in JavaScript ● Avoid using this in callbacks, since this probably refers to the object that invokes the callback, not the object that contains the code for the callback. ● Instead use jQuery's $proxy() method ● Example: controller.js
- 20. Bootstrap ● bootstrap() function ● see collabForm.js ● creates model, view and controller and ties them together ● start polling engine (if relevant) ● called by onload or $(document).ready() ● see Index.aspx
- 21. Run tests on build server ● QUnit tests needs to run in a browser ● On WIndows, the browser requires a WinStation ● So the build server must be logged on at all times for this to work ● Hard to avoid tests that hang ● Consider running tests manually instead
- 22. Testing the backend ● Test your webservices ● Use QUnit and assert on the returned JSON ● Or use your backend testing tool
- 23. Real World Example ● WizerPro, in JavaScript, using MVC pattern
- 24. Further reading ● Documentation ● http://docs.jquery.com/Qunit ● Book ● "Test-Driven JavaScript Development", Christian Johansen ● QUnit Presentation ● http://benalman.com/talks/unit-testing-qunit.html
- 25. Future meetups ● TDD coding dojo with C++ and Ruby ● Thursday June 24th (in a week!)
- 26. Feedback ● Give your evaluation at meetup.com