Unit Testing in JavaScript

Jun 11, 20150 likes561 views

This document summarizes a talk on unit testing in JavaScript. It introduces the speaker and their company Third Wave Technology. It then defines unit testing as writing code to test individual units in isolation. The benefits of unit testing are discussed such as speeding up development, providing documentation, and helping write better code. Popular JavaScript unit testing frameworks like QUnit and Jasmine are presented. The document concludes by suggesting factors to consider when choosing a unit testing framework.

Unit Testing in
JavaScript
Robert Scaduto | @scardetto
Third Wave Technology

About Me
• President and CTO of Third
Wave Technology
• Developing software
professionally since 1998
• Maintainer of a handful of
open source projects (Crux,
physique, build_number)
• Musician and aikido
practitioner

About Third Wave
• Boutique consulting ﬁrm
specializing in Agile
development
• Develop custom software for a
variety of languages and
platforms
• Strong focus on Agile
practices like Unit Testing and
Continuous Integration

What is Unit Testing?
• The practice of writing code to test individual
“units” in isolation.
• Originally conceived by Kent Beck in the
Smalltalk era. Made popular by JUnit.
• One of the pillars of Agile software development.

Why Unit Test?
• Speeds up the development cycle.
• Provides a safety net against enhancing or
refactoring existing code.
• Provides a living set of documentation about
how the code really works.
• Helps you write better code.

Better Design Through Tests
• Get immediate feedback from your API
decisions.
• Separates interface from implementation
concerns.
• Promotes the Single Responsibility Principle.
• Promotes the YAGNI principle. 
(You Ain’t Gonna Need It!)

Foundation of Quality
• Unit testing is not a
replacement for other forms of
testing.
• However, it does make testing
easier by reducing uncertainty
in individual units.
• When combined with other
types of automated and
manual testing, you can have
a high degree of conﬁdence in
the software.

Unit Testing Styles
• Test Driven Development (TDD) Style typically
structured via Arrange, Act, Assert (AAA).
• Behavior Driven Development (BDD) Style
• Both follow the Four Phase Test Form
Setup - Setup the unit under test. 
Exercise - Exercise the unit and capture results. 
Verify - Verify that the results meet expectations. 
Teardown - Cleanup any side effects of the test.

TDD Style
The Good 
Clearly shows how the API
will be used in “real” code.
The Caveat 
Can lead to bigger tests that
are less self documenting.

BDD Style
The Good 
Leads to self-documenting
speciﬁcations of units.
The Caveat 
The test code is spread out
and may be harder to grok.

QUnit 
http://qunit.js
• Developed by the jQuery
Team.
• Designed for testing in the
browser.
• However, it can be run from
the command line using a
headless browser like
phantomjs.
• Uses a TDD Style.
• Simple, ﬂat syntax.

Jasmine 
http://jasmine.github.io/
• Developed by Pivotal Labs.
• Designed to run in a DOM-
less environment.
• However, it can run in the
browser.
• BDD Style testing framework
heavily inﬂuenced by RSpec.
• Lots of built in features
including a ﬂuent assertion
syntax and spies.

Honorable Mentions
• Mocha + Chai - http://mochajs.org | http://chaijs.com
• BDD framework with simple syntax.
• Limited built in features but plays nice with other libraries.
• Chai provides a very nice ﬂuent assertions syntax.
• Jest - https://facebook.github.io/jest/
• Built on top of the Jasmine framework.
• Automatically mocks dependencies.
• Runs your tests using a fake DOM which makes it easy to run your tests
from the command line.

Which One Should You Use?
• Do you prefer a BDD or TDD syntax?
• Are you testing code that will always run in the
browser or will it run standalone?
• Are you using an application framework that
prefers one over another?

Thanks for Listening!
Tweet me if you have questions: 
@scardetto
Source code available at:
github.com/scardetto/javascript-unit-testing-talk

The document discusses modern JavaScript tooling and trends. It outlines problems with existing tools like slow performance and poor source mapping. Emerging tools like Vitejs and Snowpack are faster and support ES modules and features like instant loading and HMR. The document argues the JavaScript ecosystem is entering a third age driven by ESM, Rust/Go for tooling, and emerging technologies like Deno. Resources are provided to learn more about Vitejs, Snowpack, and trends in frontend tooling.

JSFoo-2017 TakeawaysMir Ali

Saving Time By Testing With JestBen McCormick

