Cucumber-JVM Reports - Tag: @deleteRegistrationAfterTest

Project	Number	Date
ApolloFullRunnerReport	develop.314	22 lut 2021, 04:21

	Steps	Scenarios	Features
@deleteRegistrationAfterTest	97	0	0	0	0	97	14	0	14	3m 59s 562ms	Passed

View Feature Invitation

@deleteRegistrationAfterTest

Scenario Outline Check if it possible registration after click link from invitation email

Steps

Given If user is login then logout 093ms

And Create invitation by JSON file "super-admin-skz" for "automatyy15q@test.pl" "CREATE_SUPPLIER_INVITATION" 242ms

When Mock invitation email by admin panel "super-admin-skz" "automatyy15q@test.pl" 3s 560ms

And Verify that user is redirected to registration page 179ms

And Register to application "SUPPLIER" 1s 949ms

Then Check if user can be logged "automatyy15q@test.pl" 2s 360ms

Hooks

After Hooks.cleanUpAfterTest() 462ms

View Feature Invitation

@deleteRegistrationAfterTest

Scenario Outline Check if it possible registration after click link from invitation email

Steps

Given If user is login then logout 071ms

And Create invitation by JSON file "super-admin-piast" for "automatyy19q@test.pl" "CREATE_SUPPLIER_INVITATION" 358ms

When Mock invitation email by admin panel "super-admin-piast" "automatyy19q@test.pl" 3s 407ms

And Verify that user is redirected to registration page 156ms

And Register to application "SUPPLIER" 2s 129ms

Then Check if user can be logged "automatyy19q@test.pl" 2s 216ms

Hooks

After Hooks.cleanUpAfterTest() 378ms

View Feature Invitation

@deleteRegistrationAfterTest

Scenario Outline Check if it possible registration after click link from invitation email

Steps

Given If user is login then logout 076ms

And Create invitation by JSON file "super-admin-lantmannen" for "automatyy2545q@test.pl" "CREATE_SUPPLIER_INVITATION" 232ms

When Mock invitation email by admin panel "super-admin-lantmannen" "automatyy2545q@test.pl" 3s 307ms

And Verify that user is redirected to registration page 174ms

And Register to application "SUPPLIER" 1s 984ms

Then Check if user can be logged "automatyy2545q@test.pl" 2s 059ms

Hooks

After Hooks.cleanUpAfterTest() 306ms

View Feature Invitation

@deleteRegistrationAfterTest

Scenario Outline Check if it possible registration after click link from invitation email

Steps

Given If user is login then logout 065ms

And Create invitation by JSON file "super-admin-keeeper" for "automatyy287q@test.pl" "CREATE_SUPPLIER_INVITATION" 249ms

When Mock invitation email by admin panel "super-admin-keeeper" "automatyy287q@test.pl" 3s 388ms

And Verify that user is redirected to registration page 152ms

And Register to application "SUPPLIER" 2s 083ms

Then Check if user can be logged "automatyy287q@test.pl" 2s 301ms

Hooks

After Hooks.cleanUpAfterTest() 350ms

View Feature Invitation

@deleteRegistrationAfterTest

Scenario Outline Check if it possible registration after click link from invitation email

Steps

Given If user is login then logout 080ms

And Create invitation by JSON file "super-admin-alrec" for "automatyy2871q@test.pl" "CREATE_SUPPLIER_INVITATION" 241ms

When Mock invitation email by admin panel "super-admin-alrec" "automatyy2871q@test.pl" 3s 336ms

And Verify that user is redirected to registration page 162ms

And Register to application "SUPPLIER" 2s 062ms

Then Check if user can be logged "automatyy2871q@test.pl" 2s 164ms

Hooks

After Hooks.cleanUpAfterTest() 390ms

View Feature Invitation

@deleteRegistrationAfterTest

Scenario Outline Check if logged user is redirected from registration link to invitation tab

Steps

Given If user is login then logout 061ms

And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 283ms

When Mock invitation email by admin panel "super-admin-piast" "automaty31415@test.pl" 3s 368ms

And Register to application "SUPPLIER" 2s 164ms

And Login as "automaty31415@test.pl" and set token of apiUsername "super-admin-piast" 1s 867ms

Then Mock invitation email by admin panel "super-admin-piast" "automaty31415@test.pl" 3s 367ms

And Verify that user is redirected to invitation page "automaty31415@test.pl" 411ms

Hooks

After Hooks.cleanUpAfterTest() 359ms

View Feature Invitation

@deleteRegistrationAfterTest

Scenario Outline Check if logged user is redirected from registration link to invitation tab

Steps

Given If user is login then logout 110ms

And Create invitation by JSON file "super-admin-lantmannen" for "automaty27182@test.pl" "CREATE_SUPPLIER_INVITATION" 235ms

When Mock invitation email by admin panel "super-admin-lantmannen" "automaty27182@test.pl" 3s 305ms

And Register to application "SUPPLIER" 2s 183ms

And Login as "automaty27182@test.pl" and set token of apiUsername "super-admin-lantmannen" 1s 577ms

Then Mock invitation email by admin panel "super-admin-lantmannen" "automaty27182@test.pl" 3s 367ms

And Verify that user is redirected to invitation page "automaty27182@test.pl" 302ms

Hooks

After Hooks.cleanUpAfterTest() 330ms

View Feature Invitation

@deleteRegistrationAfterTest

Scenario Outline Check if logged user is redirected from registration link to invitation tab

Steps

Given If user is login then logout 110ms

