ara-cli 0.1.9.73__py3-none-any.whl → 0.1.9.74__py3-none-any.whl

ara_cli/templates/template.feature

@@ -1,26 +0,0 @@
-@sample_tag
-Feature: <descriptive title>
-
-  As a <user>
-  I want to <do something | need something>
-  So that <I can achieve something>
-
-  Contributes to <filename or title of the artefact> <agile requirement artefact category> <(optional in case the contribution is to an artefact that is detailed with rules) using rule <rule as it is formulated>   
-
-  Description: <further optional description to understand
-  the rule, no format defined, the example artefact is only a placeholder>
-
-  Scenario: <descriptive scenario title>
-    Given <precondition>
-    When <action>
-    Then <expected result>
-
-  Scenario Outline: <descriptive scenario title>
-    Given <precondition>
-    When <action>
-    Then <expected result>
-
-    Examples:
-      | descriptive scenario title | precondition         | action             | expected result    |
-      | <example title 1>          | <example precond. 1> | <example action 1> | <example result 1> |
-      | <example title 2>          | <example precond. 2> | <example action 2> | <example result 2> |

ara_cli/templates/template.issue

@@ -1,14 +0,0 @@
-@sample_tag
-Issue: <descriptive issue>
-
-Contributes to <filename or title of the artefact> <agile requirement artefact category> <(optional in case the contribution is to an artefact that is detailed with rules) using rule <rule as it is formulated>  | blank | filled with text that does not refer to an artefact or rule (then this a free issue)
-
-*Optional descriptions of the issue in Gherkin style*
-
-Given <descriptive text of the starting conditions where the issue occurs>
-When <action under which the issues occurs>
-Then <resulting behavior in contrast to the expected behavior>
-
-*or optional free text description*
-
-Description: <further free text description to understand the issue, no format defined>

ara_cli/templates/template.keyfeature

@@ -1,15 +0,0 @@
-@sample_tag
-Keyfeature: <descriptive title>
-
-Contributes to <filename or title of the artefact> <agile requirement artefact category> <(optional in case the contribution is to an artefact that is detailed with rules) using rule <rule as it is formulated>
-
-In order to <support a capability or business goal>
-As a <main stakeholder who will benefit>
-I want <a product feature that helps me doing something so that I can achieve my named goal>
-
-Description: <further optional description to understand the capability, markdown capable text formatting, best practice is using
-    GIVEN any precondition
-    AND another precondition
-    WHEN some action takes place
-    THEN some result is to be expected
-    AND some other result is to be expected>

ara_cli/templates/template.task

@@ -1,6 +0,0 @@
-@to-do
-Task: <descriptive title>
-
-Contributes to <filename or title of the artefact> <agile requirement artefact category> <(optional in case the contribution is to an artefact that is detailed with rules) using rule <rule as it is formulated>  | blank | filled with text that does not refer to an artefact or rule (then this is a free task)
-
-Description: <further optional description to understand the task, no format defined>

ara_cli/templates/template.userstory

@@ -1,17 +0,0 @@
-@sample_tag
-Userstory: <descriptive title>
-
-Contributes to <filename or title of the artefact> <agile requirement artefact category> <(optional in case the contribution is to an artefact that is detailed with rules) using rule <rule as it is formulated>
-
-Estimate: <story points, scale?>
-
-In order to <achieve a benefit>
-As a <(user) role>
-I want <a certain product behavior>
-
-Rule: <rule needed to fulfill the wanted product behavior>
-Rule: <rule needed to fulfill the wanted product behavior>
-Rule: <rule needed to fulfill the wanted product behavior>
-
-Description: <further optional description to understand
-the user story, markdown capable text formatting>

ara_cli/templates/template.vision

@@ -1,14 +0,0 @@
-@sample_tag
-Vision: <descriptive title>
-
-Contributes to <filename or title of the artefact> <agile requirement artefact category> <(optional in case the contribution is to an artefact that is detailed with rules) using rule <rule as it is formulated>
-
-For <target customer>
-Who <needs something>
-The <product name> is a <product category>
-That <key benefit, compelling reason to buy>
-Unlike <primary competitive alternative>
-Our product <statement of primary differentiation>
-
-Description: <further optional description to understand
-the vision, markdown capable text formatting>