Cucumber Reports - Tag: @teacher

Project	Date
demo	19 Apr 2022, 09:10

	Steps	Scenarios	Features
@teacher	390	0	0	0	0	390	69	0	69	2.219	Passed

Feature: at/htl/beeyond/integration/application/application-finish.feature

Tags: @teacher

0.087

Scenario Finish a valid application

Steps

Given path 'approve/'+application.id 0.000

When method PATCH 0.068

Given path 'application', 'finish/'+application.id 0.000

When method PATCH 0.018

Then status 200 0.000

Feature: at/htl/beeyond/integration/application/application-finish.feature

Tags: @teacher

0.005

Scenario Finish a not existing application

Steps

Given path 'finish/100' 0.000

When method PATCH 0.005

Then status 404 0.000

Feature: at/htl/beeyond/integration/application/application-finish.feature

Tags: @teacher

0.007

Scenario Finish a pending application

Steps

Given path 'finish/'+application.id 0.000

When method PATCH 0.006

Then status 422 0.000

And match response == 'Application is not in state RUNNING or STOPPED' 0.000

Feature: at/htl/beeyond/integration/application/application-finish.feature

Tags: @teacher

0.009

Scenario Finish a denied application

Steps

Given path 'deny/'+application.id 0.000

When method PATCH 0.002

Given path 'application', 'finish/'+application.id 0.000

When method PATCH 0.006

Then status 422 0.000

And match response == 'Application is not in state RUNNING or STOPPED' 0.000

Feature: at/htl/beeyond/integration/application/application-finish.feature

Tags: @teacher

0.055

Scenario Finish a finished application

Steps

Given path 'approve/'+application.id 0.000

When method PATCH 0.018

Given path 'application','finish/'+application.id 0.000

When method PATCH 0.024

Given path 'application', 'finish/'+application.id 0.000

When method PATCH 0.012

Then status 422 0.000

And match response == 'Application is not in state RUNNING or STOPPED' 0.000

Feature: at/htl/beeyond/integration/application/application-finish.feature

Tags: @teacher

0.136

Scenario Finish a stopped application

Steps

Given path 'approve/'+application.id 0.000

When method PATCH 0.024

Given path 'application','stop/'+application.id 0.000

When method PATCH 0.020

Given path 'application', 'finish/'+application.id 0.000

When method PATCH 0.091

Then status 200 0.000

Feature: at/htl/beeyond/integration/template/template-get.feature

Tags: @teacher

0.010

Scenario Get all templates

Steps

When method GET 0.010

Then status 200 0.000

And assert response.length == 1 0.000

Feature: at/htl/beeyond/integration/application/application-approve.feature

Tags: @teacher

0.026

Scenario Approve a valid application

Steps

Given path 'approve/'+application.id 0.000

When method PATCH 0.026

Then status 200 0.000

Feature: at/htl/beeyond/integration/application/application-approve.feature

Tags: @teacher

0.005

Scenario Approve a not existing application

Steps

Given path 'approve/100' 0.000

When method PATCH 0.004

Then status 404 0.000

Feature: at/htl/beeyond/integration/application/application-approve.feature

Tags: @teacher

0.023

Scenario Approve a denied application

Steps

Given path 'deny/'+application.id 0.000

When method PATCH 0.013

Given path 'application', 'approve/'+application.id 0.000

When method PATCH 0.008

Then status 422 0.000

And match response == 'Application is not in state PENDING' 0.000

Feature: at/htl/beeyond/integration/application/application-approve.feature

Tags: @teacher

0.037

Scenario Approve a approved application

Steps

Given path 'approve/'+application.id 0.000

When method PATCH 0.030

Given path 'application', 'approve/'+application.id 0.000

When method PATCH 0.006

Then status 422 0.000

And match response == 'Application is not in state PENDING' 0.000

Feature: at/htl/beeyond/integration/application/application-approve.feature

Tags: @teacher

0.097

Scenario Approve a stopped application

Steps

Given path 'approve/'+application.id 0.000

When method PATCH 0.052

Given path 'application','stop/'+application.id 0.000

When method PATCH 0.036