Ben McCormick gave a presentation on how to save time by testing with Jest. He began with an introduction and explained that Jest is a JavaScript testing framework developed by Facebook that aims to solve common testing problems. He then demonstrated how Jest saves time through fast setup, writing tests quickly using familiar syntax and APIs, running tests in parallel and with a smart watch mode, and providing clear errors to fix tests fast. He concluded with a demo of Jest's features and took questions.

Can you TDD Rails?Andrzej Krzywda

The document discusses how test-driven development (TDD) can help address common fears and issues developers experience when working with existing or new code. It argues that while TDD may seem difficult with Rails, the challenges are likely due more to issues with the code structure rather than limitations of TDD or Rails. The document differentiates between hard skills related to TDD tools and techniques versus softer skills around understanding requirements, isolating business logic, continuous delivery, and refactoring tests. It provides suggestions for improving TDD skills like practicing with code katas, extracting business logic into gems, and doing "domain spikes" with in-memory objects to focus on logic alone.

Rails automatic test driven developmenttyler4long

This document discusses test driven development (TDD) for Ruby on Rails applications. It introduces TDD principles like the three laws and red-green-refactor cycle. It then provides an overview of testing tools for Rails like RSpec and Capybara for writing unit and integration tests. Additional tools that help with the testing workflow are also covered, such as Spork and Guard. The document demonstrates how to run tests directly from Sublime Text and provides references for further reading on TDD and Rails testing.

ОЛЕКСІЙ ОСТАПОВ «Найкрутіші особливості автоматизації на Playwright Python» K...QADay

Kyiv Quality Assurance Day 2021 ОЛЕКСІЙ ОСТАПОВ «Найкрутіші особливості автоматизації на Playwright Python» Слідкуйте за нами: Телеграм: t.me/goqameetup Linkedin: linkedin.com/company/goqa Fb: https://www.facebook.com/goqaevent Fb: https://www.facebook.com/qaday.org Youtube: https://www.youtube.com/channel/UCOyIrmpVbtqUZyRLxd9BKzA

Hello world - intro to node jsRefresh Annapolis Valley

Jeff Andersen from GoInstant Have you ever thought that writing web applications should allow you to use your mad Javascript skillz on the server side as well? Node.js is such a platform. Bundling up the Google Chrome Javascript runtime, Node lets you easily building fast and scalable network applications perfect for the real-time web. It's also a pretty great platform for building basic data driven websites too. Jeff, a web developer at Halifax based GoInstant, will introduce us to the Node platform, exploring it from the ground up.

Introduction to cypress in Angular (Chinese)Hong Tat Yew

Performance testing with VSTs on- and off-premisesJeff Bramwell

Many of us have been there before... You deploy your brand new web site to production, you know, the one that's going to make your company rich and you famous, and just as you're about to hit a thousand users, the site comes crashing down! If you haven?t experienced this, chances are you know someone who has.If you're building web apps and services for your organization you know how important it is to ensure those services are always up and running. While many of us go through great lengths to ensure we are testing the functionality of our systems we do not always take performance or system load into account.Visual Studio Team Services (VSTS) provides multiple options and avenues for enabling performance and load testing for your systems. For example, did you know that VSTS also supports JMeter tests? With VSTS you can even run performance tests using on-premises servers in your own data center. This talk will give you an overview of the performance and load testing capabilities of VSTS. If you haven't looked at the load testing features of VSTS lately, you should definitely check out this talk!

A tale of 3 databasesChris Skardon

This document summarizes Chris Skardon's experience migrating the database for his competition running site Tournr from SQL to document and graph databases. It describes how the initial database choice of SQL Server became limiting and led to migrations first to RavenDB, a document database, and then to Neo4j, a graph database. Both migrations required reworking the data model and code but provided performance and flexibility benefits. While challenging, the migrations were worthwhile as the graph model better fit Tournr's needs.

Cypress workshop for JSFoo 2019Biswajit Pattanayak

Cypress is a tool that allows writing automated tests in JavaScript to test frontend applications. It runs tests directly in the browser to avoid issues with end-to-end tests like flakiness and long setup times. Cypress taps into native browser APIs and uses a network proxy to control requests and avoid same-origin policy issues. It provides real-time DOM access, asynchronous commands, automatic retries, and the ability to stub network requests. While not fully open source and limited to JavaScript, Cypress aims to solve problems with traditional end-to-end testing.

Automated Testing with Cucumber, PhantomJS and SeleniumDev9Com

