Cucumber-JVM Reports - Tag: @deleteRegistrationAfterTest

Project	Number	Date
ApolloFullRunnerReport	develop.317	24 lut 2021, 06:32

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

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

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

And Verify that user is redirected to registration page 183ms

And Register to application "SUPPLIER" 2s 088ms

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

Hooks

After Hooks.cleanUpAfterTest() 381ms

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" 281ms

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

And Verify that user is redirected to registration page 155ms

And Register to application "SUPPLIER" 2s 043ms

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

Hooks

After Hooks.cleanUpAfterTest() 393ms

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

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

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

And Verify that user is redirected to registration page 156ms

And Register to application "SUPPLIER" 2s 099ms

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

Hooks

After Hooks.cleanUpAfterTest() 293ms

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" 255ms

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

And Verify that user is redirected to registration page 180ms

And Register to application "SUPPLIER" 2s 007ms

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

Hooks

After Hooks.cleanUpAfterTest() 369ms

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

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

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

And Verify that user is redirected to registration page 147ms

And Register to application "SUPPLIER" 2s 004ms

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

Hooks

After Hooks.cleanUpAfterTest() 321ms

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

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

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

And Register to application "SUPPLIER" 2s 198ms

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

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" 392ms

Hooks

After Hooks.cleanUpAfterTest() 362ms

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-lantmannen" for "automaty27182@test.pl" "CREATE_SUPPLIER_INVITATION" 228ms

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

And Register to application "SUPPLIER" 2s 018ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 303ms

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

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

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

And Register to application "SUPPLIER" 2s 222ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 339ms

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" 254ms

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

And Register to application "SUPPLIER" 2s 242ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 363ms

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

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

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

And Register to application "SUPPLIER" 2s 234ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 334ms

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

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

And Go to "USERS_TAB" 1s 076ms

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

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

And Save user details 502ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 298ms

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

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

And Go to "USERS_TAB" 797ms

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

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

And Save user details 342ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 043ms

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

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

And Go to "USERS_TAB" 790ms

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

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

And Save user details 352ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 167ms

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

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

And Go to "USERS_TAB" 1s 026ms

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

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

And Save user details 542ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 451ms

	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 929ms	Passed

Tag Report