You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Van Wilson's Site Quidquid latine dictum sit, altum videtur Menu and widgets by Testing your code is one of the most important things that you can do to make yourself a better coder. That’s not just because testing can prevent you from breaking previously-working code when you make changes (also known as regressions), but more importantly, it forces you to write better code in the first place. We
JSer.info #202 - Windows 10ã®æ–°ã—ã„プレビュー版ãŒå…¬é–‹ã•ã‚ŒãŸãŸã‚ã€IEã®ãƒ—レビュー版(IE12ã®ãƒ—レビュー版?)もアップデートã•ã‚Œã¾ã—ãŸã€‚ Living on the Edge – our next step in helping the web just work - IEBlog - Site Home - MSDN Blogs IE11ã«ã¦Edge document modeã¨ã„ã†ã®ãŒå°Žå…¥ã•ã‚Œã¦ã€IEã®ãƒ—レビュー版もã“ã®EdgeモードãŒãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã«ãªã‚Šã¾ã™ã€‚ Edgeモードã§ã¯ã‚¦ã‚§ãƒ–サイトã®X-UA-Compatibleを無視ã—互æ›ãƒ¢ãƒ¼ãƒ‰ã«ã¯ãªã‚‰ãªã„よã†ã«ãªã£ã¦ã„ã¾ã™ã€‚ 逆ã«äº’æ›è¡¨ç¤ºãƒ¢ãƒ¼ãƒ‰ã¨ãªã‚‹ã®ã¯ã‚¤ãƒ³ãƒˆãƒ©ãƒãƒƒãƒˆã€äº’æ›è¡¨ç¤ºãƒªã‚¹ãƒˆã«è¨˜è¼‰ã•ã‚Œã¦ã‚‹ã‚µã‚¤ãƒˆã€ã‚¨ãƒ³ã‚¿ãƒ¼ãƒ—ライズモードã§æŒ‡å®šã—ãŸå ´åˆã®ã¿ã¨ãªã‚Šã¾ã™ã€‚ "Living" Edge document mode,
Why do we hate testing? How do we test JavaScript? How do we test Backbone.JS? (Credits to @searls for slides 6 through 12, used with permission).
Behavior-Driven JavaScript Documentation:(日本語訳) 1.3 Not yet translated below 2.0 2.1 2.2 Edge Jasmine on GitHub
最近ã€ç§ã®ä¸ã§ Backbone.js ã¨å…±ã«æ³¨ç›®ã® Jasmine ã®ãƒ‰ã‚ュメントを和訳ã—ã¾ã—ãŸã€‚ 本家ã®ãƒ‰ã‚ュメントã¯ã“ã¡ã‚‰ã§ã™ã€‚ 和訳ã—ãŸã‚‚ã®ã¯ã“ã¡ã‚‰ã§ã™ã€‚ (もã—ã€è¨³ã§æ€ªã—ã„ã¨ã“ã‚ãŒã‚ã‚Œã°ã”指摘ãã ã•ã„。) http://mitsuruog.github.com/jasmine/ ã¡ãªã¿ã« Jasmine 㯠Javascript ã®ãƒ†ã‚¹ãƒ†ã‚£ãƒ³ã‚°ãƒ•ãƒ¬ãƒ¼ãƒ ワーク㮠1 ã¤ã§ã™ã€‚ ä»–ã®ãƒ•ãƒ¬ãƒ¼ãƒ ワークを満足ã«æ‰±ã£ãŸã“ã¨ãŒãªã„ã®ã§ã€ã‚ã¾ã‚Šå‰ãã†ãªã“ã¨ã¯è¨€ãˆã¾ã›ã‚“ãŒã€ç‰¹å¾´ã¨ã—ã¦æ¬¡ã®ã‚ˆã†ãªã“ã¨ã‚’挙ã’ã¦ãŠãã¾ã™ã€‚ standalone 版(JS ファイル)ãŒã‚ã‚Šã€ãƒ–ラウザã®ã¿ã§ãƒ†ã‚¹ãƒˆå®Ÿè¡Œã¨çµæžœã®ç¢ºèªãŒã§ãる。 テストケースã®ãƒã‚¹ãƒˆãŒå¯èƒ½ã€ï¼ˆJava ã§è¨€ã†ã“ã¨ã®ï¼‰setUpã€tearDown 機能ãŒã‚る。 豊富㪠matcher。 Mock(Spy)ãŒå‰²ã¨ç°¡å˜ã«ä½œã‚Œã‚‹ã€‚ jasmine-jque
Home/Categories/Backbone/Testing Backbone + RequireJS Applications with Jasmine/ In my previous post, I covered the structure of a Backbone.js application using RequireJS. The next thing (or if you are a TDD fan, the first thing) we do is to run some tests on it. According to Coda Hale: Writing tests for your code may not reduce the number of bugs, but it will make fixing the bugs you inevitably f
:JasmineInit ç¾åœ¨ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªã‹ã‚‰ä¸Šã«æ¤œç´¢ã‚’開始ã—〠jsディレクトリãŒå˜åœ¨ã™ã‚‹éšŽå±¤ã«specディレクトリを作æˆã—ã¾ã™ã€‚ specディレクトリ内ã«ã¯jasmineã®standalone版ã«å¿…è¦ãªãƒ•ã‚¡ã‚¤ãƒ«ä¸€å¼ãŒæƒã£ã¦ã„ã¾ã™ :JasmineAdd ClassName specディレクトリ内ã«å¼•æ•°ClassNameã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªã‚’作æˆã—〠index.html, test.jsを生æˆã—ã¾ã™ã€‚ 後述ã™ã‚‹JasmineTemplateã§ç”Ÿæˆã•ã‚Œã‚‹ãƒ•ã‚¡ã‚¤ãƒ«ã®å½¢å¼ã‚’変更å¯èƒ½ã§ã™ã€‚ ClassNameã¯çœç•¥å¯èƒ½ã§ã‚ã‚Šã€çœç•¥ã—ãŸå ´åˆã€ ç¾åœ¨ã®ãƒ•ã‚¡ã‚¤ãƒ«åã‹ã‚‰æ‹¡å¼µåを除ã„ãŸã‚‚ã®ãŒæŒ‡å®šã•ã‚ŒãŸã“ã¨ã«ãªã‚Šã¾ã™ã€‚ ã¾ãŸjsファイル内㫠%JASMINE_TEST_PATH% ã®æ–‡å—列ãŒå˜åœ¨ã—ã¦ã„ãŸå ´åˆã€ãƒ†ã‚¹ãƒˆç”¨jsファイルã¸ã®ãƒ‘スã«ç½®æ›ã•ã‚Œã¾ã™ã€‚ :JasmineTemplate 生æˆã•ã‚ŒãŸspecディレ
Browser-based development can sometimes be a challenge when trying utilize code sharing (http://jamisondance.com/2012/6/21/browser-code-sharing-is-terribad/). Add in module loading, unit testing, and automation...and things get hairy. Until the community comes to a solution, this repo provides a boilerplate for getting up and running with AMD and unit test automation. Most of what is listed here i
目標ã¯grunt + phantomjs + jasmineã®è‡ªå‹•ãƒ†ã‚¹ãƒˆç’°å¢ƒ 先日ã®å¤§ãªã”ã‚„JS Vol.3ã§ã€@_tk84ã•ã‚“ãŒç™ºè¡¨ãªã•ã£ã¦ã„ãŸã€PhantomJSã§è‡ªå‹•ãƒ†ã‚¹ãƒˆã«ã‚¤ãƒ³ã‚¹ãƒ‘イアã•ã‚Œã¦ã€Gruntã§ãã®ã‚ãŸã‚Šã‚’コントãƒãƒ¼ãƒ«ã§ãるよã†ã«ã—ã¾ã—ãŸã€‚ 今回ã®ãƒã‚¤ãƒ³ãƒˆã¯ä¸‹è¨˜ã€‚ .coffeeã‚’ä¿å˜ã—ãŸã‚‰ã€.jsã«è‡ªå‹•ã§ã‚³ãƒ³ãƒ‘イル .jsã®æ›´æ–°ã‚’検知ã—ã¦ã€SpecRunner.htmlã‚’è‡ªå‹•ç”Ÿæˆ ã“ã®ã¨ãæ›´æ–°ã•ã‚ŒãŸ.jsã¨ã€å¯¾ã«ãªã‚‹ãƒ†ã‚¹ãƒˆã‚³ãƒ¼ãƒ‰ã‚’å«ã‚“ã SpecRunner.htmlãŒç”Ÿæˆã•ã‚Œã‚‹ phantomjsã§ã€SpecRunner.htmlを実行ã—ãŸçµæžœã‚’標準出力 出力をgrowlnotifyã«æ¸¡ã—ã¦ãƒ‡ã‚¹ã‚¯ãƒˆãƒƒãƒ—通知 @_tk84ã•ã‚“ã®å…ƒãƒã‚¿ã®ã»ã†ã§ã¯ã€Emacsã¨Rubyãªç’°å¢ƒã§ã—ãŸãŒã€è‡ªåˆ†ã¯ã‚¨ãƒ‡ã‚£ã‚¿ã«ã¯ä¾å˜ã›ãšã€nodeã®å®Ÿè¡Œç’°å¢ƒã ã‘ã§ä½•ã¨ã‹ã§ãるよã†ã«æ§‹æˆã—ã¾ã—ãŸã€‚ aho
本稿ã¯ã€Senchaå…¬å¼ãƒ‰ã‚ュメント㮠Unit Testing with Jasmine ã®ç¿»è¨³ã§ã™ã€‚ I. å°Žå…¥ ã“ã®ãƒãƒ¥ãƒ¼ãƒˆãƒªã‚¢ãƒ«ã§ã¯æ—¢å˜ã®Extアプリケーションをå–り上ã’ã€ãƒ¦ãƒ‹ãƒƒãƒˆãƒ†ã‚¹ãƒˆã™ã‚‹Jasmineアサーションライブラリを紹介ã—ã¾ã™ã€‚ èªè€…ã¯JavaScript, Ext JS 4, MVCアーã‚テクãƒãƒ£åŠã³HTML, CSSã®åŸºæœ¬åŠã³ãƒªã‚½ãƒ¼ã‚¹ã®ä½¿ã„æ–¹ã«ã¤ã„ã¦ç²¾é€šã—ã¦ã„る人ãŒå¯¾è±¡ã§ã™ã€‚ ãªãœãƒ†ã‚¹ãƒˆã™ã‚‹ã®ã‹? アプリケーションをテストã™ã‚‹ã«ã¯å¤šãã®ç†ç”±ãŒã‚ã‚Šã¾ã™ã€‚ テストã¯ã™ã¹ã¦ã®ãƒ¦ãƒ¼ã‚¹ã‚±ãƒ¼ã‚¹ã‚’手動ã§æ¶ˆã—込んã§ã‚†ãã“ã¨ãªãアプリケーションã®æ©Ÿèƒ½æ€§ã‚’検証ã§ãã¾ã™ã€‚ ã•ã‚‰ã«ã€ã‚¢ãƒ—リケーションãŒãƒªãƒ•ã‚¡ã‚¯ã‚¿ãƒªãƒ³ã‚°ã‚„アップデートã•ã‚Œã‚‹æ™‚ã«ã€ テストã¯ãれらã®å¤‰æ›´ãŒã‚·ã‚¹ãƒ†ãƒ ã«å½“ãŸã‚‰ã—ãƒã‚°ã‚’呼ã³è¾¼ã¾ãªã„よã†ã«æ¤œè¨¼ã™ã‚‹ã“ã¨ãŒå‡ºæ¥ã¾ã™ã€‚ II. ã¯ã˜ã‚ã« ã“ã®ãƒãƒ¥ãƒ¼ãƒˆãƒªã‚¢ãƒ«ã§ã¯ExtJSã«ãƒãƒ³ãƒ‰
Context The aim of the article is to describe a good workflow to use when developing web applications. I always read advice on good workflow practices but they are never aggregated together, that’s why I do it right now. UI Driven Development We are going to follow a Behavior Driven Development style. Moreover we are making a web application, so we decide to focus on user: we will start by writing
Update: If you are using Jasmine 2.0 or above, the information here is out of date! Please go to http://jasmine.github.io/2.0/introduction.html#section-Spies instead. Wanna be a spy fast? Well you are in luck! Just kidding! This is actually a cheatsheet for Jasmine Spies. See, while Jasmine itself is very intuitive to use, every time use spies I have to look up the docs. I would blame it on the po
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
処ç†ã‚’実行ä¸ã§ã™
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
{{#tags}}- {{label}}
{{/tags}}