The document discusses Behavior Driven Development (BDD) using Cucumber, Selenium, and PhantomJS. Cucumber uses a natural language syntax called Gherkin to write automated acceptance tests. Selenium is used to automate interactions with a web browser, while PhantomJS allows running those tests headlessly on a CI server without requiring a graphical browser. The example project demonstrates how Cucumber features written by PMs/BAs can be linked to Selenium step definitions to test a web application.

Why use Go for web development?Weng Wei

This document discusses the suitability of Go for web development. It notes that while Go's built-in HTML template engine is basic, the Gorazor template engine provides a more powerful way to mix Go code into HTML templates. Code generation approaches also allow Go to behave more dynamically at runtime. Go's fast compilation and use of interfaces make it well-suited for dynamic web applications and large websites. The document concludes that while other languages may be more mature, Go is suitable for developing large, stable, scalable websites that need to be maintained over time.

Cypress first impressionsHans Emmel

Cypress vs Selenium WebDriver: Better, Or Just Different? -- by Gil TayarApplitools

** Full webinar recording: https://youtu.be/D7vxFuwnUio ** Watch Sr. Architect Gil Tayar's special hands-on session, where he explains & demonstrates how Selenium and Cypress differ. The session covers the following topics: * How and why do frontend developers write tests *Selenium architecture *Cypress architecture *Live Demo of Cypress - including how to write a Cypress test, and how it’s used *How Cypress deals with flakiness *Cypress and backdoors to development *Visual Testing using Cypress

Using REST with VSTS and TFSJeff Bramwell

This document contains an agenda for a presentation on using REST with Visual Studio Team Services (VSTS) and Team Foundation Server (TFS). The presentation will cover the history of APIs for VSTS/TFS, reasons for extending them, HTTP methods, debugging tools, authentication, using HttpClient vs HttpWebRequest, converting JSON to classes, and examples. It provides details on the available REST APIs, demonstrates creating a personal access token and calling an API to get a list of builds.

Paint it blue with PowerShellJaap Brasser

In IT when you spend too much time making mistakes because you did not use the correct tool, this is something that can lead to increased work pressure, working overtime and working in weekends, which is something that we should always strife to prevent. So it is similar in the sense the context switching is always going to give us delays. If we are able to leverage PowerShell correct we can prevent from having to switch between languages when working with different operating systems or clouds.

LONDON SDET MEETUP - Difference between Selenium and Cypress presentationSriram Angajala

This document summarizes a presentation comparing the automated testing tools Cypress and Selenium. It outlines key features of each tool such as browser support, speed, and capabilities. Cypress is described as a frontend testing tool that supports only Chrome and JavaScript, while Selenium supports multiple browsers and languages but requires more configuration. The presentation demonstrates Cypress for integration and end-to-end testing and concludes that Cypress may replace Selenium if it gains support for more browsers, remote execution, behavior-driven development, and additional programming languages.

ES2015 / ES6: Basics of modern JavascriptWojciech Dzikowski

Automated testing with CypressYong Shean Chong

This document introduces Cypress, an end-to-end testing framework for web applications. It discusses why Cypress is useful for testing, how to get started by installing Cypress and writing test scripts, and provides tips for selecting elements and handling dynamic content. Key aspects covered include planning test cases, writing tests for common pages like login and article creation, and using the Cypress testing library to write robust tests.

Conquering AngularJS LimitationsValeri Karpov

The document discusses strategies for addressing common AngularJS challenges including SEO, responsive design, and integration testing. It recommends using Prerender.io to generate static HTML for search engines to index Single Page Apps. For responsive design, it suggests using reactive directives that emit events in response to screen size changes rather than having directives know about screen size. Finally, it outlines an approach to integration testing AngularJS directives in isolation using Karma and bootstrapping directives for testing DOM logic.

Automating JavaScript testing with Jasmine and Perlnohuhu

This document discusses automating JavaScript testing using Jasmine and Perl. It introduces Test::WWW::Jasmine, a module that takes Jasmine test specs, runs them in a Selenium-controlled browser, and outputs the results in TAP format. This allows running JavaScript tests from Perl similar to unit tests. Examples of Jasmine test specs and TAP output are shown. The document also discusses running the same Jasmine specs locally for development. It acknowledges some limitations but seeks feedback on the new module.

Lessons in Open Source from the MongooseJS ODMValeri Karpov

