ドットインストール代表のライフハックブログ
I love testing and I love small easily testable modules in Node. Recently I had to build a library module that interacts with some web services via HTTP. To test this module as it was would mean that I would have to have a sandboxed account on the other end. I also would have to have setup and teardown routines that would reset the sandbox to a known state, etc, etc. What I really wanted for the u
Install (requires NPM): npm install soda Create `mytest.js`: var soda = require('soda'); var browser = soda.createSauceClient({ 'url': 'http://yourwebsite/' , 'username': '' , 'access-key': '' , 'os': 'Windows 2003' , 'browser': 'googlechrome' , 'max-duration': 300 }); browser .chain .session() .setTimeout(5000) .open('/') .waitForElementPresent('username') .type('username', 'invalid') .type('pass
Expresso 0.9.0 Expresso is a JavaScript TDD framework written for nodejs. Expresso is extremely fast, and is packed with features such as additional assertion methods, code coverage reporting, CI support, and more. Featureslight-weightintuitive async supportintuitive test runner executabletest coverage support and reporting via node-jscoverageuses and extends the core assert moduleassert.eql() ali
Asynchronous behaviour driven development for Node. There are two reasons why we might want asynchronous testing. The first, and obvious reason is that node.js is asynchronous, and therefore our tests should be. The second reason is to make tests which target I/O run much faster, by running them concurrently. Write some vows, execute them: $ vows test/* --spec Get the report, make sure you kept yo
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く