Given path 'application', 'approve/'+application.id 0.000

When method PATCH 0.007

Then status 422 0.000

And match response == 'Application is not in state PENDING' 0.000

Feature: at/htl/beeyond/integration/application/application-approve.feature

Tags: @teacher

0.107

Scenario Approve a finished application

Steps

Given path 'approve/'+application.id 0.000

When method PATCH 0.031

Given path 'application', 'finish/'+application.id 0.000

When method PATCH 0.065

Given path 'application', 'approve/'+application.id 0.000

When method PATCH 0.008

Then status 422 0.000

And match response == 'Application is not in state PENDING' 0.000

Feature: at/htl/beeyond/integration/namespace/namespace-assign.feature

Tags: @teacher

0.025

Scenario Assign 1 user to a valid namespace

Steps

Given request 0.000

Doc string

{
  "namespace": "beeyond",
  "users": [
    "emina"
  ]
}

When method PUT 0.014

Then status 204 0.000

And path 'beeyond' 0.000

When method GET 0.007

Then status 200 0.000

And match response.namespace == 'beeyond' 0.000

And match response.users == '#[1]' 0.002

Feature: at/htl/beeyond/integration/namespace/namespace-assign.feature

Tags: @teacher

0.018

Scenario Assign 2 user to a valid namespace

Steps

Given request 0.000

Doc string

{
  "namespace": "beeyond",
  "users": [
    "emina",
    "moritz"
  ]
}

When method PUT 0.011

Then status 204 0.000

And path 'beeyond' 0.000

When method GET 0.006

Then status 200 0.000

And match response.namespace == 'beeyond' 0.000

And match response.users == '#[2]' 0.000

Feature: at/htl/beeyond/integration/namespace/namespace-assign.feature

Tags: @teacher

0.019

Scenario Assign 3 user to a valid namespace

Steps

Given request 0.000

Doc string

{
  "namespace": "beeyond",
  "users": [
    "emina",
    "moritz",
    "marc"
  ]
}

When method PUT 0.011

Then status 204 0.000

And path 'beeyond' 0.000

When method GET 0.006

Then status 200 0.000

And match response.namespace == 'beeyond' 0.000

And match response.users == '#[3]' 0.000

Feature: at/htl/beeyond/integration/namespace/namespace-assign.feature

Tags: @teacher

0.017

Scenario Assign 2 user to a invalid namespace (wrong characters)

Steps

Given request 0.000

Doc string

{
  "namespace": "bééyond",
  "users": [
    "emina",
    "moritz"
  ]
}

When method PUT 0.016

Then status 422 0.000

Feature: at/htl/beeyond/integration/namespace/namespace-assign.feature

Tags: @teacher

0.024

Scenario Assign 2 user to a invalid namespace (too long)

Steps

* def generateString = read('classpath:string-generator.js') 0.011

Given request 0.003

Doc string

{
  "namespace": #(generateString()),
  "users": [
    "emina",
    "moritz"
  ]
}

When method PUT 0.008

Then status 422 0.000

And match response[0].message == 'This field needs to be between 1 and 253 characters' 0.001

Feature: at/htl/beeyond/integration/namespace/namespace-assign.feature

Tags: @teacher

0.019

Scenario Assign 2 user to a invalid namespace (name of user)

Steps

Given request 0.000

Doc string

{
  "namespace": "marc",
  "users": [
    "emina",
    "moritz"
  ]
}

When method PUT 0.018

Then status 422 0.000

And match response[0].message == 'Not a valid namespace name' 0.000

Feature: at/htl/beeyond/integration/namespace/namespace-assign.feature

Tags: @teacher

0.009

Scenario Assign a nonexistent user to a valid namespace

Steps

Given request 0.000

Doc string

{
  "namespace": "beeyond",
  "users": [
     "test"
  ]
}

When method PUT 0.008

Then status 422 0.000

And match response[0].message == 'User with name [test] does not exist' 0.000

Feature: at/htl/beeyond/integration/namespace/namespace-assign.feature

Tags: @teacher

0.010

Scenario Assign a user to its own namespace (name of user)

Steps