Valeri Karpov discusses his experience with the Mongoose ODM project for Node.js. He got involved after discovering Mongoose helped reduce his code, and later became the main maintainer. He provides an overview of how Mongoose works through schema validation, syntactic sugar for updates, and hooks/middleware. Recent additions include query middleware and promises support. Lessons learned include being responsive to issues and maintaining a clear vision for an open source project.

Cypress - Best PracticesBrian Mann

Use notes objects in memory and other useful java tips for xpages developmentFrank van der Linden

This document discusses various Java tips and techniques for XPages development, including: 1) Putting Notes documents in memory by wrapping them in a DominoDocument class to avoid memory issues. 2) Using built-in JSON classes to build JSON instead of string concatenation. 3) Creating managed beans to minimize server-side JavaScript and make code more readable. 4) Developing utility classes and extending classes for reusable code.

Protractor survival guideLászló Andrási

This document provides an overview of end-to-end testing with Protractor by summarizing various terminology, demonstrating example tests, and discussing continuous integration practices. It defines key Angular and testing concepts like directives, dependency injection, Jasmine, and WebDriver. Example tests are shown for a calculator app and a mock Facebook app. Continuous integration is discussed in the context of running Protractor tests within Docker containers as part of the software delivery pipeline.

Increase selenium tests stability via java scriptIgor Khrol

The document discusses using JavaScript instead of WebDriver to increase the stability of Selenium tests. UI tests are unstable due to complex, asynchronous modern user interfaces. Many interfaces are based on pre-made components that may not be thoroughly tested individually. These components often have internal APIs that are more reliable than WebDriver for interacting with them. The document provides examples of using JavaScript to synchronize tests and work around issues like multiple frames and custom controls. It emphasizes using JavaScript as a temporary workaround and understanding why standard WebDriver approaches do not work in certain cases.

Protractor trainingSergiy Stotskiy

This document discusses end-to-end testing with Protractor.js. It introduces Protractor and describes how it can be used to test Angular applications directly within browsers using WebDriverJS. It also discusses best practices like using page object patterns to organize tests and hide implementation details. Key aspects covered include setting up tests, writing maintainable page objects, and decomposing pages into reusable sections and fields.

Build automation best practicesCode Mastery

- Build automation helps ensure consistent builds, prevents errors, and speeds up the release process. It helps development teams integrate and deliver changes continuously. - Common tools for build automation include MSBuild, Team Foundation Server, CruiseControl.NET, and Hudson. These tools help with continuous integration (CI), running tests, code analysis, versioning, and deploying builds. - Best practices include CI on every code check-in, running unit tests as part of the build to prevent bugs, and continuously delivering integrated builds to environments for testing. This supports rapid and reliable software delivery.

10 Useful Testing Tools for Open Source Projects @ TuxCon 2015Peter Sabev

More Related Content

What's hot (20)

Performance testing with VSTs on- and off-premisesJeff Bramwell

A tale of 3 databasesChris Skardon

Cypress workshop for JSFoo 2019Biswajit Pattanayak

Automated Testing with Cucumber, PhantomJS and SeleniumDev9Com

Why use Go for web development?Weng Wei

Cypress first impressionsHans Emmel

Cypress vs Selenium WebDriver: Better, Or Just Different? -- by Gil TayarApplitools

Using REST with VSTS and TFSJeff Bramwell

Paint it blue with PowerShellJaap Brasser

LONDON SDET MEETUP - Difference between Selenium and Cypress presentationSriram Angajala

ES2015 / ES6: Basics of modern JavascriptWojciech Dzikowski

Automated testing with CypressYong Shean Chong

Conquering AngularJS LimitationsValeri Karpov

Automating JavaScript testing with Jasmine and Perlnohuhu

Lessons in Open Source from the MongooseJS ODMValeri Karpov

Cypress - Best PracticesBrian Mann

Use notes objects in memory and other useful java tips for xpages developmentFrank van der Linden

Protractor survival guideLászló Andrási

Increase selenium tests stability via java scriptIgor Khrol

Protractor trainingSergiy Stotskiy

Performance testing with VSTs on- and off-premisesJeff Bramwell

A tale of 3 databasesChris Skardon

Cypress workshop for JSFoo 2019Biswajit Pattanayak

Automated Testing with Cucumber, PhantomJS and SeleniumDev9Com

Why use Go for web development?Weng Wei

Cypress first impressionsHans Emmel

Cypress vs Selenium WebDriver: Better, Or Just Different? -- by Gil TayarApplitools

