All node command sare relative and other refacvtorings

- Removed session:node:* commands in favor of node:* commands

Author: dantleech

.travis.yml

@@ -13,3 +13,4 @@ before_script:
 script: 
   - phpunit --coverage-text
   - php vendor/behat/behat/bin/behat
+  - php vendor/bin/phpspec run

composer.json

@@ -14,7 +14,8 @@
         "symfony/process": "2.3.*",
         "symfony/filesystem": "2.3.*",
         "phpunit/phpunit": "~3.7.28",
-        "behat/behat": "~2.5"
+        "behat/behat": "~2.5",
+        "phpspec/phpspec": "2.0"
     },
     "license": "MIT",
     "authors": [

features/node_definition.feature

@@ -9,7 +9,7 @@ Feature: Show CND for node
 
     Scenario: Show node definition
         Given the current node is "/tests_general_base"
-        And I execute the "node:definition --no-ansi" command
+        And I execute the "node:definition daniel --no-ansi" command
         Then the command should fail
         And I should see the following:
         """

features/node_info.feature

@@ -9,12 +9,12 @@ Feature: Show information about node
 
     Scenario: Show node information
         Given the current node is "/tests_general_base"
-        And I execute the "node:info --no-ansi" command
+        And I execute the "node:info daniel --no-ansi" command
         Then the command should not fail
         And I should see the following:
         """
         +-------------------+--------------------------------------+
-        | Path              | /tests_general_base                  |
+        | Path              | /tests_general_base/daniel           |
         | UUID              | N/A                                  |
         | Index             | 1                                    |
         | Primary node type | nt:unstructured                      |

features/node_lifecycle_follow_transition.feature

@@ -9,7 +9,7 @@ Feature: Follow the given lifecycle transition on the current node
 
     Scenario: Follow lifecycle transition
         Given the current node is "/tests_general_base"
-        And I execute the "node:lifecycle:follow foo" command
+        And I execute the "node:lifecycle:follow daniel foo" command
         Then the command should fail
         And I should see the following:
         """

features/node_lifecycle_list.feature

@@ -9,7 +9,7 @@ Feature: List the possible lifecycle transitions for the current node
 
     Scenario: List possible lifecycle transitions
         Given the current node is "/tests_general_base"
-        And I execute the "node:lifecycle:list" command
+        And I execute the "node:lifecycle:list daniel" command
         Then the command should fail
         And I should see the following:
         """

features/node_mixin_add.feature

@@ -9,7 +9,7 @@ Feature: Add mixin to the current node
 
     Scenario: Add a mixin to the current node
         Given the current node is "/tests_general_base"
-        And I execute the "node:mixin:add mix:versionable --no-ansi" command
+        And I execute the "node:mixin:add . mix:versionable --no-ansi" command
         And I save the session
         Then the command should not fail
         And the node at "/tests_general_base" should have the mixin "mix:versionable"

features/node_references.feature

@@ -9,7 +9,7 @@ Feature: Show node references
 
     Scenario: List weak references
         Given the current node is "/tests_general_base/idExample/jcr:content/weakreference_target"
-        And I execute the "node:references --no-ansi" command
+        And I execute the "node:references . --no-ansi" command
         Then the command should not fail
         And I should see a table containing the following rows:
             | Type | Property | Node Path                                                      |
@@ -18,15 +18,15 @@ Feature: Show node references
 
     Scenario: List named weak references
         Given the current node is "/tests_general_base/idExample/jcr:content/weakreference_target"
-        And I execute the "node:references ref2 --no-ansi" command
+        And I execute the "node:references . ref2 --no-ansi" command
         Then the command should not fail
         And I should see a table containing the following rows:
             | Type | Property | Node Path                                                      |
             | weak | ref2     | /tests_general_base/idExample/jcr:content/weakreference_target |
 
     Scenario: List strong references
         Given the current node is "/tests_general_base/idExample"
-        And I execute the "node:references --no-ansi" command
+        And I execute the "node:references . --no-ansi" command
         Then the command should not fail
         And I should see a table containing the following rows:
             | Type   | Property | Node Path                              |

features/node_remove.feature

@@ -9,7 +9,7 @@ Feature: Remove a node
 
     Scenario: Remove a node
         Given the current node is "/tests_general_base"
-        And I execute the "node:remove" command
+        And I execute the "node:remove ." command
         Then the command should not fail
         And I save the session
         And there should not exist a node at "/tests_general_base"

features/node_rename.feature

@@ -9,7 +9,7 @@ Feature: Rename a node
 
     Scenario: Rename a node
         Given the current node is "/tests_general_base/idExample"
-        And I execute the "node:rename foobar" command
+        And I execute the "node:rename . foobar" command
         And I save the session
         Then the command should not fail
         And there should exist a node at "/tests_general_base/foobar"