leifcr-capybara-screenshot 1.0.14

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 7514778e4e78652cf17308678a13a90f0cbec61e
+  data.tar.gz: a2ff656c191ce42e534486acf6fd4b569c3d0fdf
+SHA512:
+  metadata.gz: 67060ef950c691b4db170d6db8c5ac4928043cda03fb2340d5daa8dcbc129e51df2d6ca27ac91c4801a2bf83b4aa7f1dad7f7016bb2fd126be6c191924a05f1c
+  data.tar.gz: c62e86fe6ad4e6faa3bd86f55e3735dbb69daef22c6fd62385c9952fd331262b23461ffde6958ce25f00b63b687b6eeae5cfd41bec40be2e8243824e3557ae7f

data/.gitignore

@@ -0,0 +1,9 @@
+*.gem
+.bundle
+Gemfile.lock
+gemfiles/*.lock
+pkg/*
+.rvmrc
+bin
+tmp
+.ruby-version

data/.rspec

@@ -0,0 +1,2 @@
+--color
+--format documentation

data/.travis.yml

@@ -0,0 +1,13 @@
+language: ruby
+script: "rake travis:ci"
+rvm:
+  - 2.0.0
+  - 2.1.10
+  - 2.2.1
+  - 2.3.1
+gemfile:
+  - gemfiles/cucumber.1.3.gemfile
+  - gemfiles/cucumber.2.4.gemfile
+  - gemfiles/latest.gemfile
+  - gemfiles/rspec.3.0.gemfile
+  - gemfiles/spinach.0.8.gemfile

data/Appraisals

@@ -0,0 +1,19 @@
+appraise "rspec.3.0" do
+  gem "rspec", "3.0"
+end
+
+appraise "cucumber.1.3" do
+  gem "cucumber", "~>1.3.0"
+end
+
+appraise "cucumber.2.4" do
+  gem "cucumber", "~>2.4.0"
+end
+
+appraise "spinach.0.8" do
+  gem "spinach", "~>0.8.0"
+end
+
+appraise "latest" do
+  # will get latest versions of all gems
+end

data/CHANGELOG.md

@@ -0,0 +1,256 @@
+15 Sep 2016 - 1.0.13 -> 1.0.14
+
+* CI stable again - dropped CI support for older versions of Ruby and JRuby.  It is just too painful and there is no evidence that our users need this or that Capybara Screenshot is indeed broken.  It is better to have a reliable build system so that PRs can get merged in reliably and easily.
+* Fixed an inconsistency in the use of `save_and_open_page_path`
+* Improved debugging of Aruba tests so that contributors can easily understand why their builds break
+* Path fixes thanks to [Ryan McGarvey](https://github.com/ryanmcgarvey)
+
+23 May 2016 - 1.0.12 -> 1.0.13
+
+* Fixes [mkmf bug 162](https://github.com/mattheworiordan/capybara-screenshot/issues/162) and [mkmf bug 174](https://github.com/mattheworiordan/capybara-screenshot/issues/174)
+* Fix for `Capybara.save_path` method existence assumption
+
+29 March 2016 - 1.0.11 -> 1.0.12
+
+* [Aruba upgrade - passing CI](https://github.com/mattheworiordan/capybara-screenshot/pull/156)
+* [imgcat support](https://github.com/mattheworiordan/capybara-screenshot/pull/153)
+* [Fix for capaybara root when Rails not defined](https://github.com/mattheworiordan/capybara-screenshot/pull/139)
+* [Fix using_session_with_screenshot](https://github.com/mattheworiordan/capybara-screenshot/pull/132)
+* [Skip screenshot on skipped test](https://github.com/mattheworiordan/capybara-screenshot/pull/131)
+* [Don't output screenshot paths if not saved](https://github.com/mattheworiordan/capybara-screenshot/pull/128)
+
+22 July 2015 - 1.0.10 -> 1.0.11
+
+* [Support for Fuubar reporter](https://github.com/mattheworiordan/capybara-screenshot/pull/137)
+
+Thanks to [Kai Schlichting](https://github.com/lacco)
+
+29 June 2015 - 1.0.9 -> 1.0.10
+
+* [Small fix to memoization](https://github.com/mattheworiordan/capybara-screenshot/pull/134) plus [mini refactor](https://github.com/mattheworiordan/capybara-screenshot/commit/1db950bc53c729b26b8881d058a8781d6e7611b8)
+
+Thanks to [Systho](https://github.com/Systho)
+
+6 April 2015 - 1.0.8 -> 1.0.9
+-----------
+
+* [Improved file links within screenshot output](https://github.com/mattheworiordan/capybara-screenshot/pull/123)
+
+Thanks to [Jan Lelis](https://github.com/janlelis)
+
+6 April 2015 - 1.0.7 -> 1.0.8
+-----------
+
+* Less aggressive pruning
+
+9 March 2015 - 1.0.6 -> 1.0.7
+-----------
+
+* Fix capybara-webkit bug, see https://github.com/mattheworiordan/capybara-screenshot/issues/119
+* Fix Travis CI builds in Ruby < 2.1 and added Ruby 2.2 support
+
+8 March 2015 - 1.0.5 -> 1.0.6
+-----------
+
+* Removed dependency on the colored gem
+
+Thanks to [François Bernier](https://github.com/fbernier)
+
+10 Feburary 2015 - 1.04 -> 1.0.5
+-----------
+
+* Added support for appending a random string to the filename
+
+Thanks to [Brad Wedell](https://github.com/streetlogics)
+
+5 January 2015 - 1.0.3 -> 1.0.4
+-----------
+
+* Added support for Poltergeist Billy
+* Don't initialize a new Capybara::Session in after hook
+
+Thanks to [Neodude](https://github.com/neodude) and [Dominik Masur](https://github.com/dmasur)
+
+1 October 2014 - 1.0.2 -> 1.0.3
+-----------
+
+* Added ability to prune screenshots automatically, see https://github.com/mattheworiordan/capybara-screenshot/pull/100
+
+Thanks to [Anton Kolomiychuk](https://github.com/akolomiychuk) for his contribution.
+
+27 September 2014 - 1.0.1 -> 1.0.2
+-----------
+
+* Improved documentation to cover RSpec 3's new approach to using `rails_helper` in place of `spec_helper` for Rails tests
+* Updated documentation to use Ruby formatting in language blocks
+* Removed need to manually `require 'capybara-screenshot'` for RSpec
+
+18 September 2014 - 1.0.0 -> 1.0.1
+-----------
+
+* Hot fix for RSpec version issue that assumed RSpec base library was always available, now uses `RSpec::Core::VERSION`
+* Improve Travis CI performance and stability
+
+18 September 2014 - 0.3.22 -> 1.0.0
+-----------
+
+Because of the broad test coverage now across RSpec, Cucumber, Spinach, Minitest and TestUnit using [Aruba](https://github.com/cucumber/aruba), I feel that this gem is ready for its first major release.  New features and refactoring can now reliably be done  without the fear of regressions.
+
+The major changes in this 1.0 release are:
+
+* Acceptance test coverage for RSpec, Cucumber, Spinach, Minitest and TestUnit
+* Travis CI test coverage across a matrix of old and new versions of the aforementioned testing frameworks, see https://github.com/mattheworiordan/capybara-screenshot/blob/master/.travis.yml
+* Support for RSpec 3 using the custom formatters
+* Support for sessions using `using_session`, see https://github.com/mattheworiordan/capybara-screenshot/pull/91 for more info
+* Support for RSpec DocumentationFormatter
+* Considerable refactoring of the test suite
+
+Special thanks goes to [Andrew Brown](https://github.com/dontfidget) who has contributed a huge amount of the code that has helped enable this Gem to have its stable major version release.
+
+22 July 2014 - 0.3.21 -> 0.3.22
+-----------
+
+Replaced [colorize](https://rubygems.org/gems/colorize) gem with [colored](https://rubygems.org/gems/colored) due to license issue, see https://github.com/mattheworiordan/capybara-screenshot/issues/93.
+
+22 July 2014 - 0.3.20 -> 0.3.21
+-----------
+
+As a result of recent merges and insufficient test coverage, it seems that for test suites other than RSpec the HTML or Image screenshot path was no longer being outputted in the test results.  This has now been fixed, and screenshot output format for RSpec and all other test suites has been standardised.
+
+11 July 2014 - 0.3.19 -> 0.3.20
+-----------
+
+* Added reporters to improve screenshot info in RSpec output
+* Added support for Webkit options such as width and height
+
+Thanks to https://github.com/multiplegeorges and https://github.com/noniq
+
+2 April 2014 - 0.3.18 -> 0.3.19
+-----------
+
+* Added support Spinach, thanks to https://github.com/suchitpuri
+
+2 March 2014 - 0.3.16 -> 0.3.17
+-----------
+
+* Added support for RSpec 3 and cleaned up the logging so there is less noise within the test results when a driver does not support a particular format.
+* Updated Travis to test against Ruby 2.0 and Ruby 2.1
+
+Thanks to https://github.com/noniq
+
+7 January 2014
+-----------
+
+Bug fix for Minitest 5, thanks to https://github.com/cschramm
+
+
+12 September 2013
+-----------
+
+Added support for Test Unit, fixed RSpec deprecation warnings and fixed a dependency issue.
+
+Thanks to:
+
+* https://github.com/budnik
+* https://github.com/jkraemer
+* https://github.com/mariovisic
+
+
+23 July 2013
+-----------
+
+https://github.com/stevenwilkin contributed code to display a warning for [Mechanize](http://mechanize.rubyforge.org/) users.
+
+3 June 2013
+-----------
+
+Dropped Ruby 1.8 support for this Gem because of conflicts with Nokogiri requiring a later version of Ruby.  Instead, there is a new branch https://github.com/mattheworiordan/capybara-screenshot/tree/ruby-1.8-support which can be used if requiring backwards compatabiltiy.
+
+18 Apr 2013
+-----------
+
+Improved documentation, Ruby 1.8.7 support by not allowing Capybara 2.1 to be used, improved Sinatra support.
+RSpec screenshot fix to only screenshot when applicable: https://github.com/mattheworiordan/capybara-screenshot/issues/44
+
+07 Jan 2013
+-----------
+
+Support for Terminus, thanks to https://github.com/jamesotron
+
+27 Dec 2012
+-----------
+
+Previos version bump broke Ruby 1.8.7 support, so Travis CI build added to this Gem and Ruby 1.8.7 support along with JRuby support added.
+
+30 Oct 2012 - Significant version bump 0.3
+-----------
+
+After some consideration, and continued problems with load order of capybara-screenshot in relation to other required gems, the commits from @adzap in the pull request https://github.com/mattheworiordan/capybara-screenshot/pull/29 have been incorporated.  Moving forwards, for every testing framework you use, you will be required to add an explicit require.
+
+
+15 Feb 2012
+-----------
+
+Merged pull request https://github.com/mattheworiordan/capybara-screenshot/pull/14 to limit when capybara-screenshot is fired for RSpec
+
+30 Jan 2012
+-----------
+
+Merged pull request from https://github.com/hlascelles to support Padrino
+
+15 Jan 2012
+-----------
+
+Removed unnecessary and annoying warning that a screen shot cannot be taken.  This message was being shown when RSpec tests were run that did not even invoke Capybara
+
+13 Jan 2012
+-----------
+
+Updated documentation to reflect support for more frameworks, https://github.com/mattheworiordan/capybara-screenshot/issues/9
+
+3 Jan 2012
+----------
+
+Removed Cucumber dependency https://github.com/mattheworiordan/capybara-screenshot/issues/7
+Allowed PNG save path to be configured using capybara.save_and_open_page_path
+
+3 December 2011
+---------------
+
+More robust handling of Minitest for users who have it installed as a dependency
+https://github.com/mattheworiordan/capybara-screenshot/issues/5
+
+
+2 December 2011
+---------------
+
+Fixed bug related to teardown hook not being available in Minitest for some reason (possibly version issues).
+https://github.com/mattheworiordan/capybara-screenshot/issues/5
+
+24 November 2011
+----------------
+
+Added support for:
+
+ * More platforms (Poltergeist)
+ * Removed Rails dependencies (bug)
+ * Added screenshot capability for Selenium
+ * Added support for embed for HTML reports
+
+Thanks to [https://github.com/rb2k](https://github.com/rb2k) for 2 [great commits](https://github.com/mattheworiordan/capybara-screenshot/pull/4)
+
+16 November 2011
+----------------
+
+Added support for Minitest using teardown hooks
+
+
+16 November 2011
+----------------
+
+Added support for RSpec by adding a RSpec configuration after hook and checking if Capybara is being used.
+
+15 November 2011
+----------------
+
+Ensured that tests run other than Cucumber won't fail.  Prior to this Cucumber was required.

data/Gemfile

@@ -0,0 +1,9 @@
+source "http://rubygems.org"
+
+# Specify your gem's dependencies in capybara-screenshot.gemspec
+gemspec
+
+gem 'rack', '~> 1.0'
+gem 'rake', '~> 10.0'
+gem 'appraisal', '~> 2.0'
+gem 'aruba', '~> 0.14.0'

data/LICENSE

@@ -0,0 +1,19 @@
+Copyright (c) 2011 Matthew O'Riordan, inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,315 @@
+capybara-screenshot gem
+=======================
+
+[![Build Status](https://travis-ci.org/mattheworiordan/capybara-screenshot.png)](https://travis-ci.org/mattheworiordan/capybara-screenshot)
+[![Code Climate](https://d3s6mut3hikguw.cloudfront.net/github/mattheworiordan/capybara-screenshot.png)](https://codeclimate.com/github/mattheworiordan/capybara-screenshot)
+[![Gem Version](https://badge.fury.io/rb/capybara-screenshot.svg)](http://badge.fury.io/rb/capybara-screenshot)
+
+#### Capture a screen shot for every test failure automatically!
+
+`capybara-screenshot` used with [Capybara](https://github.com/jnicklas/capybara) and [Cucumber](http://cukes.info/), [Rspec](https://www.relishapp.com/rspec) or [Minitest](https://github.com/seattlerb/minitest), will capture a screen shot for each failure in your test suite.  The HTML for the failed page, and a screenshot image (when using [capybara-webkit](https://github.com/thoughtbot/capybara-webkit), [Selenium](http://seleniumhq.org/) or [poltergeist](https://github.com/jonleighton/poltergeist)) is saved into `$APPLICATION_ROOT/tmp/capybara`.
+
+Having screenshots readily available for each test failure is incredibly helpful when trying to quickly diagnose a problem in your failing steps.  You can view the source code, and have a screen shot of the page (when applicable), at the time of each failure.
+
+_Please note that Ruby 1.9+ is required to use this Gem.  For Ruby 1.8 support, please see the [capybara-screenshot Ruby 1.8 branch](https://github.com/mattheworiordan/capybara-screenshot/tree/ruby-1.8-support)_
+
+Installation
+-----
+
+### Step 1: install the gem
+
+Using Bundler, add the following to your Gemfile
+
+```ruby
+gem 'capybara-screenshot', :group => :test
+```
+
+or install manually using Ruby Gems:
+
+```
+gem install capybara-screenshot
+```
+
+### Step 2: load capybara-screenshot into your tests
+
+#### Cucumber
+
+In env.rb or a support file, please add:
+
+```ruby
+require 'capybara-screenshot/cucumber'
+```
+
+#### RSpec
+
+In rails_helper.rb, spec_helper.rb, or a support file, after the require for 'capybara/rspec', please add:
+
+```ruby
+# remember: you must require 'capybara/rspec' first
+require 'capybara-screenshot/rspec'
+```
+
+*Note: As of RSpec Rails 3.0, it is recommended that all your Rails environment code is loaded into `rails_helper.rb` instead of `spec_helper.rb`, and as such, the capybara-screenshot require should be located in `rails_helper.rb`.  See the [RSpec Rails 3.0 upgrade notes](https://www.relishapp.com/rspec/rspec-rails/v/3-0/docs/upgrade) for more info.*
+
+#### Minitest
+
+Typically in 'test/test_helper.rb', please add:
+
+```ruby
+require 'capybara-screenshot/minitest'
+```
+
+Also, consider adding `include Capybara::Screenshot::MiniTestPlugin` to any test classes that fail. For example, to capture screenshots for all failing integration tests in minitest-rails, try something like:
+
+```ruby
+class ActionDispatch::IntegrationTest
+  include Capybara::Screenshot::MiniTestPlugin
+  # ...
+end
+```
+
+#### Test::Unit
+
+Typically in 'test/test_helper.rb', please add:
+
+```ruby
+require 'capybara-screenshot/testunit'
+```
+
+By default, screenshots will be captured for `Test::Unit` tests in the path 'test/integration'.  You can add additional paths as:
+
+```ruby
+Capybara::Screenshot.testunit_paths << 'test/feature'
+```
+
+
+Manual screenshots
+----
+
+If you require more control, you can generate the screenshot on demand rather than on failure. This is useful
+if the failure occurs at a point where the screen shot is not as useful for debugging a rendering problem. This
+can be more useful if you disable the auto-generate on failure feature with the following config
+
+```ruby
+Capybara::Screenshot.autosave_on_failure = false
+```
+
+Anywhere the Capybara DSL methods (visit, click etc.) are available so too are the screenshot methods.
+
+```ruby
+screenshot_and_save_page
+```
+
+Or for screenshot only, which will automatically open the image.
+
+```ruby
+screenshot_and_open_image
+```
+
+These are just calls on the main library methods.
+
+```ruby
+Capybara::Screenshot.screenshot_and_save_page
+Capybara::Screenshot.screenshot_and_open_image
+```
+
+Better looking HTML screenshots
+-------------------------------
+
+By the default, HTML screenshots will not look very good when opened in a browser.  This happens because the browser can't correctly resolve relative paths like `<link href="/assets/...." />`, which stops CSS, images, etc... from beind loaded.  To get a nicer looking page, configure Capybara with:
+
+```ruby
+Capybara.asset_host = 'http://localhost:3000'
+```
+
+This will cause Capybara to add `<base>http://localhost:3000</base>` to the HTML file, which gives the browser enough information to resolve relative paths.  Next, start a rails server in development mode, on port 3000, to respond to requests for assets:
+
+```bash
+rails s -p 3000
+```
+
+Now when you open the page, you should have something that looks much better.  You can leave this setup in place and use the default HTML pages when you don't care about the presentation, or start the rails server when you need something better looking.  
+
+Driver configuration
+--------------------
+
+The gem supports the default rendering method for Capybara to generate the screenshot, which is:
+
+```ruby
+page.driver.render(path)
+```
+
+There are also some specific driver configurations for Selenium, Webkit, and Poltergeist. See [the definitions here](https://github.com/mattheworiordan/capybara-screenshot/blob/master/lib/capybara-screenshot.rb). The Rack::Test driver, Rails' default, does not allow
+rendering, so it has a driver definition as a noop.
+
+Capybara-webkit defaults to a screenshot size of 1000px by 10px. To specify a custom size, use the following option:
+
+```ruby
+Capybara::Screenshot.webkit_options = { width: 1024, height: 768 }
+```
+
+If a driver is not found the default rendering will be used. If this doesn't work with your driver, then you can
+add another driver configuration like so
+
+```ruby
+# The driver name should match the Capybara driver config name.
+Capybara::Screenshot.register_driver(:exotic_browser_driver) do |driver, path|
+  driver.super_dooper_render(path)
+end
+```
+
+If your driver is based on existing browser driver, like Firefox, instead of `.super_dooper_render` do `driver.browser.save_screenshot path`.
+
+
+Custom screenshot filename
+--------------------------
+
+If you want to control the screenshot filename for a specific test library, to inject the test name into it for example,
+you can override how the basename is generated for the file like so
+
+```ruby
+Capybara::Screenshot.register_filename_prefix_formatter(:rspec) do |example|
+  "screenshot_#{example.description.gsub(' ', '-').gsub(/^.*\/spec\//,'')}"
+end
+```
+
+By default capybara-screenshot will append a timestamp to the basename. If you want to disable this behavior set the following option:
+
+```ruby
+Capybara::Screenshot.append_timestamp = false
+```
+
+
+Custom screenshot directory
+--------------------------
+By default, when running under Rails, Sinatra, and Padrino, screenshots are saved into `$APPLICATION_ROOT/tmp/capybara`. Otherwise, they're saved under `Dir.pwd`.
+If you want to customize the location, override the file path as:
+
+```ruby
+Capybara.save_path = "/file/path"
+```
+
+
+Uploading screenshots to S3
+--------------------------
+You can configure capybara-screenshot to automatically save your screenshots to an AWS S3 bucket.
+
+First, install the `aws-sdk` gem or add it to your Gemfile
+
+```ruby
+gem 'capybara-screenshot', :group => :test
+gem 'aws-sdk', :group => :test
+```
+
+Next, configure capybara-screenshot with your S3 credentials, the bucket to save to, and an optional region (default: `us-east-1`).
+
+```ruby
+Capybara::Screenshot.s3_configuration = {
+  s3_client_credentials: {
+    access_key_id: "my_access_key_id",
+    secret_access_key: "my_secret_access_key",
+    region: "eu-central-1"
+  },
+  bucket_name: "my_screenshots"
+}
+```
+
+
+Pruning old screenshots automatically
+--------------------------
+By default screenshots are saved indefinitely, if you want them to be automatically pruned on a new failure, then you can specify one of the following prune strategies as follows:
+
+```ruby
+# Keep only the screenshots generated from the last failing test suite
+Capybara::Screenshot.prune_strategy = :keep_last_run
+
+# Keep up to the number of screenshots specified in the hash
+Capybara::Screenshot.prune_strategy = { keep: 20 }
+```
+
+Callbacks
+---------
+
+You can hook your own logic into callbacks after the html/screenshot has been saved.
+
+```ruby
+# after Saver#save_html
+Capybara::Screenshot.after_save_html do |path|
+  mail = Mail.new do
+    delivery_method :sendmail
+    from     'capybara-screenshot@example.com'
+    to       'dev@example.com'
+    subject  'Capybara Screenshot'
+    add_file File.read path
+  end
+  mail.delivery_method :sendmail
+  mail.deliver
+end
+
+# after Saver#save_screenshot
+Capybara::Screenshot.after_save_screenshot do |path|
+  # ...
+end
+```
+
+Information about screenshots in RSpec output
+---------------------------------------------
+
+By default, capybara-screenshot extend RSpec’s formatters to include a link to the screenshot and/or saved html page for each failed spec. If you want to disable this feature completely (eg. to avoid problems with CI tools), use:
+
+```ruby
+Capybara::Screenshot::RSpec.add_link_to_screenshot_for_failed_examples = false
+```
+
+It’s also possible to directly embed the screenshot image in the output if you’re using RSpec’s HtmlFormatter:
+
+```ruby
+Capybara::Screenshot::RSpec::REPORTERS["RSpec::Core::Formatters::HtmlFormatter"] = Capybara::Screenshot::RSpec::HtmlEmbedReporter
+```
+
+If you want to further customize the information added to RSpec’s output, just implement your own reporter class and customize `Capybara::Screenshot::RSpec::REPORTERS` accordingly. See [rspec.rb](lib/capybara-screenshot/rspec.rb) for more info.
+
+
+Common problems
+---------------
+
+If you have recently upgraded from v0.2, or you find that screen shots are not automatically being generated, then it's most likely you have not included the necessary `require` statement for your testing framework described above.  As of version 0.3, without the explicit require, Capybara-Screenshot will not automatically take screen shots.  Please re-read the installation instructions above.
+
+Also make sure that you're not calling `Capybara.reset_sessions!` before the screenshot hook runs. For RSpec you want to make sure that you're using `append_after` instead of `after`, for instance:
+
+```ruby
+config.append_after(:each) do
+  Capybara.reset_sessions!
+end
+```
+
+[Raise an issue on the Capybara-Screenshot issue tracker](https://github.com/mattheworiordan/capybara-screenshot/issues) if you are still having problems.
+
+Repository & Contributing to this Gem
+-------------------------------------
+
+#### Bugs
+
+Please raise an issue at [https://github.com/mattheworiordan/capybara-screenshot/issues](https://github.com/mattheworiordan/capybara-screenshot/issues) and ensure you provide sufficient detail to replicate the problem.
+
+#### Contributions
+
+Contributions are welcome.  Please fork this gem, and submit a pull request.  New features must include test coverage and must pass on all versions of the testing frameworks supported.  Run `appraisal` to set up the your Gems. then `appraisal "rake travis:ci"` locally to test your changes against all versions of testing framework gems supported.
+
+#### Rubygems
+
+The gem details on RubyGems.org can be found at [https://rubygems.org/gems/capybara-screenshot](https://rubygems.org/gems/capybara-screenshot)
+
+About
+-----
+
+This gem was written by **Matthew O'Riordan**, with contributions from [many kind people](https://github.com/mattheworiordan/capybara-screenshot/network/members).
+
+ - [http://mattheworiordan.com](http://mattheworiordan.com)
+ - [@mattheworiordan](http://twitter.com/#!/mattheworiordan)
+ - [Linked In](http://www.linkedin.com/in/lemon)
+
+License
+-------
+
+Copyright © 2016 Matthew O'Riordan, inc. It is free software, and may be redistributed under the terms specified in the LICENSE file.