openshift-origin-controller 1.3.2

data/test/cucumber/cartridge-runtime-extended-ruby.feature

@@ -0,0 +1,22 @@
+@runtime
+@not-origin
+Feature: Cartridge Runtime Extended Checks (Ruby)
+
+  @runtime_extended2
+  Scenario Outline: Hot deployment tests
+    Given a new <type> type application
+    And the application is made publicly accessible
+    And hot deployment <hot_deploy_status> for the application
+    And the application cartridge PIDs are tracked
+    When an update is pushed to the application repo
+    Then a <proc_name> process will be running
+    And the tracked application cartridge PIDs <pid_changed> changed
+    When I destroy the application
+    Then a <proc_name> process will not be running
+
+  Scenarios: Code push scenarios
+    | type         | proc_name        | hot_deploy_status | pid_changed   |
+    | ruby-1.8     | PassengerWatchd  | is not enabled    | should be     |
+    | ruby-1.9     | PassengerWatchd  | is not enabled    | should be     |
+    | ruby-1.8     | PassengerWatchd  | is enabled        | should not be |
+    | ruby-1.9     | PassengerWatchd  | is enabled        | should not be |

data/test/cucumber/cartridge-runtime-standard-diy.feature

@@ -0,0 +1,6 @@
+@runtime
+Feature: Cartridge Runtime Standard Checks (DIY)
+
+  @runtime4
+  Scenario: DIY cartridge checks
+    Given a new diy-0.1 application, verify it using ruby

data/test/cucumber/cartridge-runtime-standard-jbossas.feature

@@ -0,0 +1,7 @@
+@runtime
+@not-origin
+Feature: Cartridge Runtime Standard Checks (JBoss AS)
+
+  @runtime2
+  Scenario: JBoss AS cartridge checks
+    Given a new jbossas-7 application, verify it using java

data/test/cucumber/cartridge-runtime-standard-jbosseap.feature

@@ -0,0 +1,7 @@
+@runtime
+@not-origin
+Feature: Cartridge Runtime Standard Checks (JBoss EAP)
+
+  @runtime2
+  Scenario: JBoss EAP cartridge checks
+    Given a new jbosseap-6.0 application, verify it using java

data/test/cucumber/cartridge-runtime-standard-jbossews10.feature

@@ -0,0 +1,7 @@
+@runtime
+@not-origin
+Feature: Cartridge Runtime Standard Checks (JBoss EWS2.0)
+
+  @runtime2
+  Scenario: JBoss EWS2.0 cartridge checks
+    Given a new jbossews-1.0 application, verify it using java

data/test/cucumber/cartridge-runtime-standard-jenkins.feature

@@ -0,0 +1,8 @@
+@runtime
+@runtime3
+@jenkins
+@not-origin
+Feature: Jenkins Application
+
+   Scenario: Create Delete one Jenkins Application
+     Given a new jenkins-1.4 application, verify it using java

data/test/cucumber/cartridge-runtime-standard-nodejs.feature

@@ -0,0 +1,7 @@
+@runtime
+@not-origin
+Feature: Cartridge Runtime Standard Checks (Node)
+
+  @runtime1
+  Scenario: Node cartridge checks
+    Given a new nodejs-0.6 application, verify it using node

data/test/cucumber/cartridge-runtime-standard-perl.feature

@@ -0,0 +1,6 @@
+@runtime
+Feature: Cartridge Runtime Standard Checks (Perl)
+
+  @runtime2
+  Scenario: Perl cartridge checks
+    Given a new perl-5.10 application, verify it using httpd

data/test/cucumber/cartridge-runtime-standard-php.feature

@@ -0,0 +1,6 @@
+@runtime
+Feature: Cartridge Runtime Standard Checks (PHP)
+
+  @runtime2
+  Scenario: PHP cartridge checks
+    Given a new php-5.3 application, verify it using httpd

data/test/cucumber/cartridge-runtime-standard-python.feature

@@ -0,0 +1,6 @@
+@runtime
+Feature: Cartridge Runtime Standard Checks (Python)
+
+  @runtime2
+  Scenario: Python cartridge checks
+    Given a new python-2.6 application, verify it using httpd

data/test/cucumber/cartridge-runtime-standard-ruby.feature

