17th of February, 2017 — Lucas Fernandes da Costa at Florianópolis, Brazil🇧🇷 Hi, everyone! After a few weeks without writing about JavaScript, it's about time we talk about it again! This time we're going to talk about errors and stack traces and how to manipulate them. Sometimes people don't pay attention to these details but this knowledge will certainly be useful if you're writing any library
Today we are pleased to ship version 19 of the Jest testing platform. It's the biggest Jest release we have shipped so far and we are quite excited to show you what we've built over the last two months: Immersive Watch Mode We completely rewrote the watch mode to make it instant and more extensible. As a result, the experience of using it really is immersive: tests re-run instantly after a file c
Jest-like snapshot feature for the rest of us + data-driven testing! deprecated please use snap-shot-it - it grabs test instance at runtime, avoiding looking at the source code and getting lost in the transpiled code. snap-shot-jest-test - for testing snap-shot against Jest runner (React + JSX) snap-shot-modules-test - for testing against transpiled ES6 modules snap-shot-vue-test - for testing sna
I really liked snapshot testing as implemented in Jest. Once you have a complex object, compare it with its previous value using expect(value).toMatchSnapshot(). If there is no previous snapshot, it will be saved under the test name. If there is a snapshot file already, the assertion compares the given value with the saved one and throws a well formatted exception if the two values differ. Other f
This release is one of the biggest, most feature-packed release we’ve had in a long time. We have prepared lots of tasty things for you - snapshot testing, magic assert, precompiling test helpers, improvements to Babel transpilation, and more. Our team and contributors have been working hard to deliver all this goodness. We can’t wait to hear your feedback and don’t hesitate to suggest new ideas a
Victor Savkin is a co-founder of nrwl.io. He was previously on the Angular core team at Google, and built the dependency injection, change detection, forms, and router modules. JavaScript applications are full of asynchronous code: we listen to events, debounce them, interact with web workers, send messages to the backend. Testing such code is difficult and, in some cases, hardly possible. In this
この記事は「WACUL Advent Calendar 2016」の23日目です。 今年の10月からWACULでフロントエンドエンジニアをしている@bokuwebと申します。 今回はコンポーネント単位でのvisual regressionテストについて書いてみたいと思います。 概要 単体テスト時にコンポーネントのキャプチャーを取り、差分を取るvisual regressionテストを行うために、karma-nightmareとreg-cliというツールを作りました。まだ実験的ではありますが、それらを用いたテストや作成時に検討したことなどを書いてみます。 そもそもViewのテストどうしてます? フロントエンドやっている方と話すときに、よく、Viewのテストをどこまで、どんなふうにやるか?というざっくりした質問をしてみたりします。「お、その話題ですか!」というリアクションする方もちらほらいて関
Redesigned selector system, built-in assertions and lots of bug fixes! 🚀🚀🚀 Enhancements ⚙ Redesigned selector system. (#798) New selector methods Multiple filtering and hierarchical methods were introduced for selectors. Now you can build flexible, lazily-evaluated functional-style selector chains. Here are some examples: Selector('ul').find('label').parent('div.someClass') Finds all ul elemen
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く