How to write a Cucumber test for Google Maps | Mix & Go
The other day I’ve stumbled upon an interesting challenge. I had to write a feature test for a pin showing up on Google Maps. So basically the feature was supposed to check that when a user visits a particular page, he would be able to see a pin on a Google map. Initially I thought this should be pretty easy to implement, I would just do a find using the right DOM selector and that’s that. So let’
Unit testing Ajax requests with Mocha
Jani Hartikainen Jani Hartikainen has spent over 10 years building web applications. His clients include companies like Nokia and hot super secret startups. When not programming or playing games, Jani writes about JavaScript and high quality code on his site. Ajax requests can easily go wrong. You can't guarantee the connection and the server always work correctly. They are also often used to send
Uncle Bobã®ãƒªãƒˆãƒ«ãƒ»ãƒ¢ãƒƒã‚«ãƒ¼ | POSTD
interface Authorizer { public Boolean authorize(String username, String password); } public class DummyAuthorizer implements Authorizer { public Boolean authorize(String username, String password) { return null; } } ã“ã£ã¡ã¯ã€Œãƒ€ãƒŸãƒ¼ã€ã§ã™ã€‚ ダミーã¯ã©ã†ã„ã£ãŸå ´åˆã«ä½¿ã†ã®ã§ã™ã‹ï¼Ÿ 実際ã«ä½¿ç”¨ã•ã‚Œã‚‹ã‹ã©ã†ã‹ã«é–¢ä¿‚ãªãã€ãƒ—ãƒã‚°ãƒ©ãƒ を進ã‚る時ã§ã™ã€‚ 例ãˆã°ï¼Ÿ テストã§ã™ã。実際ã«ä½¿ã‚れるã“ã¨ã¯ã‚ã‚Šã¾ã›ã‚“ãŒã€ä½•ã‹ã—らã®å¼•æ•°ã‚’渡ã™å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚ 例を見ã›ã¦ã„ãŸã ã‘ã¾ã™ã‹ï¼Ÿ ã¯ã„。 public class System { public System(Authorizer author
Test-induced design damage (DHH)
By David Heinemeier Hansson on April 29, 2014 "Code that's hard to test in isolation is poorly designed", goes a common TDD maxim. Isolation meaning free of dependent context and separated from collaborators, especially "slow" ones like database or file IO. The prevalent definition of "unit" in unit testing (though not everyone agrees with this). This is some times true. Some times finding it diff
ã“ã®ãƒšãƒ¼ã‚¸ã‚’見るã«ã¯ã€ãƒã‚°ã‚¤ãƒ³ã¾ãŸã¯ç™»éŒ²ã—ã¦ãã ã•ã„
Facebookã§æŠ•ç¨¿ã‚„写真ãªã©ã‚’ãƒã‚§ãƒƒã‚¯ã§ãã¾ã™ã€‚
TDD is dead. Long live testing. (DHH)
By David Heinemeier Hansson on April 23, 2014 Test-first fundamentalism is like abstinence-only sex ed: An unrealistic, ineffective morality campaign for self-loathing and shaming. It didn't start out like that. When I first discovered TDD, it was like a courteous invitation to a better world of writing software. A mind hack to get you going with the practice of testing where no testing had happen
Test Rake Tasks Like a BOSS
Testing Rake tasks is one of the most painful things I do as a Ruby developer. Even after extracting all the code out into a separate class (which helps a lot), I still want to make sure I test that the right classes got called correctly with the right arguments. I wanted the subject to be the task, where I could call invoke, check its prerequisites, etc. describe "cron:hourly" do its(:prerequisit
The Most Comprehensive Student Engagement Platform | Campus Labs
OrgSync is now part of Campus Labs Campus Labs Engage is your comprehensive student engagement experience Streamline your processes with Organization Management Effortlessly plan and promote using comprehensive Event Planning Easily monitor event participation with mobile Involvement Tracking Empower students to discover opportunities with Guided Pathways Discover Engage
Testing Rack-based APIs with Cucumber and RSpec
22 January 2014 Yesterday, I mentioned that we’d recently released lookout-rack-test. Today I’m going to talk about how to use it for testing Rack-based JSON APIs. One of the things we like to use this gem for is writing Cucumber scenarios as our API specification, making sure that everybody agrees on what an API looks like before we start implementing. Specifying API behavior with Cucumber Before
Beyond the default Rails environments
Rails ships with a default configuration for the three most common environments that all applications need: test, development, and production. That’s a great start, and for smaller apps, probably enough too. But for Basecamp, we have another three: Beta: For testing feature branches on real production data. We often run feature branches on one of our five beta servers for weeks at the time to eval
Rubyist Magazine - スã¯ã‚¹ãƒšãƒƒã‚¯ã®ã‚¹ ã€ç¬¬ 1 回】 RSpec ã®æ¦‚è¦ã¨ã€RSpec on Rails (モデル編)
『るã³ã¾ã€ã¯ã€Ruby ã«é–¢ã™ã‚‹æŠ€è¡“記事ã¯ã‚‚ã¡ã‚ã‚“ã®ã“ã¨ã€Rubyist ã¸ã®ã‚¤ãƒ³ã‚¿ãƒ“ューやエッセイã€ãã®ä»–ã‚’ãŠå±Šã‘ã™ã‚‹ã‚¦ã‚§ãƒ–雑誌ã§ã™ã€‚ Rubyist Magazine ã«ã¤ã„㦠『Rubyist Magazineã€ã€ç•¥ã—ã¦ã€Žã‚‹ã³ã¾ã€ã¯ã€Rubyist ã® Rubyist ã«ã‚ˆã‚‹ã€Rubyist ã¨ãã†ã§ãªã„人ã®ãŸã‚ã®ã‚¦ã‚§ãƒ–雑誌ã§ã™ã€‚ æœ€æ–°å· Rubyist Magazine 0064 å· ãƒãƒƒã‚¯ãƒŠãƒ³ãƒãƒ¼ Rubyist Magazine 0064 å· Rubyist Magazine 0063 å· Rubyist Magazine 0062 å· Kaigi on Rails ç‰¹é›†å· RubyKaigi Takeout 2020 ç‰¹é›†å· Rubyist Magazine 0061 å· Rubyist Magazine 0060 å· RubyKaigi 2019 ç›´å‰ç‰¹é›†å· Rubyist
最近ã®Ruby on Railsプãƒã‚¸ã‚§ã‚¯ãƒˆã§ä½¿ã£ã¦ã‚‹ã‚‚ã®(2012 winter edition) - Fujimura
最近ã®Ruby on Railsプãƒã‚¸ã‚§ã‚¯ãƒˆã§ä½¿ã£ã¦ã‚‹ã‚‚ã®ãƒ»ã‚„ã£ã¦ã„ã‚‹ã“ã¨ã‚’紹介ã—ã¾ã™ã€‚ rake setupã¡ã‚‡ã£ã¨å‰ã«ã“ã®è¨˜äº‹ã‚’èªã‚“ã§ã‚„ã‚ŠãŸã‹ã£ãŸã‚„ã¤ã§ã™ã€‚ Setting up a new machine for Ruby development by David of 37signals $ git clone git@your-server:you/your-repo.git $ rake setup ã™ã‚‹ã¨ã€é–‹ç™ºã«å¿…è¦ãªç’°å¢ƒãŒã§ãã‚ãŒã‚‹ã¨ã„ã†rake task。今ã„るプãƒã‚¸ã‚§ã‚¯ãƒˆã§ã¯ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã‚’作りãªãŠã—ã¦ã€é–‹ç™ºç’°å¢ƒç”¨ã®ãƒ†ã‚¹ãƒˆãƒ‡ãƒ¼ã‚¿ã‚’投入。テストデータã®ã¾ã¨ã‚ã€å„種URLãªã©ã‚’表示ã—ã¦ã„ã¾ã™ã€‚ 何ã‹ãƒ‡ãƒ¼ã‚¿ãŒå¤‰ã«ãªã£ãŸã¨ã‹ã€ã¾ã£ã•ã‚‰ã®çŠ¶æ…‹ã‹ã‚‰å‹•ã‹ã—ãŸã„ã¨ã‹ã€ãã†ã„ã†æ™‚ã¯ã¨ã«ã‹ãrake setupã™ã‚Œã°OK。 rake setupを一発å©ã‘ã°ã‚¢ãƒ—リãŒãã‚Œãªã‚Šã«å‹•ã状態ã«ãªã‚‹ã€ã£
ウェブエンジニアã®ãŸã‚ã®ã‚ªãƒ³ãƒ©ã‚¤ãƒ³ãƒ„ールã¾ã¨ã‚
The Web engineer's online toolboxã¨ã„ã†ã¾ã¨ã‚記事ãŒä¾¿åˆ©ãã†ã ã£ãŸã®ã§ã€å®Ÿéš›ã«è©¦ã—ã¤ã¤æŠ„訳ã—ã¦ã¿ã¾ã—ãŸã€‚(一部ã®ã‚³ãƒ¡ãƒ³ãƒˆã¨ä½“è£ã¯å¤‰ãˆã¦ã„ã¾ã™ã€‚) 目次 一覧 RequestBin httpリクエストをä¿å˜ã™ã‚‹ã‚¨ãƒ³ãƒ‰ãƒã‚¤ãƒ³ãƒˆã‚’作ã£ã¦ãれる。 Create a RequestBin ã®ãƒœã‚¿ãƒ³ã‚’クリックã™ã‚‹ã¨URLãŒè¡¨ç¤ºã•ã‚Œã‚‹ã®ã§ã€ãã“ã‚’HTTPクライアントã‹ã‚‰ãŸãŸãã¨RequestBinå´ã«ãƒªã‚¯ã‚¨ã‚¹ãƒˆå†…容ãŒè¨˜éŒ²ã•ã‚Œã‚‹ã€‚ ソースも公開ã•ã‚Œã¦ã‚‹ã®ã§ãƒãƒ¼ã‚«ãƒ«ã§ç«‹ã¡ã‚ã’ã‚‹ã“ã¨ã‚‚ã§ãる。 githubã®webhookã®helpã‚‚å‚考ã«ã©ã†ãžã€‚ Hurl httpリクエストを実行ã—ã¦ãれる。パーマリンクも作ã£ã¦ãれるã®ã§ã€POSTリクエストもコピペã§ä»–ã®äººã¨å…±æœ‰ã§ãる。 類似サービス: REST test test , Apigee console httpbin HTTP
detox 㧠tox テストを並列実行ã—よㆠ- forest book
複数㮠Python ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ãƒ„ール㫠tox ãŒã‚ã‚Šã¾ã™ã€‚ tox 㨠pytest 㧠Python 2/3 両対応ã®ãƒ†ã‚¹ãƒˆã‚’実行ã™ã‚‹ - forest book tox ツールãã®ã‚‚ã®ãŒã¨ã¦ã‚‚便利ãªã®ã§ã™ãŒã€ã“ã® tox テストを並列実行ã—ã¦ãれるツールãŒãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã¾ã—ãŸã€‚ detox: Python Package Index 既㫠tox を使ã£ã¦ã„る環境ã§ã‚ã‚Œã°ã€detox をインストールã™ã‚‹ã ã‘ã§è‰¯ã„ã§ã™ã€‚ $ pip install detox 使ã„方㯠tox ã¨å…¨ãåŒã˜ã§ç‰¹åˆ¥ãªè¨å®šã¯ä¸è¦ã§ã™ã€‚tox コマンドを実行ã™ã‚‹ä»£ã‚ã‚Šã« detox コマンドを実行ã—ã¾ã™ã€‚試ã—ã«å®Ÿè¡Œã—ã¦ã¿ã¾ã—ょã†ã€‚ (test)$ detox py26 create: /Users/t2y/work/repo/littlehttpserver/.tox/py26 GLOB s
TDDjangoTutorial
Seriously. This tutorial badly needs updating. Everything is in the book, and much, much more. It's also written in step-by-step tutorial form, it uses the latest django, and it really is free. No catch. Update - this tutorial needs updating, please see the book [update 2013-04-15] Two things: firstly this tutorial needs a re-write. Last time I presented it (at Pycon 2013), I did so following a co
JSã‚‚ã¤ã„ã«æœ€åˆã®è¨€èªžã¨ã—ã¦æŽ¨å¥¨ã§ãるよã†ã«ãªã£ãŸãžï¼ã¨ã„ã†BusterJSã®ç´¹ä»‹
自己紹介 ã©ã‚‚。KAYACã§JS書ã„ã¦ã‚‹@kyo_agoã§ã™ 最近ã¯ã‚¹ãƒžãƒ›ç’°å¢ƒã§è‰²ã€…JS書ã„ã¦ã¾ã™ 今回ã¯ã‹ãªã‚Šå†…容ã«ä¸»è¦³ãŒå…¥ã£ã¦ã¾ã™
In-memory key-value store in C, Go and Python
During my paternity leave, I built an in-memory hashmap in Go, Python, and C to explore implementing an alternative to memcached and to challenge my programming skills across these languages. Each version supports the essential `get` and `set` commands from the memcached protocol, allowing it to work with a memcached client. The code is available on GitHub as Key-Value-Polyglot, and I've actively
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Write Reliable, Asynchronous Integration Tests With Capybara
https://www.rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste.pdf
http://lettuce.it/tutorial/simple.html
{{#tags}}- {{label}}
{{/tags}}