Given request 0.000

Doc string

{
  "namespace": "emina",
  "users": [
    "emina"
  ]
}

When method PUT 0.009

Then status 422 0.000

And match response[0].message == 'Not a valid namespace name' 0.000

Feature: at/htl/beeyond/integration/namespace/namespace-assign.feature

Tags: @teacher

0.026

Scenario Assign 2 user to a valid namespace where one of them already belongs to that namespace

Steps

Given request 0.000

Doc string

{
  "namespace": "beeyond",
  "users": [
    "emina"
  ]
}

When method PUT 0.009

Given request 0.000

Doc string

{
  "namespace": "beeyond",
  "users": [
    "emina",
    "marc"
  ]
}

When method PUT 0.009

And path 'beeyond' 0.000

When method GET 0.005

Then status 200 0.000

And match response.namespace == 'beeyond' 0.000

And match response.users == '#[2]' 0.000

Feature: at/htl/beeyond/integration/namespace/namespace-assign.feature

Tags: @teacher

0.023

Scenario Assign 2 user to a valid namespace where both of them already belong to that namespace

Steps

Given request 0.000

Doc string

{
  "namespace": "beeyond",
  "users": [
    "emina",
    "marc"
  ]
}

When method PUT 0.009

Given request 0.000

Doc string

{
  "namespace": "beeyond",
  "users": [
    "emina",
    "marc"
  ]
}

When method PUT 0.007

And path 'beeyond' 0.000

When method GET 0.005

Then status 200 0.000

And match response.namespace == 'beeyond' 0.000

And match response.users == '#[2]' 0.000

Feature: at/htl/beeyond/integration/namespace/namespace-assign.feature

Tags: @teacher

0.026

Scenario Assign 2 user with the same name (same user) to a valid namespace

Steps

Given request 0.000

Doc string

{
  "namespace": "beeyond",
  "users": [
    "emina",
    "emina"
  ]
}

When method PUT 0.011

And path 'beeyond' 0.000

When method GET 0.014

Then status 200 0.000

And match response.namespace == 'beeyond' 0.000

And match response.users == '#[1]' 0.000

Feature: at/htl/beeyond/integration/namespace/namespace-assign.feature

Tags: @teacher

0.009

Scenario Assign 2 user with the same name (same user) to a invalid namespace (name of user)

Steps

Given request 0.000

Doc string

{
  "namespace": "emina",
  "users": [
    "emina",
    "emina"
  ]
}

When method PUT 0.009

Then status 422 0.000

And match response[0].message == 'Not a valid namespace name' 0.000

Feature: at/htl/beeyond/integration/namespace/namespace-assign.feature

Tags: @teacher

0.029

Scenario Assign 1 user and remove 1 from a valid namespace

Steps

Given request 0.000

Doc string

{
  "namespace": "beeyond",
  "users": [
    "emina"
  ]
}

When method PUT 0.009

Then status 204 0.000

Given request 0.000

Doc string

{
  "namespace": "beeyond",
  "users": [
    "marc"
  ]
}

When method PUT 0.007

Then status 204 0.000

And path 'beeyond' 0.000

When method GET 0.010

Then status 200 0.000

And match response.namespace == 'beeyond' 0.000

And match response.users == '#[1]' 0.000

And match response.users[0].name == 'marc' 0.000

Feature: at/htl/beeyond/integration/namespace/namespace-assign.feature

Tags: @teacher

0.023

Scenario Remove 1 from a valid namespace (1 user exists already)

Steps

Given request 0.000

Doc string

{
  "namespace": "beeyond",
  "users": [
    "emina"
  ]
}

When method PUT 0.008

Then status 204 0.000

Given request 0.000

Doc string

{
  "namespace": "beeyond",
  "users": []
}

When method PUT 0.007

Then status 204 0.000

And path 'beeyond' 0.000

When method GET 0.005

Then status 200 0.000

And response.deleted == true 0.001

Feature: at/htl/beeyond/integration/namespace/namespace-assign.feature

Tags: @teacher

0.024

Scenario Assign 1 to a valid namespace (1 user exists already)

Steps

