Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: bvtdev
Fetching contributors…

Octocat-spinner-32-eaf2f5

Cannot retrieve contributors at this time

file 68 lines (61 sloc) 3.58 kb
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67
Feature: Deploy rack applications that make use of autostaging

As a user of Cloud Foundry
I want to launch apps that expect automatic binding of the services that they use

Background: rack autostaging
Given I have registered and logged in

@ruby @sanity @services
Scenario: rack autostaging
Given I have deployed a rack application named app_rack_service_autoconfig
When I query status of my application
Then I should get the state of my application
Then I should be able to access my application root and see hello from sinatra
Then I should be able to access crash and it should crash
When I provision mysql service
Then I post mysqlabc to mysql service with key abc
Then I should be able to get from mysql service with key abc, and I should see mysqlabc
Then I delete my service
When I provision redis service
Then I post redisabc to redis service with key abc
Then I should be able to get from redis service with key abc, and I should see redisabc
When I provision mongodb service
Then I post mongoabc to mongo service with key abc
Then I should be able to get from mongo service with key abc, and I should see mongoabc
When I provision rabbitmq service
Then I post rabbitabc to rabbitmq service with key abc
Then I should be able to get from rabbitmq service with key abc, and I should see rabbitabc
When I provision postgresql service
Then I post postgresqlabc to postgresql service with key abc
Then I should be able to get from postgresql service with key abc, and I should see postgresqlabc
Then I delete all my service
Then I delete my application

@ruby
Scenario: rack ruby 1.9 autostaging
Given I have deployed a rack application named rack_autoconfig_ruby19
When I query status of my application
Then I should get the state of my application
Then I should be able to access my application root and see hello from sinatra
When I provision redis service
Then I post redisabc to redis service with key abc
Then I should be able to get from redis service with key abc, and I should see redisabc
Then I delete all my service
Then I delete my application

@ruby
Scenario: rack opt-out of autostaging via config file
Given I have deployed a rack application named rack_autoconfig_disabled_by_file
When I query status of my application
Then I should get the state of my application
Then I should be able to access my application root and see hello from sinatra
When I provision redis service
Then I should be able to get from redis service with key connection, and I should see Connectionrefused-UnabletoconnecttoRedison127.0.0.1:6379
Then I delete all my service
Then I delete my application

@ruby
Scenario: rack opt-out of autostaging via cf-runtime gem
Given I have deployed a rack application named rack_autoconfig_disabled_by_gem
When I query status of my application
Then I should get the state of my application
Then I should be able to access my application root and see hello from sinatra
When I provision redis service
Then I should be able to get from redis service with key connection, and I should see Connectionrefused-UnabletoconnecttoRedison127.0.0.1:6379
Then I delete all my service
Then I delete my application
Something went wrong with that request. Please try again.