@@ -0,0 +1,19 @@
+@runtime
+Feature: Cartridge Runtime Standard Checks (Ruby)
+
+  @runtime1
+  Scenario Outline: Ruby cartridge checks on ruby-1.8
+    Given a new <type> application, verify it using httpd
+
+    Scenarios:
+      | type     |
+      | ruby-1.8 |
+
+  @runtime1
+  @not-origin
+  Scenario Outline: Ruby cartridge checks on ruby-1.9
+    Given a new <type> application, verify it using httpd
+
+    Scenarios:
+      | type     |
+      | ruby-1.9 |

data/test/cucumber/cartridge-switchyard.feature

@@ -0,0 +1,36 @@
+@runtime
+@runtime4
+Feature: SwitchYard Application Sub-Cartridge
+  
+  Scenario: Create Delete one EAP application with embedded SwitchYard
+    Given a new jbosseap-6.0 type application
+    
+    When I embed a switchyard-0.6 cartridge into the application
+    Then the eap module configuration file will exist
+    
+    When I remove the switchyard-0.6 cartridge from the application
+    Then the eap module configuration file will not exist
+    
+    When I destroy the application
+    
+  Scenario: Create Delete one AS application with embedded SwitchYard
+    Given a new jbossas-7 type application
+    
+    When I embed a switchyard-0.6 cartridge into the application
+    Then the as module configuration file will exist
+    
+    When I remove the switchyard-0.6 cartridge from the application
+    Then the eap module configuration file will not exist
+    
+    When I destroy the application
+    
+  Scenario: Create Delete one Non-JBoss application with embedded SwitchYard
+    Given a new php-5.3 type application
+    
+    When I fail to embed a switchyard-0.6 cartridge into the application
+    Then the as module configuration file will not exist
+    And the eap module configuration file will not exist
+    
+    When I destroy the application
+  
+    

data/test/cucumber/descriptor.feature

@@ -0,0 +1,40 @@
+@runtime_extended
+@runtime_extended3
+Feature: Descriptor parsing and elaboration tests
+
+  Scenario: Descriptor parsing
+    Given an accepted node
+    And a descriptor file is provided
+    When the descriptor file is parsed as a cartridge
+    Then the descriptor profile exists
+    And atleast 1 group exists
+    And atleast 1 component exists
+
+
+  #Scenario: Descriptor elaboration of empty application
+    #Given an accepted node
+    #When a new application object with no framework is created
+    #And the application is elaborated
+    #Then the application contains atleast one group instance
+    #And the application contains atmost one group instance
+#
+  #Scenario: Descriptor elaboration of application with dependencies
+    #Given an accepted node
+    #When a new application object with php-5.3 framework is created
+    #And the application is elaborated
+    #Then the application contains atleast one group instance
+    #And the application contains atmost one group instance
+    #And the application does contain php-5.3 components
+#
+  #Scenario: Descriptor elaboration after dynamically adding and removing dependencies
+    #Given an accepted node
+    #When a new application object with php-5.3 framework is created
+    #And the application is elaborated
+    #Then the application does contain php-5.3 components
+    #When the cartridge mongodb-2.2 is added
+    #And the application is elaborated
+    #Then the application does contain mongodb-2.2 components
+    #When the cartridge mongodb-2.2 is removed
+    #And the application is elaborated
+    #Then the application does not contain mongodb-2.2 components
+#

data/test/cucumber/embedded.feature

@@ -0,0 +1,44 @@
+@runtime_extended
+@runtime_extended3
+Feature: Embedded Cartridge Verification Tests
+
+  Scenario: Embedded Usage
+    Given the libra client tools
+    And an accepted node
+    When 1 php-5.3 applications are created
+    Then the applications should be accessible
+
+    Given an existing php-5.3 application without an embedded cartridge
+    When the embedded mysql-5.1 cartridge is added
+    And the embedded phpmyadmin-3.4 cartridge is added
+    Then the application should be accessible
+    When the application uses mysql
+    Then the application should be accessible
+    And the mysql response is successful
+    When the embedded phpmyadmin-3.4 cartridge is removed
+    And the embedded mysql-5.1 cartridge is removed
+    Then the application should be accessible
+
+    When the embedded mongodb-2.2 cartridge is added
+    And the embedded cron-1.4 cartridge is added
+    Then the application should be accessible
+    And the embedded mongodb-2.2 cartridge is removed
+    And the embedded cron-1.4 cartridge is removed
+    Then the application should be accessible
+
+    When the application is destroyed
+    Then the application should not be accessible
+
+  #Scenario: Jenkins Client Usage
+  #  Given the libra client tools
+  #  And an accepted node
+  #  When 1 jenkins-1.4 applications are created
+  #  Then the applications should be accessible
+  #  Given an existing jenkins-1.4 application without an embedded cartridge
+  #  When the embedded jenkins-client-1.4 cartridge is added
+  #  Then the application should be accessible
+  #  When the embedded jenkins-client-1.4 cartridge is removed
+  #  Then the application should be accessible
+  #  When the application is destroyed
+  #  Then the application should not be accessible
+  

