Chrome Web Store
Add new features to your browser and personalize your browsing experience.
Running feature specs with Capybara and Chrome headless | Getaround Tech
Running feature specs with Capybara and Chrome headless July 05, 2017 – Tim Petricola – 2-minute read This article was written before Drivy was acquired by Getaround, and became Getaround EU. Some references to Drivy may therefore remain in the post At Drivy, we’ve been using Capybara and PhantomJS to run our feature specs for years. Even with its issues, PhantomJS is a great way to interact with
GitHub - vcr/vcr: Record your test suite's HTTP interactions and replay them during future test runs for fast, deterministic, accurate tests.
Run this test once, and VCR will record the HTTP request to fixtures/vcr_cassettes/synopsis.yml. Run it again, and VCR will replay the response from iana.org when the HTTP request is made. This test is now fast (no real HTTP requests are made anymore), deterministic (the test will continue to pass, even if you are offline, or iana.org goes down for maintenance) and accurate (the response will cont
Integration Testing Ruby on Rails with Minitest and Capybara - Semaphore
Introduction In this tutorial, we’ll cover how to do integration tests in Rails using Minitest and Capybara. We’ll also cover how integration tests can sometimes serve as a replacement for controller tests. Prerequisites To follow this tutorial, you’ll need to have Ruby installed along with Rails. This tutorial was tested using Ruby version 2.3.3, Rails version 5.0.0.1, Minitest version 5.10.1, an
Capybara: Taming the Hydrochoerus
If you’re a Ruby or Rails developer looking for some advice on how to get better at integration testing: congratulations! You’ve reached the highest level of difficulty in all of the areas of the stack you must conquer to become a great Ruby developer. Integration testing is hard, but it doesn’t have to be. This the subtle of this truth lies in the fact that you must be skilled in both the backend
エンジニア総出でE2Eテストを拡充した話 - てくすた
はじめまして、開発部で技術基盤を担当しているid:Yasaichiです。 乃木坂46の橋本奈々未さんを推しすぎて、デスクに雑誌の切り抜きを飾っています。 本エントリでは、先日行った技術改善の取り組みについて紹介したいと思います。 はじめに PIXTAは、「本体」と呼ばれるモノリシックなRailsアプリケーションと、そこから切りだされた複数のマイクロサービスで構成されています。 現在、これらの中で、Rails 5のリリースによって完全にサポートが切れる4.1系（とそれ以下）で動作しているアプリケーションのバージョンアップを計画しています。 This means 4.1.x and below will essentially be unsupported! Rails 5.0.0.beta1: Action Cable, API mode, Rails command | Riding Ra
Dockerized Rails Capybara tests on top of Selenium – Alfredo Motta
If you use Docker to deploy your Rails application you may want to use the same infrastructure to run your tests. However the setup of your Selenium browser tests is far from obvious with Rails and Docker and may generate some confusion 1 2 3 4 5. The short answer is available in this repository on Github. For the long answer keep reading this blog post for a step by step tutorial! Dockerize Rails
【Rails】RSpecでWeb APIのテストでハマったところ① - Qiita
（2014/12/12 追記） 本稿のアップデート版みたいなのをアップしました→『【Rails】RSpecと三種の神器でらくちんWeb APIテスト - Qiita』 Railsアプリを作るときに，Web APIのテストをしようとしたら命を落としかけたのでいろいろヤバそうなところをメモっておきますφ(｀д´) JSONレスポンスのテストはすべき？ **Everyday Rails - RSpecによるRailsテスト入門**では，Viewのテストは取り扱っていません（理由は2章 Q&Aにて）． でもWeb APIのレスポンスはどうなんだろう？ ということで訳者のひとりである西脇.rbの@jnchitoさんに聞いてみたところ，次のように答えていただきました． @izumin5210 するべきかどうかはケースバイケースです・・・っていうと回答にならないので、yes/noで答えるならyesかな～
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
The musings of bluz71
GitHub - mugi-uno/nezumi: A Chrome Extension that test code generator for Capybara/RSpec.
engine routes for controllers - Controller specs - RSpec Rails - RSpec - Relish
AndroidDriver - selenium - Getting Started With Android Driver - Project Hosting on Google Code