Automated testing with Headless Chrome  | Blog  | Chrome for Developers
If you want to run automated tests using Headless Chrome, look no further! This article will get you all set up using Karma as a runner and Mocha+Chai for authoring tests. What are these things? Karma, Mocha, Chai, Headless Chrome, oh my! Karma is a testing harness that works with any of the most popular testing frameworks (Jasmine, Mocha, QUnit). Chai is an assertion library that works with Node
Assert(js) 2019: a conference for JS developers focused on testing
The JS Testing ConferenceAssert(js) is a conference for JavaScript developers focused on testing. From TDD techniques and process to JS testing tools and frameworks, both UI and Node.js. Watch the talks As developers we know that automated testing helps us write better code, build more reliable products, and keep our development velocity consistently high. As JavaScript developers we also know tha
How to set up E2E browser testing for your GitHub project | HackerNoon
Too Long; Didn't ReadNowadays, a vast number of projects, small and large, is developed using <a href="https://nodejs.org/en/" target="_blank">Node.js</a> tools and hosted on <a href="https://github.com/" target="_blank">GitHub</a>. Authors of these projects often face the need to choose a tool for end-to-end testing. When we at DevExpress created <a href="https://devexpress.github.io/testcafe/" t
Testing with Jest Snapshots: First Impressions
Over the past 6 months my team at work has been slowly transitioning a large Backbone application to React. One of the main goals of the transition has been to build out unit tests as we transition components. As part of that we switched from using Karma to using Jest for managing our tests. Our new setup with Jest has several advantages over our previous setup. All Jest tests run through node usi
Jest 16.0: Turbocharged CLI & Community Update · Jest
It's been one month since the last major release and we've made significant improvements to Jest since. In this major release we are updating the snapshot format we are using which will likely require snapshots to be updated when upgrading Jest. We don't make these changes lightly and don't expect this to happen often but we think it is necessary to improve the format from time to time. Upgraded C
Continuous visual integration for Ember
I’m thrilled to announce official support for Ember.js in Percy! We’ve just launched ember-percy: a drop-in client for visual regression testing for Ember apps. Let’s jump right in to a quick example—say I have a bunch of Ember acceptance tests that look something like this: Simple. Just visit the About page, click a team member, and expect that the is-expanded class is now applied. But wait… are
Why I use Tape Instead of Mocha & So Should You
UPDATE: I now use RITEway instead of Tape. It’s wrapper around Tape to make it even simpler to write great unit tests which provide clear bug reports when they fail. See “Rethinking Unit Test Assertions†for more details. TL;DR: Mocha is a $150k Porsche Panamera when the best tool for the job is a $30k Tesla Model 3. Don’t waste your resources on testing bells and whistles. Invest them in creating
Automated testing in Yahoo Mail | Yahoo Engineering
We blogged about the evolution of Yahoo Mail to React + Flux and Node.js. It is important to focus on building a strong foundation when you are building a new platform and having a robust test infrastructure is a big part of the foundation. Yahoo Mail today relies on automated testing on our Continuous Integration pipeline before we deploy changes to production. We run Cucumber and Waitr-Webdriver
Easily testing React components with react-test-tree
While I love React, testing React components leaves a lot to be desired. The TestUtils are useful but don’t have a particularly intuitive API and lead to verbose tests, e.g. We’ve been working on a library at Qubit (We’re hiring) called react-test-tree which removes a lot of the pain with testing React components. It does this by creating an object that represents the given component with an API d
ブラウザã§ãƒ“ジュアルテストをã™ã‚‹reftest-runnerを作ã£ãŸ
æ¦‚è¦ reftest-runnerã¨ã„ã†ãƒ–ラウザã§æ画内容やレイアウトã¨ã„ã£ãŸè¡¨ç¤ºçµæžœã‚’テストã™ã‚‹ãŸã‚ã®ãƒ©ã‚¤ãƒ–ラリを作りã¾ã—ãŸã€‚ è¦ç´ 技術ã¨ã—ã¦ã¯ãƒ–ラウザã€WebDriver APIã€ãƒ¬ãƒ³ãƒ€ãƒªãƒ³ã‚°ã‚ャプãƒãƒ£ã€ç”»åƒDiffã¨ã„ã†æ„Ÿã˜ã§ã™ã€‚ azu/reftest-runner 時間ãŒç„¡ã„人å‘㑠以下ã®ã‚¹ãƒ©ã‚¤ãƒ‰ã«ç°¡å˜ã«reftest-runnerã‚„reftestã¨ã¯ãªã«ã‹ã€ã©ã†ã„ã†ãƒ¦ãƒ¼ã‚¹ã‚±ãƒ¼ã‚¹ãŒã‚ã‚‹ã®ã‹ãŒæ›¸ã„ã¦ã‚ã‚Šã¾ã™ã€‚ reftest-runner-overview.pdf reftestã¨ã¯ reftest(Referrence Test)ã¨ã¯ã€2ã¤ã®HTMLã®è¡¨ç¤ºçµæžœ(スクリーンショット)を比較ã™ã‚‹ã“ã¨ã§è¡¨ç¤ºçµæžœãŒæ„図ã—ãŸã‚‚ã®ã‹ã‚’テストã™ã‚‹æ–¹æ³•ã§ã™ã€‚ 用æ„ã™ã‚‹HTMLã¨ã—ã¦ä»¥ä¸‹ã®2種類を1セットã¨ã—ã¦ç”¨æ„ã—ã¦åˆ©ç”¨ã—ã¾ã™ã€‚ テスト用HTML テストã—ãŸã„機能を使ã£ã¦å®Ÿè£…ã—ãŸHTML リファ
テストã§ããªã„コードをE2Eテストを使ã£ã¦ãƒªãƒ•ã‚¡ã‚¯ã‚¿ãƒªãƒ³ã‚°ã—よã†
ユニットテストãŒã—ã«ãã„状態ã¨ãªã£ã¦ã‚‹ã‚³ãƒ¼ãƒ‰ã‚’Testiumを使ã£ãŸE2Eテストを書ã„ã¦ãƒªãƒ•ã‚¡ã‚¯ã‚¿ãƒªãƒ³ã‚°ã—ã¦ã¿ã‚‹è©±ã§ã™ã€‚ 例ãˆã°ã€ä»¥ä¸‹ã®ã‚ˆã†ãªjQueryã§æ›¸ã„ãŸã‚³ãƒ¼ãƒ‰ã¯å¤–(テストコード)ã‹ã‚‰å–り出ã™ãƒã‚¤ãƒ³ãƒˆãŒãªã„ã®ã§ã€ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã‚’書ãã®ã¯é›£ã—ã„ã¨æ€ã„ã¾ã™ã€‚(ãã‚‚ãã‚‚Viewã®ã‚³ãƒ¼ãƒ‰ãªã®ã§) 特定ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã®å¤‰æ›´ç‚¹ã‚’ç°¡å˜ã«ç¢ºèªã§ãるよã†ã€ 「Aã®åˆ—ã®ãƒ©ã‚¸ã‚ªãƒœã‚¿ãƒ³ã‚’é¸ã¶ã¨åŒã˜è¡Œã‚ˆã‚Šä¸€ã¤ä¸‹ã«ã‚ã‚‹Bã®åˆ—ã®ãƒ©ã‚¸ã‚ªãƒœã‚¿ãƒ³ã‚’自動ã§é¸ã¶ã€ ã¨ã„ã†è£œåŠ©æ©Ÿèƒ½ $(document).ready(function () { // seq: ã‚·ãƒ¼ã‚±ãƒ³ã‚¹ç•ªå· $.each(["new_version", "old_version"], function () { $("input[name='" + this + "']").each(function (idx, elem) { if (idx == 0
ソースコード以外もã¨ã«ã‹ãテストã™ã‚‹ã€‚ã‚‚ã—ãã¯ã‚«ãƒãƒ¬ãƒƒã‚¸ã ã‘ã§ã¯ãƒ€ãƒ¡ã ã¨ã„ã†è©± | ãŠãらãã¯ãã‚Œã•ãˆã‚‚平凡ãªæ—¥ã€…
ã‚ãªãŸã¯ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆã®ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã«å¯¾ã—ã¦é©åˆ‡ã«CIを回ã—ã¦ã„ã‚‹ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“。定期的ã«ã‚³ãƒ¼ãƒ‰ã‚«ãƒãƒ¬ãƒƒã‚¸ã®æ¸¬å®šã‚‚è¡Œã„ã€90%以上もã—ãã¯100%ã®æ•°å—を出ã—ã¦ã„ã‚‹ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“。 ã—ã‹ã—æžœãŸã—ã¦ãã‚Œã§å分ã§ã—ょã†ã‹ï¼Ÿã‚‚ã—ãã¯ã‚³ãƒ¼ãƒ‰ã‚«ãƒãƒ¬ãƒƒã‚¸ã ã‘ã«ã¨ã‚‰ã‚ã‚Œã™ãŽã¦ã„ãªã„ã§ã—ょã†ã‹ï¼Ÿ 監視ã¨ã¯(システムã«å¯¾ã™ã‚‹)継続的ãªãƒ†ã‚¹ãƒˆã§ã‚ã‚‹ã€ã¨ã„ã†ã®ã¯ç†è€…ã®å°Šæ•¬ã™ã‚‹å¥¥ä¸€ç©‚æ°ã®è¨€è‘‰ã§ã™ãŒã€ãã®é€†ã‚‚ã—ã‹ã‚Šã§ 「テストã¨ã¯ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆã«å¯¾ã™ã‚‹ç¶™ç¶šçš„ãªç›£è¦–ã§ã‚る〠ã¨ã„ã†ã“ã¨ã‚‚言ãˆã¾ã™ã€‚ ãã®è¦³ç‚¹ã«ç«‹ã£ã¦ã¿ã‚‹ã¨ã€ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆã®ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ä»¥å¤–ã«ã‚‚テストãŒå¿…è¦ãªã‚‚ã®ãŒãŸãã•ã‚“ã‚ã‚‹ã“ã¨ã«æ°—ã¥ãã§ã—ょã†ã€‚以下ã«å®Ÿéš›ã«ç†è€…ãŒè‡ªåˆ†ã®ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆã®ä¸ã§ã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ä»¥å¤–ã«ãƒ†ã‚¹ãƒˆã‚’書ãã€CIを回ã—ã¦ã„ãŸã‚‚ã®ã‚’挙ã’ã¦ã¿ã¾ã™ã€‚ アプリケーションè¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã®ãƒ†ã‚¹ãƒˆ 開発ä¸ã«æœ¬ç•ªç”¨ã®è¨å®šãƒ•ã‚¡ã‚¤ãƒ«ã‚’使ã†ã“ã¨ã¯ãªã„ãŸã‚ã€æœ¬ç•ªç”¨ã®è¨å®šãƒ•ã‚¡
Writing Testable JavaScript
<p>The engineering culture at Twitter requires tests. Lots of tests. I haven’t had formal experience with JavaScript testing before Twitter, so I’ve been learning a lot as I go. In particular, a number of patterns I used to use, write about, and encourage have turned out to be bad for writing testable code. So I thought it would be worthwhile to share a few of the most important princi
Docker コンテナ㧠MySQL を使ã£ãŸãƒ†ã‚¹ãƒˆã®é«˜é€ŸåŒ– - stfuawsc
全国1å„„2000万㮠Docker ファンã®çš†ã•ã‚“ã“ã‚“ã«ã¡ã¯ã€‚ MySQL ã®èµ·å‹•ãŒã¨ã¦ã¤ã‚‚ãªãé…ã„ã®ã¯æœ‰åãªè©±ã€‚ ã¨ã“ã‚㌠Docker コンテナã®èµ·å‹•ã¯ãªã‹ãªã‹æ—©ã„ã®ã§ã€ MySQL を使ã£ã¦ã„るよã†ãªãƒ†ã‚¹ãƒˆã‚’高速化ã™ã‚‹ã‚±ãƒ¼ã‚¹ã§æœ‰ç”¨æ€§ãŒèªã‚られるã®ã§ã¯ãªã„ã‹ã¨æ€ã£ã¦ PoC を書ã„ã¦ã¿ãŸã€‚ （宣ä¼ï¼‰ã“ã†ã„ã£ãŸè©±ã‚‚å«ã‚㦠YAPC ã§ãƒˆãƒ¼ã‚¯ã—ãŸã„ã®ã§ SNS ç‰ã§ upvote ãŠé¡˜ã„ã—ã¾ã™ï¼š ( ✌'ω')✌ 楽ã—ã„モデル層開発 - YAPC::Asia Tokyo 2014 （宣ä¼ãŠã‚り） MySQL を使ã£ãŸãƒ†ã‚¹ãƒˆ MySQL を使ã£ãŸãƒ†ã‚¹ãƒˆã‚’ã™ã‚‹å ´åˆã€ã ã„ãŸã„次㮠2 パターンã«ãªã‚‹ã€‚ MySQL をテストã®ãŸã³ã«èµ·å‹•ã—ã¦ã‚¯ãƒªãƒ¼ãƒ³ãªçŠ¶æ…‹ã§ä½¿ã† ãƒãƒ¼ã‚«ãƒ«ã«ãƒ‡ãƒ¼ãƒ¢ãƒ³ã¨ã—ã¦èµ·å‹•ã—㟠MySQL ã«æŽ¥ç¶šã—㦠DROP TABLE ã‚„ TRUNCATE ã§ã‚¯ãƒªãƒ¼ãƒ³ãªçŠ¶æ…‹ã«ã—ã¦ä½¿ã† ã ã‘ã©ã€
kintoneã®JSユニットテスト最新事情 - Cybozu Inside Out | サイボウズエンジニアã®ãƒ–ãƒã‚°
ã“ã‚“ã«ã¡ã¯ã€‚kintone開発ãƒãƒ¼ãƒ ã®å¤©é‡Ž (@ama_ch) ã§ã™ã€‚ 最近ã¯JavaScriptã®ãƒ†ã‚¹ãƒˆãƒ„ールãŒè‘—ã—ã進æ©ã—ã€æ—¥ã€…æ–°ã—ã„ツールãŒç™»å ´ã—ã¦ã„ã¾ã™ã€‚kintoneã®é–‹ç™ºã‚‚ã“れらã®ãƒ„ールã«ã‚ˆã£ã¦æ”¯ãˆã‚‰ã‚Œã¦ã„ã¾ã™ã€‚ kintone開発ãƒãƒ¼ãƒ ã§ã¯ã€æ˜¨å¹´æœ«é ƒã‹ã‚‰ãƒ†ã‚¹ãƒˆç’°å¢ƒã®æ”¹å–„ã«å–り組ã¿ã€ãƒ¢ãƒ€ãƒ³ãªãƒ„ールセットã«ä¹—ã‚Šæ›ãˆã¾ã—ãŸã€‚今回ã¯ã€ç¾åœ¨ã®kintoneã®JSユニットテスト環境ã«ã¤ã„ã¦ç´¹ä»‹ã—ã¾ã™ã€‚ kintoneã¨JSユニットテスト æ•°å¹´å‰ã‹ã‚‰ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã¨è‡ªå‹•åŒ–ã®ä»•çµ„ã¿ã¯ã‚ã£ãŸã®ã§ã™ãŒã€ã”ã一部ã®ãƒ¦ãƒ¼ãƒ†ã‚£ãƒªãƒ†ã‚£é–¢æ•°ã«æ›¸ã‹ã‚Œã¦ã„ã‚‹ã®ã¿ã§ã€æ™®æ®µã®é–‹ç™ºã«ã¯æ´»ç”¨ã•ã‚Œã¦ã„ã¾ã›ã‚“ã§ã—ãŸã€‚ ã“ã“1,2å¹´ã»ã©ã§ テストスケルトンを生æˆã™ã‚‹ã‚¸ã‚§ãƒãƒ¬ãƒ¼ã‚¿ã‚¹ã‚¯ãƒªãƒ—トを作る テストã®æ›¸ã方をã¾ã¨ã‚ãŸãƒ‰ã‚ュメントを用æ„ã™ã‚‹ MTGã§ã€Œãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã‚’書ã‹ãªãã¦ã„ã„ã®ã¯å°å¦ç”Ÿã¾ã§ã€ãªã©ã¨ç…½ã‚‹ コードレビュー
ランã‚ング
ãŠçŸ¥ã‚‰ã›
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Snapshot Testing: Use With Care
Domain error
Meteor’s Reactive GraphQL Is Just Awesome - Medium
Airbnb Engineering & Data Science
Registered & Protected by MarkMonitor
{{#tags}}- {{label}}
{{/tags}}