Chai
chai-webdriver Provides selenium-webdriver sugar for the Chai assertion library. Allows you to create expressive integration tests: expect('.frequency-field').dom.to.contain.text('One time') expect('.toggle-pane').dom.to.not.be.visible() What sorts of assertions can we make? All assertions start with a Sizzle-compatible css selector, for example: expect('.list') expect('div > h1') expect('a[href=h
How To Use Mocha With Node.js For Test-Driven Development to Avoid Pain and Ship Products Faster – webapplog [tech blog]
Test-driven development (TDD) , as many of you might know, is one of the main, agile development techniques. The genius of TDD lies in increased quality of code, faster development resulting from greater programmer confidence, and improved bug detection (duh!). Historically, web apps have been hard to autotest, and developers relied heavily on manual testing. But, certain parts such as standalone
![How To Use Mocha With Node.js For Test-Driven Development to Avoid Pain and Ship Products Faster – webapplog [tech blog]](https://cdn-ak-scissors.b.st-hatena.com/image/square/785d847986d5495cd76789c5377dde4f5f5b3b1b/height=288;version=1;width=512/https%3A%2F%2Fwebapplog.com%2Fwp-content%2Fuploads%2Fleaf-latter-art-mug-dish-1024x682.jpg)
Karmaの ReferenceError: Can't find variable: chai エラーを解決 - Qiita
フロントエンドエンジニア養成読本のテストランナーの項を写経してたら思いがけないエラーに遭遇したのでその解決方法。 まずは、本の通り、foo.jsとfoo_spec.jsを書いて設定ファイル(karma.conf.js)を作ってからターミナル上でKarmaを起動します。 すると、 PhantomJS 1.9.7 (Mac OS X) ERROR ReferenceError: Can't find variable: chai Chrome 36.0.1985 (Mac OS X 10.9.4) ERROR Uncaught ReferenceError: chai is not defined のエラーが。 そこで、 karma.conf.jsの中を見て、 frameworks: ['mocha'],の部分を frameworks: ['mocha', 'chai'],と書き換えて再度ター
Headless Functional Testing with Selenium and PhantomJS | Envato Tuts+
Let's build a system for performing functional tests on web applications, using Selenium and PhantomJS. The resulting system will allow us to write easy test scenarios in JavaScript, and test those scenarios both in real browsers and a headless simulator. Choosing Components The obvious downside to Selenium is that it requires a full graphical desktop for any and all tests. To begin, we have to ch
Mocha + Chai で CoffeeScript を Grunt で自動テスト - Qiita
module.exports = (grunt) -> grunt.initConfig pkg: grunt.file.readJSON 'package.json' coffeelint: app: files: src: [ 'Gruntfile.coffee' 'src/**/*.coffee' 'test/**/*.coffee' ] simplemocha: all: src: ['test/**/*.coffee'] options: reporter: 'nyan' ui: 'bdd' coffee: compile: files: 'lib/sample.js': 'src/sample.coffee' options: bare: yes watch: scripts: files: [ 'Gruntfile.coffee' 'src/**/*.coffee' 'tes
Expect / Should - Chai
BDD The BDD styles are expect and should. Both use the same chainable language to construct assertions, but they differ in the way an assertion is initially constructed. Check out the Style Guide for a comparison. API Reference Language Chains The following are provided as chainable getters to improve the readability of your assertions. Chains to be been is that which and has have with at of same
Assert - Chai
Assert The assert style is very similar to node.js’ included assert module, with a bit of extra sugar. Of the three style options, assert is the only one that is not chainable. Check out the Style Guide for a comparison. API Reference assert(expression, message) @param { Mixed } expression to test for truthiness @param { String } message to display on error Write your own test expressions. assert(
Assertion Styles - Chai
Assertion Styles This section of the guide introduces you to the three different assertion styles that you may use in your testing environment. Once you have made your selection, it is recommended that you look at the API Documentation for your selected style. Assert View full Assert API The assert style is exposed through assert interface. This provides the classic assert-dot notation, similar to
Introduction - Chai
API Reference The Chai API is broken down by style or task. Assertion Styles The Expect / Should API covers the BDD assertion styles. The Assert API covers the TDD assertion style. Plugins The Plugin API will be of use to anyone interested in building plugins as helpers to DRY up your tests, or for release to the community. Tools The Online Test Suite is a live run of Chai’s test suite. Use it to
Chai
Chai Assertions for Promises Chai as Promised extends Chai with a fluent language for asserting facts about promises. Instead of manually wiring up your expectations to a promise’s fulfilled and rejected handlers: doSomethingAsync().then( function (result) { result.should.equal("foo"); done(); }, function (err) { done(err); } );
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
GitHub - chaijs/type-detect: Improved typeof detection for node.js and the browser.
GitHub - chaijs/chai: BDD / TDD assertion framework for node.js and the browser that can be paired with any testing framework.
GitHub - chaijs/chai: BDD / TDD assertion framework for node.js and the browser that can be paired with any testing framework.
GitHub - chaijs/assertion-error: Error constructor for test and validation frameworks that implements standardized AssertionError specification.
Release 1.9.0 / 2014-01-29 · chaijs/chai
https://github.com/chaijs/chai/blob/master/karma.sauce.js
Problem in PhantomJS · Issue #107 · chaijs/chai
mochaとchaiを使ってcoffeescriptでBDD - Qiita
chai のエラーメッセージの情報を増やす - Qiita
Chai