And Create invitation by JSON file "super-admin-keeeper" for "automaty6022@test.pl" "CREATE_SUPPLIER_INVITATION" 250ms

When Mock invitation email by admin panel "super-admin-keeeper" "automaty6022@test.pl" 3s 383ms

And Register to application "SUPPLIER" 2s 054ms

And Login as "automaty6022@test.pl" and set token of apiUsername "super-admin-keeeper" 1s 836ms

Then Mock invitation email by admin panel "super-admin-keeeper" "automaty6022@test.pl" 3s 343ms

And Verify that user is redirected to invitation page "automaty6022@test.pl" 318ms

Hooks

After Hooks.cleanUpAfterTest() 364ms

View Feature Invitation

@deleteRegistrationAfterTest

Scenario Outline Check if logged user is redirected from registration link to invitation tab

Steps

Given If user is login then logout 099ms

And Create invitation by JSON file "super-admin-skz" for "automaty666@test.pl" "CREATE_SUPPLIER_INVITATION" 256ms

When Mock invitation email by admin panel "super-admin-skz" "automaty666@test.pl" 3s 356ms

And Register to application "SUPPLIER" 2s 176ms

And Login as "automaty666@test.pl" and set token of apiUsername "super-admin-skz" 1s 787ms

Then Mock invitation email by admin panel "super-admin-skz" "automaty666@test.pl" 3s 297ms

And Verify that user is redirected to invitation page "automaty666@test.pl" 363ms

Hooks

After Hooks.cleanUpAfterTest() 389ms

View Feature Invitation

@deleteRegistrationAfterTest

Scenario Outline Check if logged user is redirected from registration link to invitation tab

Steps

Given If user is login then logout 102ms

And Create invitation by JSON file "super-admin-alrec" for "automaty2871q@test.pl" "CREATE_SUPPLIER_INVITATION" 270ms

When Mock invitation email by admin panel "super-admin-alrec" "automaty2871q@test.pl" 3s 375ms

And Register to application "SUPPLIER" 2s 180ms

And Login as "automaty2871q@test.pl" and set token of apiUsername "super-admin-alrec" 1s 840ms

Then Mock invitation email by admin panel "super-admin-alrec" "automaty2871q@test.pl" 3s 276ms

And Verify that user is redirected to invitation page "automaty2871q@test.pl" 324ms

Hooks

After Hooks.cleanUpAfterTest() 337ms

View Feature Invitation

@deleteRegistrationAfterTest

Scenario Outline Check if invitation cant be sent to already used username

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 170ms

When Create and accept invitation by JSON file as "super-admin-skz" for "automaty1591qa@test.pl" "CREATE_CARRIER_INVITATION" 720ms

And Go to "USERS_TAB" 985ms

And Find user "automaty1591qa@test.pl" 1s 373ms

And Change user details "email" to "apolloautomattest@test.pl" 415ms

And Save user details 511ms

And Create invitation for "CARRIER" "CARRIER" "automaty1591qa@test.pl" 703ms

Then Verify that invitation can't be sent on already used username 30s 021ms

Hooks

After Hooks.cleanUpAfterTest() 1s 105ms

View Feature Invitation

@deleteRegistrationAfterTest

Scenario Outline Check if invitation cant be sent to already used username

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 132ms

When Create and accept invitation by JSON file as "super-admin-lantmannen" for "automaty1231qa@test.pl" "CREATE_CARRIER_INVITATION" 586ms

And Go to "USERS_TAB" 765ms

And Find user "automaty1231qa@test.pl" 1s 269ms

And Change user details "email" to "apolloautomattest@test.pl" 265ms

And Save user details 313ms

And Create invitation for "CARRIER" "CARRIER" "automaty1231qa@test.pl" 592ms

Then Verify that invitation can't be sent on already used username 30s 084ms

Hooks

After Hooks.cleanUpAfterTest() 994ms

View Feature Invitation

@deleteRegistrationAfterTest

Scenario Outline Check if invitation cant be sent to already used username

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 209ms

When Create and accept invitation by JSON file as "super-admin-piast" for "automaty9231qa@test.pl" "CREATE_CARRIER_INVITATION" 641ms

And Go to "USERS_TAB" 809ms

And Find user "automaty9231qa@test.pl" 1s 233ms

And Change user details "email" to "apolloautomattest@test.pl" 247ms

And Save user details 333ms

And Create invitation for "CARRIER" "CARRIER" "automaty9231qa@test.pl" 681ms

Then Verify that invitation can't be sent on already used username 30s 078ms

Hooks

After Hooks.cleanUpAfterTest() 1s 146ms

View Feature Invitation

@deleteRegistrationAfterTest

Scenario Outline Check if invitation cant be sent to already used username

Steps

Given Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 195ms

When Create and accept invitation by JSON file as "super-admin-farmacol" for "automaty7221qa@test.pl" "CREATE_CARRIER_INVITATION" 799ms

And Go to "USERS_TAB" 975ms

And Find user "automaty7221qa@test.pl" 1s 419ms

And Change user details "email" to "apolloautomattest@test.pl" 323ms

And Save user details 479ms

And Create invitation for "CARRIER" "CARRIER" "automaty7221qa@test.pl" 689ms

Then Verify that invitation can't be sent on already used username 30s 074ms

Hooks

After Hooks.cleanUpAfterTest() 3s 605ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@deleteRegistrationAfterTest	97	0	0	0	0	97	14	0	14	3m 59s 562ms	Passed

Tag Report