Docker + Rails + System tests with Headless Chrome
Goal Show a simple setup of headless system testing inside a container with Ruby on Rails. There are likely many ways to achieve this goal. However, my aim was to hook into an eventual CI system where the Rails application could be validated by building the docker image and running the test suite. I'll break this down into 3 steps: Create docker image with CentOS and ruby 2.4 Create docker images
èªã¿ã‚„ã™ã„（？）RSpecã®feature testã€ã“ã®ç™ºæƒ³ã¯ãªã‹ã£ãŸã‚・・・ | mah365
Ruby Weekly経由ã§çŸ¥ã£ãŸã®ã§ã™ãŒã€èªã¿ã‚„ã™ã„RSpecã®feature testを書ã方法ã€ã“ã®ç™ºæƒ³ã¯ãªã‹ã£ãŸã‚・・・ã£ã¦æ„Ÿã˜ã§ã™ã€‚ Cucumberã½ãèªã‚るよã†ã«æ›¸ã å…ƒãƒã‚¿ã¯ã“ã®è¨˜äº‹ã€How we write readable feature tests with RSpec。 Cucumberã§ã¯ã“ã‚“ãªæ„Ÿã˜ã®ã‚³ãƒ¼ãƒ‰ã§feature testを表ç¾ã§ãã¦ãƒªãƒ¼ãƒ€ãƒ–ルã ã‘ã©ã€ Feature: Enrolment Scenario: Enrolling in a course Given there is a course And I am logged in as a learner When I enrol on a course Then the course should appear in 'my courses' RSpecã§ã®feature testã¯ã“ã‚“ãªæ„Ÿã˜ã®
Rails Engine Testing with RSpec, Capybara, and FactoryGirl | Viget
UPDATED: I've updated the instructions based on feedback in the comments suggesting the use of the --dummy-path=spec/dummy --skip-test-unit options on the rails plugin new command. Recently, we've been doing a lot more with Rails engines. We've developed a few engines that we've released publicly, and even more that we use privately on applications. We've found it's a good way to organize and shar
Automatically Wait for AJAX with Capybara
We have a race condition between click_link and reload_page. Sometimes the AJAX call will go through before Capybara reloads the page, and sometimes it won’t. This kind of nondeterministic test can be very difficult to debug, so I added a little helper. Capybara’s Little Helper Here’s the helper, via Coderwall: # spec/support/wait_for_ajax.rb module WaitForAjax def wait_for_ajax Timeout.timeout(Ca
How To: Test with Capybara
Acceptance tests for your application may require that a test user be logged in. To do this in your application you can either sign in the user using capybara by visiting the sign in url and entering valid credentials, or you can stub the logged in user. Signing in via Capybara is perhaps the most 'correct' way since we want our tests to be as close to real world conditions as possible, however if
[rspec][ruby][rails] rspec-rails 㨠capybara ã®ã¾ã¨ã‚, [Life] 散髪記録 - HsbtDiary(2012-11-16)
â– [rspec][ruby][rails] rspec-rails 㨠capybara ã®ã¾ã¨ã‚ rspec-rails 㨠capybara をアップデートã—ãŸã‚‰ request spec 㧠click_link ãŒä½¿ãˆãªããªã£ãŸã¨ã„ã†å£°ã‚’隣å¸ã®ã±ãƒ¼ã‚‰ãƒ¼æ°æ–¹é¢ã‹ã‚‰èžã“ãˆã¦ããŸã®ã§ã€ã¡ã‚ƒã‚“ã¨ã‚³ãƒ¼ãƒ‰ã‚’èªã‚“ã§æ–°äºº's ã«å±•é–‹ã—ã¾ã—ãŸã€‚ ã¶ã£ã¡ã‚ƒã‘ spec_helper.rb 㧠include Capybara::DSL ã—ã¦ã—ã¾ãˆã°å‹•ãã‚“ã§ã™ãŒã€rspec ã‚„ capybara ã¨ã„ㆠRails ã§ãƒ†ã‚¹ãƒˆã‚’書ã上ã§ç„¡ãã¦ã¯ãªã‚‰ãªã„ライブラリã®é–“ã§ã©ã®ã‚ˆã†ãªæ–¹æ³•ãŒè‰¯ã„ã¨ã„ã†ã“ã¨ã«ãªã£ãŸã®ã‹ã‚’知るã“ã¨ã¯ Rails Way ã«ä¹—る上ã§å¤§äº‹ãªã“ã¨ã§ã™ã€‚ ãã‚Œãžã‚ŒãŒã©ã®ã‚ˆã†ã«å‹•ã„ã¦ã„ã‚‹ã‹ã‚’ç†è§£ã™ã‚‹ã«ã¯ã¾ãšæœ€åˆã« example group ã¨ã„ã†ã‚‚ã®ã‚’èªã‚€ã¨ç†è§£ãŒé€²ã¿ã¾ã™ã€‚ https:/
![[rspec][ruby][rails] rspec-rails 㨠capybara ã®ã¾ã¨ã‚, [Life] 散髪記録 - HsbtDiary(2012-11-16)](https://cdn-ak-scissors.b.st-hatena.com/image/square/8cab6183abe73ade0ce0a24c302ac36ee5c17b43/height=288;version=1;width=512/https%3A%2F%2Fwww.hsbt.org%2Fdiary%2Ftheme%2Fogimage.png)
File: README — Documentation for jnicklas/capybara (master)
Capybara Capybara helps you test web applications by simulating how a real user would interact with your app. It is agnostic about the driver running your tests and comes with Rack::Test and Selenium support built in. WebKit is supported through an external gem. Support Capybara If you and/or your company find value in Capybara and would like to contribute financially to its ongoing maintenance an
Andy Lindeman – Medium
Tarball is not a dirty wordHow we deploy code swiftly and safely at Salesforce Pardot
twiwt.org - ã“ã®ã‚¦ã‚§ãƒ–サイトã¯è²©å£²ç”¨ã§ã™ï¼Â - twiwt リソースãŠã‚ˆã³æƒ…å ±
ã“ã®ã‚¦ã‚§ãƒ–サイトã¯è²©å£²ç”¨ã§ã™ï¼ twiwt.org ã¯ã€ã‚ãªãŸãŒãŠæŽ¢ã—ã®æƒ…å ±ã®å…¨ã¦ã®æœ€æ–°ã‹ã¤æœ€é©ãªã‚½ãƒ¼ã‚¹ã§ã™ã€‚一般トピックã‹ã‚‰ã“ã“ã‹ã‚‰æ¤œç´¢ã§ãる内容ã¯ã€twiwt.orgãŒå…¨ã¦ã¨ãªã‚Šã¾ã™ã€‚ã‚ãªãŸãŒãŠæŽ¢ã—ã®å†…容ãŒè¦‹ã¤ã‹ã‚‹ã“ã¨ã‚’願ã£ã¦ã„ã¾ã™ï¼
End-to-End Testing with RSpec Integration Tests and Capybara
Stability can become an issue as web applications evolve and grow – integration tests provide a great way to perform end-to-end tests that validate the application is performing as expected. Integration test with RSpec and Capybara When writing integration tests, try to model the test around an actor (user of the system) and the action they are performing. # spec/features/visitor_signs_up_spec.rb
Capybara-webkitã«ã‚ˆã‚‹é«˜é€Ÿã‚¤ãƒ³ãƒ†ã‚°ãƒ¬ãƒ¼ã‚·ãƒ§ãƒ³ãƒ†ã‚¹ãƒˆã¾ã¨ã‚ - === SANDmark 19106 === beginning stress test
ã“ã®ãƒ†ã®ã‚¨ãƒ³ãƒˆãƒªã‚‚何度目ã«ãªã‚‹ã‹ã‚ã‹ã‚Šã¾ã›ã‚“ãŒã€ 実際ã«ä½¿ã£ã¦ãã¦ã€Œã“ã‚Œã ï¼ã€ã¨ã„ã†ç’°å¢ƒãŒã‚る程度確立ã§ããŸæ°—ãŒã™ã‚‹ã®ã§ 一旦ã“ã“ã«ã¾ã¨ã‚ã¦ãŠãã¾ã™ã€‚Ruby1.9.3ã€Rails3.2.2ã§å‹•ä½œç¢ºèªã€‚ å‚考: http://ja.asciicasts.com/episodes/285-spork http://d.hatena.ne.jp/akihito_s/20110701 （今更）RSpec2+Capybara-webkitã§ã‚¤ãƒ³ãƒ†ã‚°ãƒ¬ãƒ¼ã‚·ãƒ§ãƒ³ãƒ†ã‚¹ãƒˆ - === SANDmark 19106 === beginning stress test RSpec2 + Capybara-Webkitã§ã®æ³¨æ„点 - === SANDmark 19106 === beginning stress test 使ã†ã‚‚ã®ãƒªã‚¹ãƒˆ: ライブラリå ã¡ã‚‡ã£ã¨ã—ãŸè§£èª¬ Spork テストã®é«˜é€ŸåŒ–ã‚’ã—ã¦ãれるD
RSpec + capybara-webkit 㧠ヘッドレステスト - LocalScope::
ã“ã“ã—ã°ã‚‰ãã€Rails 3.x ベースã§ç°¡å˜ãªé–‹ç™ºã‚’ã—ã¦ã„ã¾ã™ã€‚ ã©ã†ã›ã‚„ã‚‹ãªã‚‰ã€æ–°ã—ã„ã“ã¨ã‚„らãªã„ã¨ã€ã¨ã„ã†ã“ã¨ã§ã€ä»Šå›žã¯ Behavior Driven 開発をã—よã†ã¨ã—ã¦ã¾ã—ãŸã€‚Cucumberã§ã®ã€æŒ¯ã‚‹èˆžã„ベースã®è¦æ±‚仕様ç–定ã‹ã‚‰ã€RSpecを用ã„㟠Test Driven ãªé–‹ç™ºã¸ã¨è½ã¨ã—込んã§è¡Œã方法ã§ã™ã€‚The RSpec Bookやらã€Continuous Testing: with Ruby, Rails, and JavaScriptã‚’èªã¿ã¤ã¤ã€è‰²ã€…ã¨å®Ÿé¨“ã—ã¦ã¾ã—ãŸã€‚ ãã‚“ãªã‚ã‘ã§ã€ã„ãã¤ã‹Tipsãªã©ã¾ã¨ã‚ãŸã„ã¨æ€ã£ã¦ã„ã‚‹ã®ã§ã™ãŒã€ã¨ã‚Šã‚ãˆãšã€å½¹ã«ç«‹ã¡ãã†ãªã“ã¨ã‚’å…ˆã«æ›¸ã„ã¿ã‚ˆã†ã¨ã„ã†ã“ã¨ã§ã€å‰ç½®ããŒé•·ããªã‚Šã¾ã—ãŸãŒã€capybara-webkitã«ã¤ã„ã¦ã€‚ RSpecã¯ã€ 「プãƒã‚°ãƒ©ãƒ ã®æŒ¯èˆž (behaviour)ã€ã‚’記述ã™ã‚‹ãŸã‚ã®ãƒ‰ãƒ¡ã‚¤ãƒ³ç‰¹åŒ–言語 (DomainS
1
メンテナンス
ãŠçŸ¥ã‚‰ã›
障害
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Support for Rspec / Capybara subdomain integration testing
Improving Rails boot time with Zeus
{{#tags}}- {{label}}
{{/tags}}