data/test/cucumber/idler.feature

@@ -0,0 +1,75 @@
+@singleton
+Feature: Explicit idle/restore checks
+
+  Scenario Outline: Idle one application
+    Given a new <type> type application
+    Then a <proc_name> process will be running
+    And I record the active capacity
+
+    When I oo-idle the application
+    Then a <proc_name> process will not be running
+    And the active capacity has been reduced
+
+  Scenarios:
+    | type         | proc_name |
+    | jbossas-7    | java      |
+    | jbosseap-6.0 | java      |
+    | jbossews-1.0 | java      |
+    | nodejs-0.6   | node      |
+    | perl-5.10    | httpd     |
+    | php-5.3      | httpd     |
+    | python-2.6   | httpd     |
+    | ruby-1.8     | httpd     |
+    | ruby-1.9     | httpd     |
+
+  Scenario Outline: Restore one application
+    Given a new <type> type application
+    Then a <proc_name> process will be running
+    And I record the active capacity
+
+    When I oo-idle the application
+    Then a <proc_name> process will not be running
+    And the active capacity has been reduced
+    And I record the active capacity after idling
+
+    When I oo-restore the application
+    Then a <proc_name> process will be running
+    And the active capacity has been increased
+
+  Scenarios:
+    | type         | proc_name |
+    | jbossas-7    | java      |
+    | jbosseap-6.0 | java      |
+    | jbossews-1.0 | java      |
+    | nodejs-0.6   | node      |
+    | perl-5.10    | httpd     |
+    | php-5.3      | httpd     |
+    | python-2.6   | httpd     |
+    | ruby-1.8     | httpd     |
+    | ruby-1.9     | httpd     |
+
+  Scenario Outline: Auto-restore one application
+    Given a new <type> type application
+    Then a <proc_name> process will be running
+    And I record the active capacity
+
+    When I oo-idle the application
+    Then a <proc_name> process will not be running
+    And the active capacity has been reduced
+    And I record the active capacity after idling
+
+    When I run the health-check for the <type> cartridge
+    Then a <proc_name> process will be running
+    And the active capacity has been increased
+
+  Scenarios:
+    | type         | proc_name |
+    | jbossas-7    | java      |
+    | jbosseap-6.0 | java      |
+    | jbossews-1.0 | java      |
+    | nodejs-0.6   | node      |
+    | perl-5.10    | httpd     |
+    | php-5.3      | httpd     |
+    | python-2.6   | httpd     |
+    | ruby-1.8     | httpd     |
+    | ruby-1.9     | httpd     |

data/test/cucumber/misc/descriptor/manifest.yml

@@ -0,0 +1,22 @@
+Name: www-dynamic
+Display-Name: www-dynamic v2.2 (noarch)
+Description: Web server
+Version: 1.0.0
+License: ASL 2.0
+Vendor: Apache
+Provides:
+  - "www-dynamic"
+Conflicts:
+Native-Requires: mod_bw
+Architecture: noarch
+Publishes:
+  get-internal-uri:
+    Type: "NET_TCP:HTTP"
+Subscribes:
+  set-doc-root:
+    Type: "FILESYSTEM:doc-root"
+    Required: false
+  set-proxy-url:
+    Type: "STRING:proxy-path"
+    Required: false
+

data/test/cucumber/misc/php/db_test.php

