On 01/11/11 08:44 -0400, Chris Alfonso wrote:
The deployment features currently rely on the deltacloud-core service
running.
rake cucumber will by default not run tests marked with the tag @wip
To run the @wip tests with rake, use rake cucumber:wip
You can also exclude the @wip tests using cucumber directly with,
cucumber --tags ~@wip <feature>
---
src/features/deployment.feature | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/src/features/deployment.feature b/src/features/deployment.feature
index 0df9549..6eec21a 100644
--- a/src/features/deployment.feature
+++ b/src/features/deployment.feature
@@ -26,6 +26,7 @@ Feature: Manage Deployments
#It's difficult to mock out all the dependencies to get the instance launching
#working in a testable scenario.
+ @wip
Scenario: Launch new deployment
Given a pool "mockpool" exists
And there is "front_hwp1" conductor hardware profile
@@ -79,6 +80,7 @@ Feature: Manage Deployments
And I press "stop_button"
Then I should see "testdeployment"
+ @wip
Scenario: Stop a deployment over XHR
Given there is a deployment named "testdeployment" belonging to
"testdeployable" owned by "testuser"
And I request XHR
@@ -175,6 +177,7 @@ Feature: Manage Deployments
When I follow "details_instances"
Then I should see "testdeployment"
+ @wip
Scenario: Delete a deployment
Given there is a deployment named "testdeployment" belonging to
"testdeployable" owned by "testuser"
And I am on the pools page
@@ -182,6 +185,7 @@ Feature: Manage Deployments
And I press "delete"
Then I should see "The deployment testdeployment was scheduled for
deletion"
+ @wip
Scenario: Delete multiple deployments
Given a deployment "mydeployment1" exists
And a deployment "mydeployment2" exists
@@ -193,6 +197,7 @@ Feature: Manage Deployments
And I press "delete_button"
Then I should see "The deployments mydeployment1, mydeployment2 were scheduled
for deletion"
+ @wip
Scenario: Delete a deployment with running instances
Given a deployment "mockdeployment" exists
And the deployment "mockdeployment" has an instance named
"myinstance"
--
1.7.6.4
It's also worth mentioning, the deployment tests take a really long time to execute,
so by marking them with a tag that is by default excluded, you can get through a test run
much more quickly. We may want to introduce a new tag with @takesforever or something,
that way you could run sanity check tests more often, then run the @takesforever tests
when you really want to test everything.