Cucumber-JVM Reports - Tag: @deleteRegistrationAfterTest

Project	Number	Date
ApolloFullRunnerReport	develop.316	23 lut 2021, 06:54

	Steps	Scenarios	Features
@deleteRegistrationAfterTest	97	0	0	0	0	97	14	0	14	4m 1s 200ms	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 100ms

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

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

And Verify that user is redirected to registration page 191ms

And Register to application "SUPPLIER" 2s 090ms

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

Hooks

After Hooks.cleanUpAfterTest() 478ms

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-piast" for "automatyy19q@test.pl" "CREATE_SUPPLIER_INVITATION" 280ms

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

And Verify that user is redirected to registration page 167ms

And Register to application "SUPPLIER" 2s 015ms

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

Hooks

After Hooks.cleanUpAfterTest() 377ms

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

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

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

And Verify that user is redirected to registration page 213ms

And Register to application "SUPPLIER" 2s 044ms

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

Hooks

After Hooks.cleanUpAfterTest() 310ms

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-keeeper" for "automatyy287q@test.pl" "CREATE_SUPPLIER_INVITATION" 241ms

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

And Verify that user is redirected to registration page 168ms

And Register to application "SUPPLIER" 1s 928ms

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

Hooks

After Hooks.cleanUpAfterTest() 335ms

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

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

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

And Verify that user is redirected to registration page 152ms

And Register to application "SUPPLIER" 2s 038ms

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

Hooks

After Hooks.cleanUpAfterTest() 349ms

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

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

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

And Register to application "SUPPLIER" 2s 190ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 377ms

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

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

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

And Register to application "SUPPLIER" 2s 193ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 327ms

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

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

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

And Register to application "SUPPLIER" 2s 161ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 357ms

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

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

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

And Register to application "SUPPLIER" 2s 185ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 354ms

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-alrec" for "automaty2871q@test.pl" "CREATE_SUPPLIER_INVITATION" 236ms

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

And Register to application "SUPPLIER" 2s 139ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 356ms

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

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

And Go to "USERS_TAB" 948ms

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

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

And Save user details 517ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 960ms

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

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

And Go to "USERS_TAB" 776ms

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

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

And Save user details 287ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 070ms

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

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

And Go to "USERS_TAB" 787ms

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

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

And Save user details 298ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 204ms

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

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

And Go to "USERS_TAB" 992ms

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

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

And Save user details 535ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 400ms

	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 1s 200ms	Passed

Tag Report