@@ -0,0 +1,21 @@
+<?php
+# Connection Info
+$hostname="HOSTNAME";
+$user="USER";
+$password="PASSWORD";
+$database="mysql";
+
+# Queries
+$table_sql="CREATE TABLE test2(id int(6) NOT NULL auto_increment, name varchar(15) NOT NULL, PRIMARY KEY(id))";
+$insert_sql="INSERT INTO test2 VALUES ('', 'Success')";
+$select_sql="SELECT * from test2";
+
+# MySQL verification
+mysql_connect($hostname, $user, $password) or die(mysql_error());
+mysql_select_db($database) or die(mysql_error());
+mysql_query($table_sql);
+mysql_query($insert_sql);
+$result=mysql_query($select_sql) or die(mysql_error());
+mysql_close();
+echo mysql_result($result,0,"name")
+?>

data/test/cucumber/openshift-node.feature

@@ -0,0 +1,21 @@
+@runtime
+@runtime4
+Feature: Account Management
+  Scenario: Create One Account
+    Given an accepted node
+    When I create a guest account
+    Then an account password entry should exist
+    And an account home directory should exist
+
+  Scenario: Delete One Account
+    Given an accepted node
+    And a new guest account
+    When I delete the guest account
+    Then an account password entry should not exist
+    And an account home directory should not exist
+    
+ Scenario: Delete One Namespace
+    Given an accepted node
+    When I create a new namespace
+    And I delete the namespace
+    Then a namespace should get deleted

data/test/cucumber/rest-application-templates.feature

@@ -0,0 +1,31 @@
+@broker_api
+@broker_api1
+@not-origin
+Feature: application templates
+	As an API client
+	In order to do things with application templates
+	I want to List and Show application templates without authenticating
+
+	Scenario Outline: List application templates
+		Given I accept "<format>"
+		When I send an unauthenticated GET request to "/application_templates"
+		Then the response should be "200"
+		#And the response should be a list of "application templates"
+		
+		Scenarios:
+		|format|
+		|JSON|
+		|XML|
+		
+	#Scenario Outline: Get a specific application template
+	#	Given I accept "<format>"
+	#	And an application template UUID
+	#	When I send an unauthenticated GET request to "/application_templates/<uuid>"
+	#	Then the response should be "200"
+	#	And the response should be a "application template"
+		
+	#	Scenarios:
+	#	|format|
+	#	|JSON|
+	#	|XML|
+		

data/test/cucumber/rest-applications.feature

