cello 0.0.12 → 0.0.16

data/.gitignore

@@ -1,3 +1,5 @@
 *.sw*
+*.gem
 *.lock
 screenshot.png
+coverage/*

data/Gemfile

@@ -1,8 +1,11 @@
 source "http://rubygems.org"
 
-gem 'selenium-webdriver'
+gem 'pry'
+gem 'simplecov'
+gem 'watir-webdriver'
 gem 'cucumber'
 gem 'rake'
-
+gem 'headless'
+gem 'rspec'
 
 gemspec

data/README.md

@@ -1,33 +1,35 @@
 CELLO
 =====
 
+[![Build Status](https://secure.travis-ci.org/camiloribeiro/cello.png)](http://travis-ci.org/camiloribeiro/cello])
+
 What?
 -----
-Cello is a Framework for automated UI tests based on Watir-Webdriver and Selenium-Webdriver in ruby, extended by metaprogramming and magic to implement something based on page object model and describe the behaviour with cucumber.
+Cello is a framework for automated web UI tests based on Watir-Webdriver. It uses the [Cucumber](http://cukes.info/) readable behavior specification language to specify tests based on the Page Object Model. It is written in Ruby, and extended by metaprogramming and magic.
 
-This framework isn't realeased or stable yet, but the concept is already done. The concept consists in a way to implement tests faster like when we record using tools like seleium IDE, but using magic and metaprogramming instead all that terrible bullshit code generated by those tools.
+This framework isn't officially released or stable yet, but the concept is already done. It consists in a way to implement tests fast, like when we record using tools like the Seleium IDE, but without all the terrible code generated by those tools.
 
-What a funny name :-p
+What a funny name :-p!
 ----------------------
-The name is cello, not just because I love it, but because as a music composition are steps that, when syncronized guide the musician to play wonderful songs, the acceptance automated tests are steps that when syncronized guide the developer to keep coding wonderfull peaces of business value.
+The name is Cello not just because I play and love it, but because as a music composition consists of steps that when synchronized guide the musician to play wonderful songs, the acceptance automated tests are steps that when synchronized guide the developer to keep coding wonderful pieces of business value.
+
 
 What is the idea?
 -----------------
-The core idea is based on two tecniques and a lots of ideas:
-*The first one is the Page-Object Model that provide a way to make tests more maintainable
-*The second one is the record but not replay that allows people without programming skills generate automated regression tests in a easier and faster way
+The core idea is based on two techniques and lots of ideas:
 
-No one technique is required, but the first one is really recommended
+* The first one is the Page-Object Model, that provides a way to make tests more maintainable.
+* The second one is the "record but not replay", that allows people without programming skills generate automated regression tests in an easier and faster way.
 
-We still have to much work to do ( as you can see in right bellow in this document), but, if you want, you can fork it and have fun!
+No one technique is mandatory, but the first one is strongly recommended.
 
-It's STRONGLY recommended do not use it for comercial projects, because it will change too much and we never tested it in a real project. We recomend you use it to emulate a project and, if possible, return us you example to be added on our library.
+We still have to much work to do (as you can see further below, in this very document), but, if you want, you can fork it and have fun!
 
+It's STRONGLY recommended to not use it for commercial projects just yet, because it will change too much and we never tested it in a real project. We recommend you use it to emulate a project and, if possible, send us your example to be added on our library.
 
-The way we choose to test our framework was . . . writing tests with it! This way we keep a stable version of it, we can overcome the limitations writing new features to cover the tests that wasn't working and build a library of examples to future users. 
-
-So, that way, if you are not a developer but a awesome QA with a little experience with code, you can help us practicing this tool in a little bit in your free time, and we will try make you happy fixing the bugs and implementing the new features you find during the time you'll spend writing tests. This examples will be storage on our repository with your name, mail, blog link or what you want.
+The way we chose to test our framework was... writing tests with it! This way we keep a stable version of it, and we can overcome the limitations of writing new features to cover the tests that weren't working and build a library of examples to future users. 
 
+So, this way, if you are not a developer, but an awesome QA with a little experience with code, you can help us by exploring this tool a little bit in your free time, and we will try make you happy fixing the bugs and implementing the new features you end up suggesting by writing great tests. These examples will be stored on our repository with your author credentials.
 
 
 Instructions
@@ -40,9 +42,10 @@ To develop `cello`, you are going to need [Bundler][1]
     $ git clone git@github.com:camiloribeiro/cello.git
     $ cd cello
     $ bundle install
-    $ rake run
+    $ rake
+
+The last step is launching the regression tests and all should be green.
 
-The last step launch the regression tests and it should be everything green
 If you have any problems, please let us know.
 
 [1]: http://gembundler.com
@@ -50,40 +53,42 @@ If you have any problems, please let us know.
 Using
 -----
 
-To use it you will need the developing env described in this document
-Then you can follow the example bugbang inside the directory cello/example
+To use it you will need the development environment described in this document. Then you can follow the `bugbang` example inside the `cello/example` directory.
+
+Soon I will provide more use descriptions :)
+
+FEATURED
+========
+
+- X-Platform: It does not matter if you are a Apple fan, A linux hard user or a windows geek. You can use it ;)
+
+- X-Browser Running: You can create different browsers to different tests, and can use it in parallel
+
+- Agnostic approach: You can choose between classical script, BDD, Object Oriented tests and hybrid tests to structure your tests. Also there is not a particular BDD tool to use it.
+
+- Restricted and unrestricted interface: By nature, you can do only do what an user can do, example: It is not possível to access non visible/enabled elements. Also can use the common Watir common interface to access them if necessary, therefore, it is not recommended.
+
+- Easy DSL: You will be able to create your DSL soon, but for while you have a simple DSL to work with.
+
+- Rspec asserssion: Even without a mandatody Rspec approach, you can use the 'should/should_not' assertions in your testings
 
-Soon I will provide a new use description :) 
 
 ROADMAP
 =======
 
-0.5 Partitura
--------------
--DSL: Based framework that consists on a metaprogramming way to create customized test methods to each single project using a new DSL to provide test methods in execution time using only one line description for each element.
--Selenium: Change watir-webdriver to selenium
--Cukes: Cucumber by nature
+- DSL: Based framework that consists on a metaprogramming way to create customized test methods to each single project using a new DSL to provide test methods in execution time using only one line description for each element.
+
+- Selenium: Change Watir-webdriver to Selenium
 
-1.0 Tabulatura
---------------
--Gem: Creat the cello gem that will:
-  *Create project 
-  *Get a page and write the elements in the page
--No Browser: Headless browser execution
+- Gem: Create the cello gem that will:
 
-1.5 Ocarine
------------
--DDT: Data driven testing by nature
--No Cukes: Provide a way to work with other BDD tools
--XTest: X-browser Testing by nature
+  * Create project 
 
-2.0 Orquestra
--------------
--No Selenium: Provide a way to choose at least Watir or selenium
--Scala: Create a copu for scala and java users
+  * Get a page and write the elements in the page
 
+- DDT: Data driven testing by nature
 
-LICENCE
+LICENSE
 =======
 
 Copyright 2012 Camilo Ribeiro cribeiro@thoughtworks.com

data/Rakefile

@@ -1,4 +1,9 @@
 require "cucumber/rake/task"
+require 'rspec/core/rake_task'
+
+task :default => [:spec,:run]
+
+Spec::Rake::SpecTask.new(:spec)
 
 Cucumber::Rake::Task.new(:run) do |task|
   task.cucumber_opts = ["-t","~@pending","features --format pretty"]

data/cello.gemspec

@@ -20,10 +20,15 @@ Gem::Specification.new do |s|
 
   s.require_paths = ["lib"]
 
+  s.add_development_dependency 'simplecov'
+  s.add_development_dependency 'pry'
   s.add_development_dependency 'cucumber'
+  s.add_development_dependency 'watir-webdriver'
   s.add_development_dependency 'rake'
+  s.add_development_dependency 'rspec'
+  s.add_development_dependency 'headless'
 
   s.add_dependency 'cucumber'
+  s.add_dependency 'rspec'
   s.add_dependency 'watir-webdriver'
-  s.add_dependency 'selenium-webdriver'
 end

data/examples/bugbang/pages/home.rb

@@ -1,4 +1,4 @@
-require File.join(File.dirname(__FILE__), '../../../lib/cello/page')
+require File.join(File.dirname(__FILE__), '../../../lib/cello/structure/page')
 
 module BugBang
   class HomePage < Cello::Structure::Page

data/features/access_element.feature

@@ -2,21 +2,21 @@ Feature: Access elements
   As developer
   I want access elements in diferent ways
 
-  Scenario: Write in a element text field sing id 
+  Scenario: Write in a element textfield using id 
     Given I am on a page that has a textfield
     Then I should be able to write "Test" in a element using id
 
-  Scenario: Write in a element text field sing name 
+  Scenario: Write in a element textfield using name 
     Given I am on a page that has a textfield
     Then I should be able to write "Test" in a element using name
   
   @pending
-  Scenario: Write in a element text field sing xpath
+  Scenario: Write in a element textfield using xpath
     Given I am on a page that has a textfield
     Then I should be able to write "Test" in a element using xpath
 
   @pending
-  Scenario: Write in a element text field sing label related
+  Scenario: Write in a element textfield using label related
     Given I am on a page that has a textfield
     Then I should be able to write "Test" in a element using label
   

data/features/browser.feature

@@ -0,0 +1,25 @@
+Feature: Browser
+  As a developer
+  I want use a browser in different contexts
+
+  Scenario: Get a context
+    Given I have a browser with no context (blank page)
+    When I ask for the context inputs
+    And and I ask to visit the page
+    Then I should see the page inputs
+
+  Scenario: Fill a textfield on a context
+    Given I am in the inputs context
+    When I ask for fill the textfield
+    Then I should see the filled textfield
+    And I should be able to close the browser
+
+  Scenario: Pass by two different contexts
+    Given I am in the inputs context
+    When I ask for fill the textfield
+    Then I should see the filled textfield
+    When I click on the simple page link 
+    And I ask to use the simple page context
+    Then I should fail when try access the old textfield
+    And I should be able to verify the text on the new textfield
+    And I should be able to close the browser

data/features/button.feature

@@ -0,0 +1,4 @@
+Feature: Button
+  As developer
+  I want use button with different behaviours
+

data/features/dsl.feature

@@ -0,0 +1,21 @@
+Feature: DSL
+  As developer
+  I want to create my own interface to use this framework
+    
+  @pending
+  Scenario: Keep the common DSL
+    Given I have the common dls defined
+    When I invoque a page that has all html elements
+    Then I should be able to run the follow methods:
+      | method            | 
+      |                   |
+      
+  @pending
+  Scenario: Defining new DS
+    Given I have the follow dls defined on dls file:
+      | method            | new_name             |
+      |                   |                      |
+    When I invoque a page that has all html elements
+    Then I should be able to run the follow methods:
+      | method            | 
+      |                   |

data/features/element.feature

@@ -2,15 +2,13 @@ Feature: Element
   As a developer
   I want use element to run my tests
 
-  @pending
-  Scenario: Use as element and send a native watir/selenium method
-  
   Scenario: Click at the element
     Given I am on a page that has a element
     And that element is named as: 
       | checkbox      |
       | text_field    |
       | textarea      |
+      | radios         |
     Then I want click on this element
     
   Scenario: Know if the element is visible
@@ -19,6 +17,7 @@ Feature: Element
       | checkbox      |
       | text_field    |
       | textarea      |
+      | radios         |
     Then I want know if this element is visible
 
   Scenario: Know if the element is enable
@@ -27,6 +26,7 @@ Feature: Element
       | checkbox      |
       | text_field    |
       | textarea      |
+      | radios         |
     Then I want know if this element is enable
 
   Scenario: Know if the element exists
@@ -35,14 +35,16 @@ Feature: Element
       | checkbox      |
       | text_field    |
       | textarea      |
+      | radios         |
     Then I want know if this element exists
 
-  Scenario: Riht click at the element
+  Scenario: Right click at the element
     Given I am on a page that has a element
     And that element is named as: 
       | checkbox      |
       | text_field    |
       | textarea      |
+      | radios         |
     Then I shoud be able to click with the right button in this element
 
   @pending
@@ -52,6 +54,7 @@ Feature: Element
       | checkbox      |
       | text_field    |
       | textarea      |
+      | radios         |
 
   @pending
   Scenario: Wait until the element is present
@@ -60,6 +63,7 @@ Feature: Element
       | checkbox      |
       | text_field    |
       | textarea      |
+      | radios         |
 
   @pending
   Scenario: get the location of it
@@ -68,4 +72,5 @@ Feature: Element
       | checkbox      |
       | text_field    |
       | textarea      |
+      | radios         |
     Then I should be able to get the location of it

data/features/get_html_attributes.feature

@@ -0,0 +1,30 @@
+Feature: Getting HTML Atributes
+  As Developer
+  I want to get HTML atributs from elements
+
+  Scenario: Get the value of a html element
+    Given I am on a page that has a element
+    And the textfield has the value "text value"
+    When I ask for the "value" of it element
+    Then I should see the value of it
+
+  @pending
+  Scenario: Get the text of a html element
+    Given I am on a page that has a element
+    And the textfield has the text "text text"
+    When I ask for the "text" of it element
+    Then I should see the text of it
+
+  @pending
+  Scenario: Get the class of a html element
+    Given I am on a page that has a element
+    And the textfield has the class "text_class"
+    When I ask for the "class" of it element
+    Then I should see the class of it
+
+  @pending
+  Scenario: Get the tilte of a html element 
+    Given I am on a page that has a element
+    And the textfield has the title "text title"
+    When I ask for the "title" of it element
+    Then I should see the title of it

data/features/pages/firefox.rb

@@ -0,0 +1,12 @@
+require File.join(File.dirname(__FILE__), '../../lib/cello')
+
+module StaticPages
+  module Site
+    class Firefox < Cello::Structure::Browser
+
+      def initialize
+        super :firefox
+      end
+    end
+  end
+end

data/features/pages/input_fields.rb

@@ -1,4 +1,4 @@
-require File.join(File.dirname(__FILE__), '../../lib/cello/page')
+require File.join(File.dirname(__FILE__), '../../lib/cello')
 
 module StaticPages
   module Site
@@ -8,10 +8,16 @@ module StaticPages
       element :text_fieldxpath,  :text_field, :xpah, '//*[@id="text1"]'
       element :checkbox,  :checkbox, :id => 'check1'
       element :textarea,  :textarea, :id => 'area1'
+      element :radios,  :radios, :name => 'items'
+      element :select,  :select, :id => 'select1'
+      element :link,  :link, :id => 'link1'
+      
+      def get_url
+        'file://' + File.dirname(__FILE__) + '/../site/inputs.html'
+      end
 
-      @@url = 'file://' + File.dirname(__FILE__) + '/../site/inputs.html'
-      def initialize
-        super(@@url)
+      def initialize(teste)
+        super(teste)
       end
     end
   end

data/features/pages/response_page.rb

@@ -0,0 +1,17 @@
+require File.join(File.dirname(__FILE__), '../../lib/cello')
+
+module StaticPages
+  module Site
+    class ResponsePage < Cello::Structure::Page
+      element :text,  :text_field, :id => 'new_element'
+      
+      def get_url
+        'file://' + File.dirname(__FILE__) + '/../site/read_page.html'
+      end
+
+      def initialize(teste)
+        super(teste)
+      end
+    end
+  end
+end

data/features/radio.feature

@@ -0,0 +1,85 @@
+Feature: Radio
+  As a develper
+  I want to interact with radio elements
+
+  @pending  
+  Scenario: See whitch option of a radio collection is setted
+    Given I am on a page that has a radio group with the follow opitions:
+      | cucumber           | 
+      | watir-webdriver    | 
+      | selenium-webdriver | 
+      | ruby               | 
+    And the option "Ruby" is setted
+    Then I should be able to know that the option "Ruby" is setted
+
+  Scenario: See if a radio option is not setted
+    Given I am on a page that has a radio group with the follow opitions:
+      | cucumber           | 
+      | watir-webdriver    | 
+      | selenium-webdriver | 
+      | ruby               | 
+    And the option "Ruby" is setted
+    Then I should be able to know if the option "Cucumber" is not setted
+
+  Scenario: See if a radio option is not setted (Counter Proof)
+    Given I am on a page that has a radio group with the follow opitions:
+      | cucumber           | 
+      | watir-webdriver    | 
+      | selenium-webdriver | 
+      | ruby               | 
+    And the option "Cucumber" is setted
+    Then I should fail when ask if the the option "Cucumber" is not setted
+
+  Scenario: See if a radio option is setted
+    Given I am on a page that has a radio group with the follow opitions:
+      | cucumber           | 
+      | watir-webdriver    | 
+      | selenium-webdriver | 
+      | ruby               | 
+    And the option "Ruby" is setted
+    Then I should be able to know if the option "Ruby" is setted
+
+  Scenario: See if a radio option is setted (counter proof)
+    Given I am on a page that has a radio group with the follow opitions:
+      | cucumber           | 
+      | watir-webdriver    | 
+      | selenium-webdriver | 
+      | ruby               | 
+    Then I should fail when ask if the option "Ruby" is setted
+
+  Scenario: See if the radio collection has some option setted
+    Given I am on a page that has a radio group with the follow opitions:
+      | cucumber           | 
+      | watir-webdriver    | 
+      | selenium-webdriver | 
+      | ruby               | 
+    And the option "Ruby" is setted
+    Then I should be able to know if there is some options setted 
+
+  Scenario: See if the radio collection has some option setted
+    Given I am on a page that has a radio group with the follow opitions:
+      | cucumber           | 
+      | watir-webdriver    | 
+      | selenium-webdriver | 
+      | ruby               | 
+    Then I should fail when ask if there is some options setted 
+
+  Scenario: Select an radio option  
+    Given I am on a page that has a radio group with the follow opitions:
+      | cucumber           | 
+      | watir-webdriver    | 
+      | selenium-webdriver | 
+      | ruby               | 
+    And the option "Ruby" is setted
+    Then I should be able to select the option "Cucumber"
+    And I should be able to know if the option "Cucumber" is setted
+    
+  Scenario: Select an radio option  
+    Given I am on a page that has a radio group with the follow opitions:
+      | cucumber           | 
+      | watir-webdriver    | 
+      | selenium-webdriver | 
+      | ruby               | 
+    And the option "Ruby" is setted
+    Then I should be able to select the option "Cucumber"
+    And I should fail when ask if the option "Ruby" is setted

data/features/select.feature

@@ -0,0 +1,29 @@
+Feature: Select
+  As a developer
+  I want to use select fields
+
+  Scenario: Get the values available
+    Given I am on a page that has a select
+    Then I should be able to get the options available of it
+    
+  Scenario: Select a value
+    Given I am on a page that has a select
+    Then I should be able to select an option on it
+    And be sure that the option setted is the option selected
+
+  Scenario: Get selected
+    Given I am on a page that has a select
+    And the option "Cucumber" is selected
+    Then I should be able to know the option "Cucumber" is selected
+
+  Scenario: Get selected (counter proof)
+    Given I am on a page that has a select
+    And the option "Cucumber" is selected
+    Then I should fail when ask if the option "Rspec" is selected
+
+  #TODO: Think a way to create a default value
+  @pending 
+  Scenario: Go to default or empty
+    Given I am on a page that has a select
+    And the option "Cucumber" is selected
+    Then I should be able to go to the default option of it

data/features/site/inputs.html

@@ -1,4 +1,7 @@
 <html>
+  <head>
+    <title> Inputs page </title>
+  </head>
   <div>
     This page is used to test Cello Framwork
   </div>
@@ -18,4 +21,39 @@
       <div>Textarea with id area1</div><div> <textarea id='area1'></textarea></div>
     </div>
   </div>
+  <div>
+    <div> <p><b>Radio:</b></p>
+      <input type="radio" name="items" value="Selenium-Webdriver">Selenium-Webdriver</input>
+      <input type="radio" name="items" value="Ruby">Ruby</input>
+      <input type="radio" name="items" value="Cucumber">Cucumber</input>
+      <input type="radio" name="items" value=">Watir-Webdriver">Watir-Webdriver</input>
+    </div>
+  </div>
+  <div>
+    <div> <p><b>Link:</b></p>
+      <div>Link to other page</div><div> <a id='link1' href='./read_page.html'>Link</a>
+    </div>
+  </div>
+  <div>
+    <div> <p><b>Simple Select:</b></p>
+      <div>Select example</div><div> 
+        <select id="select1">
+          <option value="">...</option>
+          <option value="cello">Cello</option>
+          <option value="cucumber">Cucumber</option>
+          <option value="ruby">Ruby</option>
+          <option value="rspec">Rspec</option>
+         <option value="qa">QA Rocks!</option>
+        </select>
+      </div>
+    </div>
 </html>
+
+
+
+
+
+
+
+
+

data/features/site/read_page.html

@@ -0,0 +1,23 @@
+<html>
+  <div>
+    Camilo
+  </div>
+  <div>
+    Ribeiro
+  </div>
+  <div>
+    Test
+  </div>
+  <div>
+    Testing
+  </div>
+  <div>
+    Foo
+  </div>
+  <div>
+    Bar
+  </div>
+  <div>
+    <input type="text" id="new_element" value="Worked Again!" >
+  </div>
+</html>