# Mocha Mocha is a JavaScript test framework for Node.js and web browsers. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How to Stop or Skip Cypress Test Commands DevFeed: [How to Stop or Skip Cypress Test Commands]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-08-07T04:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [Mocha](), [test](), [Code]() Tags: [callback](), [command](), [commands](), [condition](), [cypress](), [object](), [products](), [skip](), [syntax](), [test](), [testing](), [tests]() ### AI overview This tutorial explains three ways to stop or skip Cypress test execution: using Cypress.stop, skipping the current Mocha test, and skipping the remaining commands in the Cypress command queue. It describes the trade-offs of each approach, including whether later tests run and whether completed commands remain visible. ### Source excerpt Let's say you have a long-ish Cypress test and you know a place where it might fail. You want to stop / skip the test commands. ## How To Type Function Mocha Context With Cypress Aliases DevFeed: [How To Type Function Mocha Context With Cypress Aliases]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2025-12-11T05:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [Mocha](), [interfaces](), [test]() Tags: [argument](), [callback](), [code](), [cypress](), [how-to](), [interface](), [interfaces](), [linter](), [products](), [test](), [typescript]() ### AI overview This tutorial explains how to add strong typing for the custom property Cypress aliases place on the Mocha test context. It shows how to extend the relevant callback context type when the bundled type is not directly exposed. ### Source excerpt In Cypress you can save values under aliases which is pretty handy. You can get the aliased value ## Node.js 24.0.0 (Current) DevFeed: [Node.js 24.0.0 (Current)]() Original publisher: [Read original article]() Published: 2025-05-06T14:31:35Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [JavaScript](), [npm](), [V8](), [MSVC](), [HTTP](), [Mocha](), [Security]() Tags: [cross-platform](), [http](), [javascript](), [latest-release](), [msvc](), [node-js](), [npm](), [open-source](), [performance](), [release](), [security](), [tests](), [updates](), [windows]() ### AI overview Node.js 24.0.0 is a Current release that upgrades V8 to 13.6 and npm to 11, removes MSVC support on Windows in favor of ClangCL, improves asynchronous context tracking, expands the Permission Model, enhances the test runner, and updates Undici. It is scheduled to enter long-term support in October. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Node.js March 17th Infrastructure Incident Post-mortem DevFeed: [Node.js March 17th Infrastructure Incident Post-mortem]() Original publisher: [Read original article]() Published: 2023-03-23T20:10:01Z Content type: article Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [Post Mortem](), [incident](), [Cloudflare](), [Mocha](), [nginx](), [Cache](), [Caching](), [migration]() Tags: [caching](), [cloudflare](), [configuration](), [incident](), [migration](), [next-js](), [nginx](), [node-js](), [post-mortem]() ### AI overview This post-mortem explains an infrastructure incident that caused intermittent 404 responses when users downloaded Node.js or accessed parts of nodejs.org. Cloudflare cached incorrect 404 responses, an overloaded origin server returned 404s for valid files, and a build script bug triggered frequent rebuilds and cache purges after the migration to Next.js. The team fixed the configuration and reduced origin load, with the incident fully resolved on March 17. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Add Mocha reporter for Karma unit tests to your Angular CLI project DevFeed: [Add Mocha reporter for Karma unit tests to your Angular CLI project]() Original publisher: [Read original article]() Published: 2018-02-13T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Angular](), [Angular CLI](), [Mocha](), [test](), [npm](), [Yarn](), [Command-line interface]() Tags: [angular](), [cli](), [how-to](), [install](), [npm](), [tests](), [unit-tests](), [video]() ### AI overview This tutorial explains how to replace Karma's default progress reporter with the Karma Mocha reporter in an Angular CLI project. It covers installing the reporter with npm or Yarn, updating the project configuration, and viewing test suite and test case names in the resulting output. ### Source excerpt Lorem ipsum dolor sit amet ## Automatic visual diffing with Puppeteer DevFeed: [Automatic visual diffing with Puppeteer]() Original publisher: [Read original article]() Author: Monica Dinculescu Published: 2018-01-31T00:00:00Z Content type: tutorial Language: en Sources: [Monica Dinculescu]() Topics: [Puppeteer](), [Testing](), [Chrome](), [Chai](), [Mocha](), [npm](), [Selenium](), [Express]() Tags: [chrome](), [code](), [npm](), [selenium](), [testing]() ### AI overview A tutorial on using Puppeteer to take screenshots of web application routes and compare them with golden images for visual regression testing. The approach works with Chrome, supports wide and narrow viewports, and can exercise UI states such as an opened navigation drawer. ### Source excerpt So testing, right? We should do it. The thing is, testing is hard, and good testing is reaaaaaaally hard, and tbh I'm pretty bad at testing. So I end up not testing my apps, and then I feel guilty about it, but I'll stop you now: you can't run guilt on Travis. If this sounds familiar, then this blog post is for you. I did a little song-and-dance that sets up Puppeteer* , takes screenshots of your app (like, all the routes you care about), and then compares them to the "golden" ones. If they match, your test passes! Yes, it only works on Chrome. No, it's not actually unit testing. Yes, it's literally just counting pixels but you know what? It counts them in both a wide and a narrow viewport size and any testing is better than no testing at all; fight me. * Puppeteer is an npm library that lets you control Chrome. You know, like a puppet. In particular, Puppeteer makes it super easy to take screenshots (and click on things in your page). It's like a waaaaaaay less infuriating Selenium, but infinitely harder to spell. This post looks long because I've put all the code I have so that you can copy paste it. Skip to the good part if you already know how to test. Do the npm If you want to test things with Puppeteer, you have to setup a thing for the tests, a server that launches your site, and then Puppeteer to look at that site. I have this in my package.json to wrangle these things: "devDependencies": { "chai": "^4.1.2", "mocha": "^5.0.0", "puppeteer": "^1.0.0", "pixelmatch": "^4.0.2", "polyserve": "^0.23.0" } Explanation: I chose Mocha/Chai for testing because that's what I'm used to. You can literally use any other testing framework you're comfortable with; I don't think it matters. Pixelmatch is the thing that diffs two images and tells you how many pixels they differ by. It's super awesome 🏆. Polyserve is what I use as a local server. You can use Python or Express or whatever you cool kids use. I'll point out in the code where it's Polyserve specific (literally 2 lin ## CICD for Serverless Part 1 - Mocha Endpoint Testing DevFeed: [CICD for Serverless Part 1 - Mocha Endpoint Testing]() Original publisher: [Read original article]() Author: Pete Johnson Published: 2017-02-17T00:00:00Z Content type: tutorial Language: en Sources: [Serverless Blog]() Topics: [Serverless](), [CI/CD](), [Mocha](), [Testing]() Tags: [aws](), [aws-lambda](), [cicd](), [cloud-computing](), [engineering](), [faas](), [function-as-a-service](), [how-to](), [infrastructure-as-code](), [serverless](), [serverless-architecture](), [serverless-framework](), [testing](), [workflow]() ### AI overview Part 1 of a two-part tutorial on implementing a CI/CD workflow for a Serverless project, focusing on Mocha endpoint testing. ### Source excerpt Part 1 of 2 on how to implement a CICD workflow for a Serverless project ## Learning How to Set Up Automated, Cross-browser JavaScript Unit Testing DevFeed: [Learning How to Set Up Automated, Cross-browser JavaScript Unit Testing]() Original publisher: [Read original article]() Published: 2016-07-11T06:48:41Z Content type: tutorial Language: en Sources: [Philip Walton]() Topics: [Testing](), [Unit testing](), [JavaScript](), [Automation](), [Web Development](), [Mocha](), [Node.js](), [Puppeteer]() Tags: [automated](), [browser](), [browsers](), [how-to](), [javascript](), [node-js](), [testing](), [unit-testing](), [web-development]() ### AI overview A tutorial on understanding and building automated cross-browser JavaScript unit testing. It explains the manual testing workflow first, then shows how automation can handle repetitive steps while preserving an understanding of how the process works. ### Source excerpt We all know how important it is to test our code in multiple browsers. And I think for the most part, we in the web development community do a pretty good job at this--at least when first releasing a project.