Cucumber-JVM Reports - Tag: @deleteRegistrationAfterTest

Project	Number	Date
ApolloFullRunnerReport	develop.319	25 lut 2021, 06:08

	Steps	Scenarios	Features
@deleteRegistrationAfterTest	97	0	0	0	0	97	14	0	14	4m 2s 097ms	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 073ms

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

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

And Verify that user is redirected to registration page 190ms

And Register to application "SUPPLIER" 2s 003ms

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

Hooks

After Hooks.cleanUpAfterTest() 442ms

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 090ms

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

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

And Verify that user is redirected to registration page 184ms

And Register to application "SUPPLIER" 2s 127ms

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

Hooks

After Hooks.cleanUpAfterTest() 395ms

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 064ms

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

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

And Verify that user is redirected to registration page 158ms

And Register to application "SUPPLIER" 2s 075ms

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

Hooks

After Hooks.cleanUpAfterTest() 299ms

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 090ms

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

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

And Verify that user is redirected to registration page 175ms

And Register to application "SUPPLIER" 2s 053ms

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

Hooks

After Hooks.cleanUpAfterTest() 357ms

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 077ms

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

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

And Verify that user is redirected to registration page 163ms

And Register to application "SUPPLIER" 2s 064ms

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

Hooks

After Hooks.cleanUpAfterTest() 370ms

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 062ms

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

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

And Register to application "SUPPLIER" 2s 178ms

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

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

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

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 104ms

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 364ms

And Register to application "SUPPLIER" 2s 113ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 300ms

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 092ms

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

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

And Register to application "SUPPLIER" 2s 308ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 335ms

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 097ms

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

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

And Register to application "SUPPLIER" 2s 187ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 387ms

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 087ms

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

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

And Register to application "SUPPLIER" 2s 075ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 327ms

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 207ms

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

And Go to "USERS_TAB" 1s 094ms

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

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

And Save user details 533ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 275ms

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 115ms

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

And Go to "USERS_TAB" 776ms

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

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

And Save user details 284ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 016ms

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 145ms

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

And Go to "USERS_TAB" 767ms

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

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

And Save user details 368ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 117ms

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 252ms

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

And Go to "USERS_TAB" 1s 046ms

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

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

And Save user details 524ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 325ms

	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	4m 2s 097ms	Passed

Tag Report