Using REST with VSTS and TFSJeff Bramwell

Paint it blue with PowerShellJaap Brasser

LONDON SDET MEETUP - Difference between Selenium and Cypress presentationSriram Angajala

ES2015 / ES6: Basics of modern JavascriptWojciech Dzikowski

Automated testing with CypressYong Shean Chong

Conquering AngularJS LimitationsValeri Karpov

Automating JavaScript testing with Jasmine and Perlnohuhu

Lessons in Open Source from the MongooseJS ODMValeri Karpov

Cypress - Best PracticesBrian Mann

Use notes objects in memory and other useful java tips for xpages developmentFrank van der Linden

Protractor survival guideLászló Andrási

Increase selenium tests stability via java scriptIgor Khrol

Protractor trainingSergiy Stotskiy

Similar to Unit Testing in JavaScript (20)

Build automation best practicesCode Mastery

10 Useful Testing Tools for Open Source Projects @ TuxCon 2015Peter Sabev

Tools for Software TestingMohammed Moishin

Continuous IntegrationXPDays

Lean-Agile Development with SharePoint - Bill AyersSPC Adriatics

SharePoint gives us a great platform for developing sophisticated intranet portals and collaboration sites and many other workloads. But it can also be a challenge to use modern software development frameworks like Scrum and XP. Wouldn’t it be great if we could get all the benefits of Agile practices – faster development, predictable deliveries, better quality, less stress and happy stakeholders? In this session we will cover the definitions of Lean, Agile, Scrum, Kanban, XP, and TDD. Then we will look at the specific challenges around Agile SharePoint development and some development techniques to overcome these obstacles. This talk covers both project delivery and engineering. We’ll look at unit tests, integration tests, UI tests, continuous integration and, of course, test-driven development (TDD) with practical experiences from real-life Agile SharePoint projects.

Test automation proposalMihai-Cristian Fratila

This document proposes an automated test architecture for the UI Builder application using REST API testing, UI testing, and integration testing. It recommends the Rest Assured library for API testing due to its ability to integrate with Jenkins and remove the need for manual HTTP calls. Protractor is proposed for UI testing as it allows testing Angular applications in JavaScript and integrates well with Selenium. Both test frameworks would be set up with their own Git repositories linked to Jenkins jobs. Integration testing would link the API and UI test repos. The test automation aims to provide faster feedback and reduce regressions as the application grows.

Microsoft power point automation-opensourcetestingtools_matrix-1tactqa

The document provides an overview of open source automation tools that can be used at RSA, including JSYSTEM, Selenium, BadBoy, AutoIT, FIT, FitNesse, and JEMMY. It discusses the challenges of automation, how the tools address issues like time consumption and reliability. It then introduces each tool, covering what it is used for and how it works. The document also discusses how the tools can work together, the automation life cycle at RSA, and provides a demo of some of the tools in action.

Introduction to-automated-testingBestBrains

This document introduces automated testing and provides guidance on how to implement it. It discusses: 1) The benefits of unit tests such as finding bugs quickly, preventing regressions, and improving design. 2) The different types of automated tests including unit, system, and performance tests. Unit tests are fast and robust while system tests test entire systems. 3) How to set up an automated testing environment including tools for different languages, integrating tests into development workflows, and using build servers to run tests on commits.

Introduction to Automated TestingLars Thorup

Jenkins an opensource CICD platform for allssuserd7cedc

Topic production codeKavi Kumar

Jenkins_1679702972.pdfMahmoudAlnmr1

Continuous Integration is a software development practice where developers regularly merge their work into a central repository. When code is committed, an automated build is triggered to check that new code does not break the existing code base. There are typically five stages of adopting Continuous Integration: 1) a few manual commits and builds, 2) nightly automated builds, 3) builds triggered with every commit, 4) code quality metrics added to builds, 5) automated deployment to staging environments. Continuous Integration helps catch bugs early in the development process and ensures code quality.

jenkins.pdfshahidafrith

Continuous Integration is a software development practice where developers regularly merge their work into a central repository. This triggers an automated build and test of the code. If the build fails, developers are immediately notified. There are typically five stages of adopting Continuous Integration - from just committing code occasionally to triggering automated builds and tests with every commit and deploying to production. Jenkins is an open source tool that supports Continuous Integration. It allows developers to easily set up CI/CD pipelines with features like automated testing, code quality reporting, deployment to staging environments and more.

