0.0
No commit activity in last 3 years
No release in over 3 years
There's a lot of open issues
Page Object implementation with ActiveRecord like reading from specialy formatted HTML-page
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

Runtime

 Project Readme

githalytics.com alphaGem VersionCode Climate Build Status Dependency Status Coverage Status Inline docs

#Intro You've probably been there. You're building your killer Web Application. You, being a responsible developer, your code is thoroughly tested. You are using the likes of cucumber and Rspec to do so. Besides your unit-tests, you also have integration tests doing a full stack test. You are using Capybara to read, parse and test the rendered pages. You use all kinds of selectors to select different parts of the page. Slowly but surely your test code becomes less and less readable.

##PageRecord can help. There are a lot of ways you can do this. PageRecord is one of these ways. PageRecord is an ActiveRecord like abstraction for information on the HTML page.

Check the wiki for usage. See the example for more details. Check Changes for (breaking) changes per version.

Installation

Add this line to your application's Gemfile:

gem 'page_record'

And then execute:

$ bundle

Or install it yourself as:

$ gem install page_record

##Documentation Look at the yard documentation for details.

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request