@@ -0,0 +1,431 @@
+@broker_api
+@broker_api2
+Feature: applications
+  As an API client
+  In order to do things with domains
+  I want to List, Create, Retrieve, Start, Stop, Restart, Force-stop and Delete applications
+  
+  Scenario Outline: List applications
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge=php-5.3"
+    Then the response should be "201"
+    When I send a GET request to "/domains/api<random>/applications"
+    Then the response should be "200"
+    When I send a DELETE request to "/domains/api<random>/applications/app"
+    Then the response should be "204"
+    
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+
+    
+  Scenario Outline: Create application
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge=php-5.3"
+    Then the response should be "201"
+    And the response should be a "application" with attributes "name=app&framework=php-5.3"
+    When I send a DELETE request to "/domains/api<random>/applications/app"
+    Then the response should be "204"
+    
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+
+  Scenario Outline: Create application with multiple cartridges
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridges=php-5.3&cartridges=mysql-5.1&cartridges=phpmyadmin-3.4&initial_git_url=https://github.com/openshift/wordpress-example"
+    Then the response should be "201"
+    And the response should be a "application" with attributes "name=app&framework=php-5.3"
+    When I send a DELETE request to "/domains/api<random>/applications/app"
+    Then the response should be "204"
+    
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+     
+  Scenario Outline: Create application with invalid cartridge combinations
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridges=mysql-5.1&cartridges=phpmyadmin-3.4"
+    Then the response should be "422"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridges=php-5.3&cartridges=ruby-1.9"
+    Then the response should be "422"
+    
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+     
+  Scenario Outline: Create application with blank, missing, too long and invalid name
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=&cartridge=php-5.3"
+    Then the response should be "422"
+    And the error message should have "field=name&severity=error&exit_code=105"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"cartridge=php-5.3"
+    Then the response should be "422"
+    And the error message should have "field=name&severity=error&exit_code=105"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app?one&cartridge=php-5.3"
+    Then the response should be "422"
+    And the error message should have "field=name&severity=error&exit_code=105"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=appone1234567890123456789012345678901234567890&cartridge=php-5.3"
+    Then the response should be "422"
+    And the error message should have "field=name&severity=error&exit_code=105"
+    
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+
+  Scenario Outline: Retrieve application
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge=php-5.3"
+    Then the response should be "201"
+    When I send a GET request to "/domains/api<random>/applications/app"
+    Then the response should be "200"
+    And the response should be a "application" with attributes "name=app&framework=php-5.3"
+    When I send a DELETE request to "/domains/api<random>/applications/app"
+    Then the response should be "204"
+    
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+
+  Scenario Outline: Start application
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge=php-5.3"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications/app/events" with the following:"event=start"
+    Then the response should be "200"
+    When I send a DELETE request to "/domains/api<random>/applications/app"
+    Then the response should be "204"
+    
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+
+  Scenario Outline: Stop application
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge=php-5.3"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications/app/events" with the following:"event=stop"
+    Then the response should be "200"
+    When I send a DELETE request to "/domains/api<random>/applications/app"
+    Then the response should be "204"
+    
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+
+  Scenario Outline: Restart application
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge=php-5.3"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications/app/events" with the following:"event=restart"
+    Then the response should be "200"
+    When I send a DELETE request to "/domains/api<random>/applications/app"
+    Then the response should be "204"
+    
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+
+  Scenario Outline: Force-stop application
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge=php-5.3"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications/app/events" with the following:"event=force-stop"
+    Then the response should be "200"
+    When I send a DELETE request to "/domains/api<random>/applications/app"
+    Then the response should be "204"
+  
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+  
+  Scenario Outline: Threaddump application
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge=ruby-1.8"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications/app/events" with the following:"event=thread-dump"
+    Then the response should be "200"
+    When I send a DELETE request to "/domains/api<random>/applications/app"
+    Then the response should be "204"
+    
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+  Scenario Outline: Add and remove application alias
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge=php-5.3"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications/app/events" with the following:"event=add-alias"
+    Then the response should be "422"
+    When I send a POST request to "/domains/api<random>/applications/app/events" with the following:"event=add-alias&alias=app-api.foobar.com"
+    Then the response should be "200"
+    When I send a POST request to "/domains/api<random>/applications/app/events" with the following:"event=remove-alias&alias=app-api.foobar.com"
+    Then the response should be "200"
+    When I send a POST request to "/domains/api<random>/applications/app/events" with the following:"event=add-alias&alias=app-@#$api.foobar.com"
+    Then the response should be "422"
+    When I send a DELETE request to "/domains/api<random>/applications/app"
+    Then the response should be "204"
+    
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+  
+  Scenario Outline: Delete application
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge=php-5.3"
+    Then the response should be "201"
+    When I send a DELETE request to "/domains/api<random>/applications/app"
+    Then the response should be "204"
+    When I send a GET request to "/domains/api<random>/applications/app"
+    Then the response should be "404"
+  
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+
+  Scenario Outline: Create duplicate application
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge=php-5.3"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge=php-5.3"
+    Then the response should be "422"
+    And the error message should have "field=name&severity=error&exit_code=100"
+    When I send a DELETE request to "/domains/api<random>/applications/app"
+    Then the response should be "204"
+    
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+
+  Scenario Outline: Create application with invalid, blank or missing cartridge
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge=bogus"
+    Then the response should be "422"
+    And the error message should have "field=cartridge&severity=error&exit_code=109"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge="
+    Then the response should be "422"
+    And the error message should have "field=cartridge&severity=error&exit_code=109"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app"
+    Then the response should be "422"
+    And the error message should have "field=cartridge&severity=error&exit_code=109"
+    When I send a DELETE request to "/domains/api<random>/applications/app"
+    Then the response should be "404"
+  
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+
+  Scenario Outline: Retrieve or delete a non-existent application
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a GET request to "/domains/api<random>/applications/app"
+    Then the response should be "404"
+    And the error message should have "severity=error&exit_code=101"
+    When I send a DELETE request to "/domains/api<random>/applications/app"
+    Then the response should be "404"
+    And the error message should have "severity=error&exit_code=101"
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+
+  Scenario Outline: Retrieve application descriptor
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge=php-5.3"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications/app/cartridges" with the following:"cartridge=mysql-5.1"
+    Then the response should be "201"
+    When I send a GET request to "/domains/api<random>/applications/app/descriptor"
+    Then the response descriptor should have "php-5.3,mysql-5.1" as dependencies
+    When I send a DELETE request to "/domains/api<random>/applications/app"
+    Then the response should be "204"
+    
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+
+  Scenario Outline: Stop and Start embedded cartridge
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge=php-5.3"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications/app/cartridges" with the following:"cartridge=mysql-5.1"
+    Then the response should be "201"
+    When I send a GET request to "/domains/api<random>/applications/app/descriptor"
+    Then the response descriptor should have "php-5.3,mysql-5.1" as dependencies
+    When I send a POST request to "/domains/api<random>/applications/app/cartridges/mysql-5.1/events" with the following:"event=stop"
+    Then the response should be "200"
+    When I send a POST request to "/domains/api<random>/applications/app/cartridges/mysql-5.1/events" with the following:"event=start"
+    Then the response should be "200"
+    When I send a DELETE request to "/domains/api<random>/applications/app"
+    Then the response should be "204"
+    
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+
+  Scenario Outline: Restart embedded cartridge
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge=php-5.3"
+    Then the response should be "201"  
+    When I send a POST request to "/domains/api<random>/applications/app/cartridges" with the following:"cartridge=mysql-5.1"
+    Then the response should be "201"
+    When I send a GET request to "/domains/api<random>/applications/app/cartridges/mysql-5.1"
+    Then the response should be "200"
+    When I send a GET request to "/domains/api<random>/applications/app/descriptor"
+    Then the response descriptor should have "php-5.3,mysql-5.1" as dependencies
+    When I send a POST request to "/domains/api<random>/applications/app/cartridges/mysql-5.1/events" with the following:"event=restart"
+    Then the response should be "200"
+    When I send a DELETE request to "/domains/api<random>/applications/app"
+    Then the response should be "204"
+    
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+
+  Scenario Outline: Remove embedded cartridge
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge=php-5.3"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications/app/cartridges" with the following:"cartridge=mysql-5.1"
+    Then the response should be "201"
+    When I send a GET request to "/domains/api<random>/applications/app/descriptor"
+    Then the response descriptor should have "php-5.3,mysql-5.1" as dependencies
+    When I send a DELETE request to "/domains/api<random>/applications/app/cartridges/mysql-5.1"
+    Then the response should be "200"
+    When I send a GET request to "/domains/api<random>/applications/app/descriptor"
+    Then the response descriptor should have "php-5.3" as dependencies
+    When I send a DELETE request to "/domains/api<random>/applications/app"
+    Then the response should be "204"
+  
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+     
+     
+  Scenario Outline: Scale-up and scale-down as application that is not scalable
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge=diy-0.1"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications/app/events" with the following:"event=scale-up"
+    Then the response should be "422"
+    When I send a POST request to "/domains/api<random>/applications/app/events" with the following:"event=scale-down"
+    Then the response should be "422"
+    When I send a DELETE request to "/domains/api<random>/applications/app"
+    Then the response should be "204"
+    
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+     
+  Scenario Outline: add application or application event to a non-existent domain
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains/bogus/applications" with the following:"name=app&cartridge=jbossas-7"
+    Then the response should be "404"
+    And the error message should have "severity=error&exit_code=127"
+    When I send a POST request to "/domains/bogus/applications/app/events" with the following:"event=scale-up"
+    Then the response should be "404"
+    And the error message should have "severity=error&exit_code=127"
+    
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+     
+  Scenario Outline: Resolve application dns
+    Given a new user
+    And I accept "<format>"
+    When I send a POST request to "/domains" with the following:"id=api<random>"
+    Then the response should be "201"
+    When I send a POST request to "/domains/api<random>/applications" with the following:"name=app&cartridge=php-5.3"
+    Then the response should be "201"
+    When I send a GET request to "/domains/api<random>/applications/app/dns_resolvable"
+    Then the response should be one of "200,404"
+    
+    Scenarios:
+     | format | 
+     | JSON | 
+     | XML | 
+