Cucumber-JVM Reports - Tag: @deleteRegistrationAfterTest

Project	Number	Date
ApolloFullRunnerReport	develop.313	21 lut 2021, 10:42

	Steps	Scenarios	Features
@deleteRegistrationAfterTest	97	0	0	0	0	97	14	0	14	4m 734ms	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 084ms

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

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

And Verify that user is redirected to registration page 197ms

And Register to application "SUPPLIER" 2s 002ms

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

Hooks

After Hooks.cleanUpAfterTest() 458ms

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

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

And Verify that user is redirected to registration page 156ms

And Register to application "SUPPLIER" 1s 975ms

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

Hooks

After Hooks.cleanUpAfterTest() 358ms

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

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

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

And Verify that user is redirected to registration page 166ms

And Register to application "SUPPLIER" 2s 044ms

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

Hooks

After Hooks.cleanUpAfterTest() 321ms

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

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

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

And Verify that user is redirected to registration page 161ms

And Register to application "SUPPLIER" 2s 074ms

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

Hooks

After Hooks.cleanUpAfterTest() 368ms

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

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

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

And Verify that user is redirected to registration page 162ms

And Register to application "SUPPLIER" 1s 954ms

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

Hooks

After Hooks.cleanUpAfterTest() 318ms

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

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

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

And Register to application "SUPPLIER" 2s 156ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 378ms

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

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

And Register to application "SUPPLIER" 2s 131ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 301ms

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

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

And Register to application "SUPPLIER" 2s 282ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 356ms

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

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

And Register to application "SUPPLIER" 1s 964ms

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

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

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

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

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

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

And Register to application "SUPPLIER" 2s 213ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 358ms

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

And Go to "USERS_TAB" 1s 021ms

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

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

And Save user details 441ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 161ms

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

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

And Go to "USERS_TAB" 766ms

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

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

And Save user details 330ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 159ms

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

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

And Go to "USERS_TAB" 795ms

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

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

And Save user details 339ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 270ms

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

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

And Go to "USERS_TAB" 962ms

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

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

And Save user details 539ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 2s 640ms

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

Tag Report