KrishnaToolComparisionPPT.pdfQA or the Highway

The document compares four automation tools: Selenium, Playwright, Cypress, and TestCafe. It provides a detailed comparison matrix covering aspects like supported languages, browsers, speed, APIs, fault tolerance, CI/CD integration, communities, learning curves, and ecosystems. The conclusion is that Playwright is a solid pick for end-to-end testing due to its flexibility, auto waits features, large and active community. Cypress can be easily adopted but has some limitations. While Selenium is widely used, newer tools like Playwright are faster and more reliable. The best tool depends on an application, team and test requirements.

Buildmanagment tools mavenandgradle.pptxpraveena210336

Enter the mind of an Agile DeveloperBSGAfrica

This document discusses BSG's approach to agile software development. It covers their use of agile methodologies like Scrum, test-driven development, behavior-driven development, and pair programming. It also describes their testing strategy, which uses a hybrid of BDD and TDD with a domain specific language. Tests are written at multiple levels, from acceptance to unit, and are run locally and through continuous integration with Jenkins.

Bootstrapping QualityMichael Roufa

Making software development processes to work for youAmbientia

Mikko Paukkila discusses optimizing software development processes to balance bureaucracy and flexibility. He advocates for continuous integration to find errors early and speed up feedback loops. Tools like Git, Jenkins, Gerrit enable CI by automating builds, testing and code reviews. Process optimizations include reducing time from change to product, automating more tests, and ensuring developers have easy environments and fast feedback. The goal is enabling smooth development flows from needs to requirements to changes to high quality products.

Introduction to jenkinsAbe Diaz

Build automation best practicesCode Mastery

10 Useful Testing Tools for Open Source Projects @ TuxCon 2015Peter Sabev

Tools for Software TestingMohammed Moishin

Continuous IntegrationXPDays

Lean-Agile Development with SharePoint - Bill AyersSPC Adriatics

Test automation proposalMihai-Cristian Fratila

Microsoft power point automation-opensourcetestingtools_matrix-1tactqa

Introduction to-automated-testingBestBrains

Introduction to Automated TestingLars Thorup

Jenkins an opensource CICD platform for allssuserd7cedc

Topic production codeKavi Kumar

Jenkins_1679702972.pdfMahmoudAlnmr1

jenkins.pdfshahidafrith

KrishnaToolComparisionPPT.pdfQA or the Highway

Buildmanagment tools mavenandgradle.pptxpraveena210336

Enter the mind of an Agile DeveloperBSGAfrica

Bootstrapping QualityMichael Roufa

Making software development processes to work for youAmbientia

Introduction to jenkinsAbe Diaz

Recently uploaded (20)

The Evolution of Meme Coins A New Era for Digital Currency ppt.pdfAbi john

Big Data Analytics Quick Research Guide by Arthur MorganArthur Morgan

This is a Quick Research Guide (QRG). QRGs include the following: - A brief, high-level overview of the QRG topic. - A milestone timeline for the QRG topic. - Links to various free online resource materials to provide a deeper dive into the QRG topic. - Conclusion and a recommendation for at least two books available in the SJPL system on the QRG topic. QRGs planned for the series: - Artificial Intelligence QRG - Quantum Computing QRG - Big Data Analytics QRG - Spacecraft Guidance, Navigation & Control QRG (coming 2026) - UK Home Computing & The Birth of ARM QRG (coming 2027) Any questions or comments? - Please contact Arthur Morgan at [email protected]. 100% human made.

Salesforce AI Associate 2 of 2 Certification.docxJosé Enrique López Rivera

Splunk Security Update | Public Sector Summit Germany 2025Splunk

Automation Dreamin': Capture User Feedback From AnywhereLynda Kane

AI EngineHost Review: Revolutionary USA Datacenter-Based Hosting with NVIDIA ...SOFTTECHHUB

I started my online journey with several hosting services before stumbling upon Ai EngineHost. At first, the idea of paying one fee and getting lifetime access seemed too good to pass up. The platform is built on reliable US-based servers, ensuring your projects run at high speeds and remain safe. Let me take you step by step through its benefits and features as I explain why this hosting solution is a perfect fit for digital entrepreneurs.

TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...TrustArc