Given request 0.000

Doc string

{
  "namespace": "beeyond",
  "users": [
    "emina"
  ]
}

When method PUT 0.008

Then status 204 0.000

Given request 0.000

Doc string

{
  "namespace": "beeyond",
  "users": [
    "emina",
    "marc"
  ]
}

When method PUT 0.008

Then status 204 0.000

And path 'beeyond' 0.000

When method GET 0.005

Then status 200 0.000

And match response.namespace == 'beeyond' 0.000

And match response.users == '#[2]' 0.000

Feature: at/htl/beeyond/integration/namespace/namespace-assign.feature

Tags: @teacher

0.042

Scenario Replace 2 users with 2 other users (A, B -> C, D)

Steps

Given request 0.000

Doc string

{
  "namespace": "beeyond",
  "users": [
    "emina",
    "marc"
  ]
}

When method PUT 0.017

Then status 204 0.000

Given request 0.000

Doc string

{
  "namespace": "beeyond",
  "users": [
    "moritz",
    "stuetz"
  ]
}

When method PUT 0.017

Then status 204 0.000

And path 'beeyond' 0.000

When method GET 0.005

Then status 200 0.000

And match response.namespace == 'beeyond' 0.000

And match response.users == '#[2]' 0.000

And match response.users contains { 'name': 'moritz', 'id': #number } 0.000

And match response.users contains { 'name': 'stuetz', 'id': #number } 0.000

Feature: at/htl/beeyond/integration/application/application-get.feature

Tags: @teacher

0.019

Scenario Get all applications

Steps

When method GET 0.019

Then status 200 0.000

And assert response.length == 1 0.000

Feature: at/htl/beeyond/integration/template/template-creation.feature

Tags: @teacher

0.011

Scenario Create a valid template application

Steps

Given request 0.000

Doc string

{
  "name": "Nginx Deployment",
  "description": "Static Webserver",
  "content": "#(nginxDeployment)",
  "fields": [
    {
      "label": "Server count",
      "wildcard": "replica",
      "description": "How many server should there be?"
    },
    {
      "label": "Port of your saver",
      "wildcard": "port",
      "description": "This will be the port that will be exposed to the world"
    }
  ]
}

When method POST 0.011

Then status 201 0.000

Feature: at/htl/beeyond/integration/template/template-creation.feature

Tags: @teacher

0.016

Scenario Create a template with no description

Steps

Given request 0.000

Doc string

{
  "name": "Nginx Deployment",
  "content": "#(nginxDeployment)",
  "fields": [
    {
      "label": "Server count",
      "wildcard": "replica",
      "description": "How many server should there be?"
    },
    {
      "label": "Port of your saver",
      "wildcard": "port",
      "description": "This will be the port that will be exposed to the world"
    }
  ]
}

When method POST 0.016

Then status 201 0.000

Feature: at/htl/beeyond/integration/template/template-creation.feature

Tags: @teacher

0.008

Scenario Create a template with no name and content

Steps

Given request 0.000

Doc string

{
  "description": "Static Webserver"
}

When method POST 0.007

Then status 422 0.000

And match response contains { message: 'This field cannot be empty', key: 'name', value: '' } 0.000

And match response contains { message: 'This field cannot be empty', key: 'content', value: '' } 0.000

Feature: at/htl/beeyond/integration/template/template-creation.feature

Tags: @teacher

0.015

Scenario Create a template with a too long name and description

Steps

Given request 0.006

Doc string

{
  "name": #(generateString()),
  "description": #(generateString()),
  "content": "#(nginxDeployment)",
  "fields": [
    {
      "label": "Server count",
      "wildcard": "replica",
      "description": "How many server should there be?"
    },
    {
      "label": "Port of your saver",
      "wildcard": "port",
      "description": "This will be the port that will be exposed to the world"
    }
  ]
}

When method POST 0.008

Then status 422 0.000

And match response contains {message:'This field needs to be between 1 and 255 characters', key: 'name', value:'#ignore'} 0.000

And match response contains {message:'This field needs to be between 0 and 255 characters', key: 'description', value:'#ignore'} 0.000

Feature: at/htl/beeyond/integration/template/template-creation.feature

Tags: @teacher

0.012

Scenario Create a template where at least 1 field is missing

Steps

Given request 0.000

Doc string

{
  "name": "Nginx Deployment",
  "description": "Static Webserver",
  "content": "#(nginxDeployment)",
  "fields": [
    {
      "label": "Server count",
      "wildcard": "replica",
      "description": "How many server should there be?"
    }
  ]
}

When method POST 0.012

Then status 422 0.000

And match response contains { message: 'Missing fields: [port], obsolete fields: []', value: '', key: '' } 0.000

Feature: at/htl/beeyond/integration/template/template-creation.feature

Tags: @teacher

0.010

Scenario Create a template where all fields is missing

Steps

Given request 0.000

Doc string

{
  "name": "Nginx Deployment",
  "description": "Static Webserver",
  "content": "#(nginxDeployment)",
  "fields": []
}

When method POST 0.010

Then status 422 0.000

And match response contains { message: 'Missing fields: [replica, port], obsolete fields: []', value: '', key: '' } 0.000

Feature: at/htl/beeyond/integration/template/template-creation.feature

Tags: @teacher

0.009

Scenario Create a template where the field label and wildcard are missing

Steps

Given request 0.000

Doc string

{
  "name": "Nginx Deployment",
  "description": "Static Webserver",
  "content": "#(nginxDeployment)",
  "fields": [
    {
      "label": "Server count",
      "wildcard": "replica",
      "description": "How many server should there be?"
    },
    {
      "description": "This will be the port that will be exposed to the world"
    }
  ]
}

When method POST 0.009

Then status 422 0.000

And match response contains { message:'This field cannot be empty' ,value: '' ,key: 'wildcard' } 0.000

And match response contains { message:'This field cannot be empty' ,value: '' ,key: 'label' } 0.000

Feature: at/htl/beeyond/integration/template/template-creation.feature

Tags: @teacher

0.010

Scenario Create a template where the field label and wildcard are empty

Steps

Given request 0.000

Doc string

{
  "name": "Nginx Deployment",
  "description": "Static Webserver",
  "content": "#(nginxDeployment)",
  "fields": [
    {
      "label": "Server count",
      "wildcard": "replica",
      "description": "How many server should there be?"
    },
    {
      "label": "",
      "wildcard": "",
      "description": "This will be the port that will be exposed to the world"
    }
  ]
}

When method POST 0.009

Then status 422 0.000

And match response contains { message: 'This field cannot be empty' , value: '' , key: 'wildcard' } 0.000

And match response contains { message: 'This field cannot be empty' , value: '' , key: 'label' } 0.000

Feature: at/htl/beeyond/integration/template/template-creation.feature

Tags: @teacher

0.014

Scenario Create a template where the field label, wildcard and description are too long

Steps

Given request 0.004

Doc string

{
  "name": "Nginx Deployment",
  "description": "Static Webserver",
  "content": "#(nginxDeployment)",
  "fields": [
    {
      "label": "Server count",
      "wildcard": "replica",
      "description": "How many server should there be?"
    },
    {
      "label": #(generateString()),
      "wildcard": #(generateString()),
      "description": #(generateString())
    }
  ]
}

When method POST 0.010

Then status 422 0.000

And match response contains { message: 'This field needs to be between 0 and 255 characters', key:'label', value: '#ignore' } 0.000

And match response contains { message: 'This field needs to be between 0 and 255 characters', key:'description', value: '#ignore' } 0.000

And match response contains { message: 'This field needs to be between 0 and 255 characters', key:'wildcard', value: '#ignore' } 0.000

Feature: at/htl/beeyond/integration/template/template-creation.feature

Tags: @teacher

0.008

Scenario Create a template where only a wrong wildcard is present

Steps

Given request 0.000

Doc string

{
  "name": "Nginx Deployment",
  "description": "Static Webserver",
  "content": "#(nginxDeployment)",
  "fields": [
    {
      "label": "Server count",
      "wildcard": "wrong-wildcard",
      "description": "How many server should there be?"
    },
  ]
}

When method POST 0.008

Then status 422 0.000

And match response contains { message: 'Missing fields: [replica, port], obsolete fields: [wrong-wildcard]', value: '', key: '' } 0.000

Feature: at/htl/beeyond/integration/template/template-creation.feature

Tags: @teacher

0.013

Scenario Create a template where no fields are missing but 1 is obsolete

Steps

Given request 0.000

Doc string

{
  "name": "Nginx Deployment",
  "description": "Static Webserver",
  "content": "#(nginxDeployment)",
  "fields": [
    {
      "label": "Server count",
      "wildcard": "wrong-wildcard",
      "description": "How many server should there be?"
    },
    {
      "label": "Server count",
      "wildcard": "replica",
      "description": "How many server should there be?"
    },
    {
      "label": "Port of your saver",
      "wildcard": "port",
      "description": "This will be the port that will be exposed to the world"
    }
  ]
}

When method POST 0.013

Then status 422 0.000

And match response contains { message: 'Missing fields: [], obsolete fields: [wrong-wildcard]', value: '', key: '' } 0.000

Feature: at/htl/beeyond/integration/template/template-creation.feature

Tags: @teacher

0.011

Scenario Create a template where id is set

Steps

Given request 0.000

Doc string

{
  "id": 9999,
  "name": "Nginx Deployment",
  "description": "Static Webserver",
  "content": "#(nginxDeployment)",
  "fields": [
    {
      "label": "Server count",
      "wildcard": "replica",
      "description": "How many server should there be?"
    },
    {
      "label": "Port of your saver",
      "wildcard": "port",
      "description": "This will be the port that will be exposed to the world"
    }
  ]
}

When method POST 0.011

Then status 201 0.000

Feature: at/htl/beeyond/integration/template/template-creation.feature

Tags: @teacher

0.017

Scenario Create a template where deleted is set

Steps

Given request 0.000

Doc string

{
  "deleted": true,
  "name": "Nginx Deployment",
  "description": "Static Webserver",
  "content": "#(nginxDeployment)",
  "fields": [
    {
      "label": "Server count",
      "wildcard": "replica",
      "description": "How many server should there be?"
    },
    {
      "label": "Port of your saver",
      "wildcard": "port",
      "description": "This will be the port that will be exposed to the world"
    }
  ]
}

When method POST 0.016

Then status 201 0.000

Feature: at/htl/beeyond/integration/template/template-creation.feature

Tags: @teacher

0.010

Scenario Create a template where field id is set

Steps

Given request 0.000

Doc string

{
  "name": "Nginx Deployment",
  "description": "Static Webserver",
  "content": "#(nginxDeployment)",
  "fields": [
    {
      "id": 9998,
      "label": "Server count",
      "wildcard": "replica",
      "description": "How many server should there be?"
    },
    {
      "id": 9999,
      "label": "Port of your saver",
      "wildcard": "port",
      "description": "This will be the port that will be exposed to the world"
    }
  ]
}

When method POST 0.010

Then status 201 0.000

Feature: at/htl/beeyond/integration/application/application-start.feature

Tags: @teacher

0.138

Scenario Start a valid application

Steps

Given path 'approve/'+application.id 0.000

When method PATCH 0.053

Given path 'application', 'stop/'+application.id 0.000

When method PATCH 0.038

Given path 'application', 'start/'+application.id 0.000

When method PATCH 0.043

Then status 200 0.000

Feature: at/htl/beeyond/integration/application/application-start.feature

Tags: @teacher

0.010

Scenario Start a not existing application

Steps

Given path 'start/100' 0.000

When method PATCH 0.009

Then status 404 0.000

Feature: at/htl/beeyond/integration/application/application-start.feature

Tags: @teacher

0.009

Scenario Start a pending application

Steps

Given path 'start/'+application.id 0.000

When method PATCH 0.008

Then status 422 0.000

And match response == 'Application is not in state STOPPED' 0.000

Feature: at/htl/beeyond/integration/application/application-start.feature

Tags: @teacher

0.012

Scenario Start a denied application

Steps

Given path 'deny/'+application.id 0.000

When method PATCH 0.005

Given path 'application', 'start/'+application.id 0.000

When method PATCH 0.006

Then status 422 0.000

And match response == 'Application is not in state STOPPED' 0.000

Feature: at/htl/beeyond/integration/application/application-start.feature

Tags: @teacher

0.120

Scenario Start a finished application

Steps

Given path 'approve/'+application.id 0.000

When method PATCH 0.047

Given path 'application','finish/'+application.id 0.000

When method PATCH 0.063

Given path 'application', 'start/'+application.id 0.000

When method PATCH 0.008

Then status 422 0.000

And match response == 'Application is not in state STOPPED' 0.000

Feature: at/htl/beeyond/integration/application/application-stop.feature

Tags: @teacher

0.035

Scenario Stop a valid application

Steps

Given path 'approve/'+application.id 0.000

When method PATCH 0.016

Given path 'application', 'stop/'+application.id 0.000

When method PATCH 0.015

Then print karate.prevRequest.headers 0.003

Doc string

09:10:10.862 [print] {
  "Authorization": [
    "Basic c3R1ZXR6OnBhc3N3b3Jk"
  ],
  "Host": [
    "localhost:8081"
  ],
  "Connection": [
    "Keep-Alive"
  ],
  "User-Agent": [
    "Apache-HttpClient/4.5.13 (Java/11.0.14)"
  ],
  "Accept-Encoding": [
    "gzip,deflate"
  ]
}

Then status 200 0.000

Feature: at/htl/beeyond/integration/application/application-stop.feature

Tags: @teacher

0.010

Scenario Stop a not existing application

Steps

Given path 'stop/100' 0.000

When method PATCH 0.009

Then status 404 0.000

Feature: at/htl/beeyond/integration/application/application-stop.feature

Tags: @teacher

0.009

Scenario Stop a pending application

Steps

Given path 'stop/'+application.id 0.000

When method PATCH 0.008

Then status 422 0.000

And match response == 'Application is not in state RUNNING' 0.000

Feature: at/htl/beeyond/integration/application/application-stop.feature

Tags: @teacher

0.011

Scenario Stop a denied application

Steps

Given path 'deny/'+application.id 0.000

When method PATCH 0.004

Given path 'application', 'stop/'+application.id 0.000

When method PATCH 0.006

Then status 422 0.000

And match response == 'Application is not in state RUNNING' 0.000

Feature: at/htl/beeyond/integration/application/application-stop.feature

Tags: @teacher

0.105

Scenario Stop a finished application

Steps

Given path 'approve/'+application.id 0.000

When method PATCH 0.065

Given path 'application','finish/'+application.id 0.000

When method PATCH 0.030

Given path 'application', 'stop/'+application.id 0.000

When method PATCH 0.009

Then status 422 0.000

And match response == 'Application is not in state RUNNING' 0.000

Feature: at/htl/beeyond/integration/application/application-stop.feature

Tags: @teacher

0.097

Scenario Stop a stopped application

Steps

Given path 'approve/'+application.id 0.000

When method PATCH 0.068

Given path 'application','stop/'+application.id 0.000

When method PATCH 0.020

Given path 'application', 'stop/'+application.id 0.000

When method PATCH 0.007

Then status 422 0.000

And match response == 'Application is not in state RUNNING' 0.000

Feature: at/htl/beeyond/integration/application/application-deny.feature

Tags: @teacher

0.010

Scenario Deny a valid application

Steps

Given path 'deny/'+application.id 0.000

When method PATCH 0.010

Then status 200 0.000

Feature: at/htl/beeyond/integration/application/application-deny.feature

Tags: @teacher

0.006

Scenario Deny a not existing application

Steps

Given path 'deny/100' 0.000

When method PATCH 0.005

Then status 404 0.000

Feature: at/htl/beeyond/integration/application/application-deny.feature

Tags: @teacher

0.028

Scenario Deny a approved application

Steps

Given path 'approve/'+application.id 0.000

When method PATCH 0.021

Given path 'application', 'deny/'+application.id 0.000

When method PATCH 0.006

Then status 422 0.000

And match response == 'Application is not in state PENDING' 0.000

Feature: at/htl/beeyond/integration/application/application-deny.feature

Tags: @teacher

0.023

Scenario Deny a denied application

Steps

Given path 'deny/'+application.id 0.000

When method PATCH 0.015

Given path 'application','deny/'+application.id 0.000

When method PATCH 0.007

Then status 422 0.000

And match response == 'Application is not in state PENDING' 0.000

Feature: at/htl/beeyond/integration/application/application-deny.feature

Tags: @teacher

0.048

Scenario Deny a stopped application

Steps

Given path 'approve/'+application.id 0.000

When method PATCH 0.024

Given path 'application','stop/'+application.id 0.000

When method PATCH 0.016

Given path 'application', 'deny/'+application.id 0.000

When method PATCH 0.007

Then status 422 0.000

And match response == 'Application is not in state PENDING' 0.000

Feature: at/htl/beeyond/integration/application/application-deny.feature

Tags: @teacher

0.060

Scenario Deny a finished application

Steps

Given path 'approve/'+application.id 0.000

When method PATCH 0.023

Given path 'application', 'finish/'+application.id 0.000

When method PATCH 0.025

Given path 'application', 'deny/'+application.id 0.000

When method PATCH 0.010

Then status 422 0.000

And match response == 'Application is not in state PENDING' 0.000

Feature: at/htl/beeyond/integration/template/template-deletion.feature

Tags: @teacher

0.013

Scenario Delete a template

Steps

Given path template.id 0.000

When method DELETE 0.006

Then status 204 0.000

Given path template.id 0.000

When method GET 0.006

Then status 200 0.000

And match response.deleted == true 0.000

Feature: at/htl/beeyond/integration/template/template-deletion.feature

Tags: @teacher

0.004

Scenario Delete a template that does not exist

Steps

Given path '1000' 0.000

When method DELETE 0.004

Then status 404 0.000

Feature: at/htl/beeyond/integration/application/application-request.feature

Tags: @teacher

0.019

Scenario Request a valid application

Steps

Given path 'deny/'+application.id 0.000

When method PATCH 0.010

Given path 'application', 'request/'+application.id 0.000

When method PATCH 0.008

Then status 200 0.000

Feature: at/htl/beeyond/integration/application/application-request.feature

Tags: @teacher

0.005

Scenario Request a not existing application

Steps

Given path 'request/100' 0.000

When method PATCH 0.004

Then status 404 0.000

Feature: at/htl/beeyond/integration/application/application-request.feature

Tags: @teacher

0.010

Scenario Request a pending application

Steps

Given path 'request/'+application.id 0.000

When method PATCH 0.009

Then status 422 0.000

And match response == 'Application is not in state DENIED' 0.000

Feature: at/htl/beeyond/integration/application/application-request.feature

Tags: @teacher

0.029

Scenario Request a approved application

Steps

Given path 'approve/'+application.id 0.000

When method PATCH 0.021

Given path 'application', 'request/'+application.id 0.000

When method PATCH 0.006

Then status 422 0.000

And match response == 'Application is not in state DENIED' 0.000

Feature: at/htl/beeyond/integration/application/application-request.feature

Tags: @teacher

0.189

Scenario Request a finished application

Steps

Given path 'approve/'+application.id 0.000

When method PATCH 0.125

Given path 'application','finish/'+application.id 0.001

When method PATCH 0.043

Given path 'application', 'request/'+application.id 0.000

When method PATCH 0.019

Then status 422 0.000

And match response == 'Application is not in state DENIED' 0.000

Feature: at/htl/beeyond/integration/application/application-request.feature

Tags: @teacher

0.057

Scenario Request a stopped application

Steps

Given path 'approve/'+application.id 0.000

When method PATCH 0.030

Given path 'application','stop/'+application.id 0.000

When method PATCH 0.019

Given path 'application', 'request/'+application.id 0.000

When method PATCH 0.006

Then status 422 0.000

And match response == 'Application is not in state DENIED' 0.000

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@teacher	390	0	0	0	0	390	69	0	69	2.219	Passed

Tag Report