README.md in puppetlabs_spec_helper-2.3.2 vs README.md in puppetlabs_spec_helper-2.4.0

@@ -238,10 +238,22 @@
   repositories:
     firewall: "git://github.com/puppetlabs/puppetlabs-firewall"
     stdlib: "git://github.com/puppetlabs/puppetlabs-stdlib"
 ```
 
+Put a supplementary repository at a different location
+
+```yaml
+fixtures:
+  repositories:
+    firewall: "git://github.com/puppetlabs/puppetlabs-firewall"
+    stdlib: "git://github.com/puppetlabs/puppetlabs-stdlib"
+    control_repo:
+      repo: "https://github.com/puppetlabs/control-repo"
+      target: "spec/fixtures/control_repos"
+```
+
 Specify that the git tag `2.4.2` of `stdlib' should be checked out:
 
 ```yaml
 fixtures:
   repositories:
@@ -331,9 +343,19 @@
 remembering to duplicate any existing environment variables:
 
     env:
       - FUTURE_PARSER=yes CI_NODE_TOTAL=2 CI_NODE_INDEX=1
       - FUTURE_PARSER=yes CI_NODE_TOTAL=2 CI_NODE_INDEX=2
+      
+#### Running tests tagged with test tiers
+To run tests tagged with risk levels set the ``TEST_TIERS`` environment variable to a comma-separated list of 
+the appropriate tiers.
+
+For example: to run tests marked ``tier_high => true`` and ``tier_medium => true`` in the same test run set the 
+environment variable``TEST_TIERS=high,medium``
+  
+Note, if the ``TEST_TIERS`` environment variable is set to empty string or nil, all tiers will be executed.
+
 
 Generating code coverage reports
 ================================
 
 This section describes how to add code coverage reports for Ruby files (types, providers, ...).