Most consumers believe they’re making informed decisions about their personal data—adjusting privacy settings, blocking trackers, and opting out where they can. However, our new research reveals that while awareness is high, taking meaningful action is still lacking. On the corporate side, many organizations report strong policies for managing third-party data and consumer consent yet fall short when it comes to consistency, accountability and transparency. This session will explore the research findings from TrustArc’s Privacy Pulse Survey, examining consumer attitudes toward personal data collection and practical suggestions for corporate practices around purchasing third-party data. Attendees will learn: - Consumer awareness around data brokers and what consumers are doing to limit data collection - How businesses assess third-party vendors and their consent management operations - Where business preparedness needs improvement - What these trends mean for the future of privacy governance and public trust This discussion is essential for privacy, risk, and compliance professionals who want to ground their strategies in current data and prepare for what’s next in the privacy landscape.

What is Model Context Protocol(MCP) - The new technology for communication bw...Vishnu Singh Chundawat

The MCP (Model Context Protocol) is a framework designed to manage context and interaction within complex systems. This SlideShare presentation will provide a detailed overview of the MCP Model, its applications, and how it plays a crucial role in improving communication and decision-making in distributed systems. We will explore the key concepts behind the protocol, including the importance of context, data management, and how this model enhances system adaptability and responsiveness. Ideal for software developers, system architects, and IT professionals, this presentation will offer valuable insights into how the MCP Model can streamline workflows, improve efficiency, and create more intuitive systems for a wide range of use cases.

#AdminHour presents: Hour of Code2018 slide deck from 12/6/2018Lynda Kane

Asthma presentación en inglés abril 2025 pdfVanessaRaudez

Network Security. Different aspects of Network Security.gregtap1

DevOpsDays Atlanta 2025 - Building 10x Development Organizations.pptxJustin Reock

Building 10x Organizations with Modern Productivity Metrics 10x developers may be a myth, but 10x organizations are very real, as proven by the influential study performed in the 1980s, ‘The Coding War Games.’ Right now, here in early 2025, we seem to be experiencing YAPP (Yet Another Productivity Philosophy), and that philosophy is converging on developer experience. It seems that with every new method we invent for the delivery of products, whether physical or virtual, we reinvent productivity philosophies to go alongside them. But which of these approaches actually work? DORA? SPACE? DevEx? What should we invest in and create urgency behind today, so that we don’t find ourselves having the same discussion again in a decade?

"Rebranding for Growth", Anna VelykoivanenkoFwdays

Image processinglab image processing image processingRaghadHany

Procurement Insights Cost To Value Guide.pptxJon Hansen

Linux Professional Institute LPIC-1 Exam.pdfRHCSA Guru

Learn the Basics of Agile Development: Your Step-by-Step GuideMarcel David

Drupalcamp Finland – Measuring Front-end Energy ConsumptionExove

SAP Modernization: Maximizing the Value of Your SAP S/4HANA Migration.pdfPrecisely

How Can I use the AI Hype in my Business Context?Daniel Lehner

𝙄𝙨 𝘼𝙄 𝙟𝙪𝙨𝙩 𝙝𝙮𝙥𝙚? 𝙊𝙧 𝙞𝙨 𝙞𝙩 𝙩𝙝𝙚 𝙜𝙖𝙢𝙚 𝙘𝙝𝙖𝙣𝙜𝙚𝙧 𝙮𝙤𝙪𝙧 𝙗𝙪𝙨𝙞𝙣𝙚𝙨𝙨 𝙣𝙚𝙚𝙙𝙨? Everyone’s talking about AI but is anyone really using it to create real value? Most companies want to leverage AI. Few know 𝗵𝗼𝘄. ✅ What exactly should you ask to find real AI opportunities? ✅ Which AI techniques actually fit your business? ✅ Is your data even ready for AI? If you’re not sure, you’re not alone. This is a condensed version of the slides I presented at a Linkedin webinar for Tecnovy on 28.04.2025.

The Evolution of Meme Coins A New Era for Digital Currency ppt.pdfAbi john

Big Data Analytics Quick Research Guide by Arthur MorganArthur Morgan

Salesforce AI Associate 2 of 2 Certification.docxJosé Enrique López Rivera

Splunk Security Update | Public Sector Summit Germany 2025Splunk

Automation Dreamin': Capture User Feedback From AnywhereLynda Kane

AI EngineHost Review: Revolutionary USA Datacenter-Based Hosting with NVIDIA ...SOFTTECHHUB

TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...TrustArc

What is Model Context Protocol(MCP) - The new technology for communication bw...Vishnu Singh Chundawat

