A pattern for Go tests
I used to spend an unreasonable amount of time thinking about how to begin writing a test. A deconstructed ship — Deutsches Technikmuseum, BerlinI googled test patterns in Go.Many people seem to rely on external dependencies for assertions. And in fact, I understand that generic (aha!) functions like isNil(v interface{}) bool can initially bring some speed to the development. But in the long run,
Setting up Angular 2 Testing Environment with Karma and webpack
This article will explain how to create an environment for Angular 2 testing. It uses Karma, webpack and some useful stuffs. And it focuses on simplicity and ease to use. Let’s understand it step by step. 1. Create an Application (no tests)> npm init -y> npm i -S @angular/{core,common,compiler,platform-browser,platform-browser-dynamic} rxjs zone.js core-js> npm i -D typescript webpack@~2.1.0-beta
Three Ways to Test Angular Components
Victor Savkin is a co-founder of nrwl.io, providing Angular consulting to enterprise teams. He was previously on the Angular core team at Google, and built the dependency injection, change detection, forms, and router modules. In this article we will look at three ways to test Angular components: isolated tests, shallow tests, and integration tests. ExamplesFor all the examples we will use a mail
navigator.userAgentをモックしてJSのユニットテストをする - $shibayu36->blog;
JavaScriptのユニットテストでnavigator.userAgentをモックしてテストしたいことがあり、そのようなユーティリティを作ってテストをしてみたのでメモ。 ちなみにいろいろ試した例は https://github.com/shibayu36/javascript-playground/blob/master/es2015-project/test/stubUserAgent.js にあるので、参照してください。 やりたいこと 最近はkarmaやkarma-html2js-preprocessorを利用することで、DOMに依存するテストでもHTMLの断片を用意してユニットテストを行うことができるようになった。TypeScript環境でそのようなテストをする方法については 以前の記事 で紹介した。またES2015版でのテスト環境を作った例は https://github.com
Getting Started with TDD in React - Semaphore Tutorial
Loves JavaScript, Ruby, and IPAs. His blog helps fellow devs level up their Angular, React, and JS skills. Known as @dceddia around the Interwebs. Introduction You’ve spent some time with React, maybe even written a few tests. But you’re not really sure how best to test your components. Where do you start? What exactly do you test? Some React components seem so simple that it’s not even clear whet
一休.comのE2Eテスト事情 ~ギリギリ話せるところまで話します~ /cybozu_ikyu_e2e
一休.com宿泊サイトのE2Eテスト事情をギッリギリまで話しました。このスライドを見た方は一休のエンジニアより一休のE2Eに詳しくなると自負しております。
Testing API Requests From window.fetch
Here’s how to combine window.fetch and sinon stubs to test API requests. This is the second of two parts in a miniseries on functional client-server testing. In the first, we used sinon.js’s fakeServer utility to test an XMLHttpRequest-based client. If you’re in a hurry, skip on over to the demo project on Github; everyone else, read on!_ If we designed a generic API for JavaScript client requests
Enzyme: JavaScript Testing utilities for React
Testing code is crucial for the maintainability of a complex code base, but it is just as important that tests are easy to write, maintain, and understand. Frontend code is no exception to this rule, and behaviors that live in your UI should be tested as well. Almost three months ago, Airbnb open sourced Enzyme, a JavaScript library for testing React components. Since then, the reception has been
Reactjs のテストを ava + jsdom で書いてみる - Qiita
目的 ava + jsdom がどういうものかさらっと触れてみる。 ついでに以前書いた ReactJS + facebook/flux を ES6 の記述でカウンターのサンプル をリファクタしてみた。 ファイル構成 . ├── index.html ├── js │ └── bundle.js ├── package.json ├── src │ ├── app.jsx │ └── app_dispatcher.js └── test ├── hoge.html └── hoge_test.js { "name": "ava_and_jsdom", "version": "1.0.0", "description": "", "main": "index.js", "scripts": { "build": "browserify src/app.jsx -o js/bundl
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Angular2 configuration and Unit testing with Mocha and Chai
GitHub - KDAB/phantomjs-cef: A PhantomJS implementation based on CEF