Migrate to Allure 2 (#749)

Add allure 2.7.0 dependency; change class references of Description, Features, Stories

Signed-off-by: Stefan Klotz <stefan.klotz@bosch-si.com>
This commit is contained in:
Stefan Klotz
2018-10-25 18:18:38 +02:00
committed by Dominic Schabel
parent f8e1a547b0
commit d09ca7be05
129 changed files with 602 additions and 601 deletions

View File

@@ -44,12 +44,12 @@ Examples:
### Test documentation
Please documented the test cases that you contribute by means of [Allure](http://allure.qatools.ru) annotations and proper test method naming.
Please documented the test cases that you contribute by means of [Allure](https://docs.qameta.io/allure/) annotations and proper test method naming.
All test classes are documented with [Allure's](https://github.com/allure-framework/allure-core/wiki/Features-and-Stories) **@Features** and **@Stories** annotations in the following format:
All test classes are documented with [Allure's](https://docs.qameta.io/allure/#_behaviours_mapping) **@Feature** and **@Story** annotations in the following format:
```
@Features("TEST_TYPE - HAWKBIT_COMPONENT")
@Stories("Test class description")
@Feature("TEST_TYPE - HAWKBIT_COMPONENT")
@Story("Test class description")
```
Test types are:
@@ -69,8 +69,8 @@ Examples for hawkBit components:
* Security
```java
@Features("Component Tests - Management API")
@Stories("Distribution Set Type Resource")
@Feature("Component Tests - Management API")
@Story("Distribution Set Type Resource")
```
In addition all test method's name describes in **camel case** what the test is all about and has in addition a long description in Allures **@Description** annotation.