#AdminHour presents: Hour of Code2018 slide deck from 12/6/2018Lynda Kane

Asthma presentación en inglés abril 2025 pdfVanessaRaudez

Network Security. Different aspects of Network Security.gregtap1

DevOpsDays Atlanta 2025 - Building 10x Development Organizations.pptxJustin Reock

"Rebranding for Growth", Anna VelykoivanenkoFwdays

Image processinglab image processing image processingRaghadHany

Procurement Insights Cost To Value Guide.pptxJon Hansen

Linux Professional Institute LPIC-1 Exam.pdfRHCSA Guru

Learn the Basics of Agile Development: Your Step-by-Step GuideMarcel David

Drupalcamp Finland – Measuring Front-end Energy ConsumptionExove

SAP Modernization: Maximizing the Value of Your SAP S/4HANA Migration.pdfPrecisely

How Can I use the AI Hype in my Business Context?Daniel Lehner

Unit Testing in JavaScript

1. Unit Testing in JavaScript Robert Scaduto | @scardetto Third Wave Technology

2. This talk was sponsored by:

3. About Me • President and CTO of Third Wave Technology • Developing software professionally since 1998 • Maintainer of a handful of open source projects (Crux, physique, build_number) • Musician and aikido practitioner

4. About Third Wave • Boutique consulting ﬁrm specializing in Agile development • Develop custom software for a variety of languages and platforms • Strong focus on Agile practices like Unit Testing and Continuous Integration

5. What is Unit Testing? • The practice of writing code to test individual “units” in isolation. • Originally conceived by Kent Beck in the Smalltalk era. Made popular by JUnit. • One of the pillars of Agile software development.

6. Why Unit Test? • Speeds up the development cycle. • Provides a safety net against enhancing or refactoring existing code. • Provides a living set of documentation about how the code really works. • Helps you write better code.

7. Better Design Through Tests • Get immediate feedback from your API decisions. • Separates interface from implementation concerns. • Promotes the Single Responsibility Principle. • Promotes the YAGNI principle.  (You Ain’t Gonna Need It!)

8. Foundation of Quality • Unit testing is not a replacement for other forms of testing. • However, it does make testing easier by reducing uncertainty in individual units. • When combined with other types of automated and manual testing, you can have a high degree of conﬁdence in the software.

9. Unit Testing Styles • Test Driven Development (TDD) Style typically structured via Arrange, Act, Assert (AAA). • Behavior Driven Development (BDD) Style • Both follow the Four Phase Test Form Setup - Setup the unit under test.  Exercise - Exercise the unit and capture results.  Verify - Verify that the results meet expectations.  Teardown - Cleanup any side effects of the test. 

10. TDD Style The Good  Clearly shows how the API will be used in “real” code. The Caveat  Can lead to bigger tests that are less self documenting.

11. BDD Style The Good  Leads to self-documenting speciﬁcations of units. The Caveat  The test code is spread out and may be harder to grok.

12. JavaScript Unit Testing Frameworks

13. QUnit  http://qunit.js • Developed by the jQuery Team. • Designed for testing in the browser. • However, it can be run from the command line using a headless browser like phantomjs. • Uses a TDD Style. • Simple, ﬂat syntax.

14. Jasmine  http://jasmine.github.io/ • Developed by Pivotal Labs. • Designed to run in a DOM- less environment. • However, it can run in the browser. • BDD Style testing framework heavily inﬂuenced by RSpec. • Lots of built in features including a ﬂuent assertion syntax and spies.

15. Honorable Mentions • Mocha + Chai - http://mochajs.org | http://chaijs.com • BDD framework with simple syntax. • Limited built in features but plays nice with other libraries. • Chai provides a very nice ﬂuent assertions syntax. • Jest - https://facebook.github.io/jest/ • Built on top of the Jasmine framework. • Automatically mocks dependencies. • Runs your tests using a fake DOM which makes it easy to run your tests from the command line.

16. Which One Should You Use? • Do you prefer a BDD or TDD syntax? • Are you testing code that will always run in the browser or will it run standalone? • Are you using an application framework that prefers one over another?

17. Live Demo

18. Thanks for Listening! Tweet me if you have questions:  @scardetto Source code available at: github.com/scardetto/javascript-unit-testing-talk

Unit Testing in JavaScript

Recommended

More Related Content

What's hot (20)

Similar to Unit Testing in JavaScript (20)

Recently uploaded (20)

Unit Testing in JavaScript