adamgoucher

basics
------
parts
selectors
synchronization
evolution-of-a-script

se-ide
------
overview

adamgoucher

# see https://github.com/rspec/rspec-core/commit/aa6f7e8744abb4bdc2060fb32a58bd2aeea04e14

describe "rabbit holes" do
  #
  # single tags - can be either but not both
  #
  # rspec --tag depth:shallow tags.rb
  # rspec --tag depth:deep tags.rb
  #
  # multiple tags

adamgoucher

So this is what I have got myself into:

An important trend in software development is the idea of continuous delivery and the deployment pipeline. It is possible to have a deployment pipeline that is a series of manual steps, but that is neither efficient to execute or fun to build. Automation plays a large role in addressing both of these problems. This workshop looks at each stage of a typical pipeline and illustrates the role of automation and it’s goals.  Appropriate for developers, testers, operations or anyone who wants to speed up their release time, participants will leave with implementable automation ideas and strategies.

The current version of the agenda is:
- Introduction to Continuous Delivery
   - http://element34.ca/blog/what-continuous-delivery-looks-like-to-me
   - http://vimeo.com/16587500
- Managing the Machines (Puppet)
   - http://element34.ca/blog/continuous-delivery-managing-the-machines

adamgoucher

# RSpec 2.0 syntax Cheet Sheet by http://ApproachE.com

# defining spec within a module will automatically pick Player::MovieList as a 'subject' (see below)
module Player
	describe MovieList, "with optional description" do
		  
	  it "is pending example, so that you can write ones quickly"
	  
	  it "is already working example that we want to suspend from failing temporarily" do
		pending("working on another feature that temporarily breaks this one")

adamgoucher

When doing automation I coach people not to put in logging in their scripts aside from things like 'here is the user name and password I randomly created just now' but I couldn't coax the default documentation formatter in rspec to capture information send via 'puts'. So I over-engineered a solution. Proper documentation and inclusion in my rspec-selenium-pageobjects project in a day or so.

spec_helper.rb
--------------
module RSpec
  module Core
    class Reporter
      def with(message)
        notify :with, message
      end

adamgoucher

So what would a 'Testing Android' book look like?

Part One
1 - High-level overview of the moving parts of Android
  * Activities
  * Services
  * Broadcast Receivers
  * Content Providers

2 - Introduction to the Sample App

adamgoucher

import pytest
import selenium

class TestRemoteControl():
    def setup_method(self, method):
        self.connection = selenium.selenium("localhost", 4444, "*firefox", "http://saucelabs.com")
        self.connection.start()
        self.connection.window_maximize()
        self.connection.open("/signup")
        

adamgoucher

Page Objects 101

* Why?
  * Readable scripts
  * Improved maintenance
  * Moves complexity out of Scripts
* Page Objects
  * One per page /or/ one per logical section of page
  * Locators
  * Elements

adamgoucher

def foo(object):
    def __init_(self):
        self.content = "blah"
    def __get__(self):
        print(self.content)
    def __set__(self, a, b):
        self.a = b

class monkey(object):
    bar = foo()

adamgoucher

Feature: Add a workshop
  In order to have people book a workshop
  As a trainer
  I want to add a workshop
  
  Scenario: A basic workshop
    Given I have entered a basic workshop information
    When I add it to the system
    Then learners can express interest