Cucumber-JVM Reports - Tag: @deleteRegistrationAfterTest

Project	Number	Date
ApolloFullRunnerReport	develop.317	22 lut 2021, 10:48

	Steps	Scenarios	Features
@deleteRegistrationAfterTest	97	0	0	0	0	97	14	0	14	4m 6s 188ms	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 083ms

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

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

And Verify that user is redirected to registration page 174ms

And Register to application "SUPPLIER" 2s 039ms

Then Check if user can be logged "automatyy15q@test.pl" 3s 420ms

Hooks

After Hooks.cleanUpAfterTest() 570ms

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

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

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

And Verify that user is redirected to registration page 167ms

And Register to application "SUPPLIER" 2s 009ms

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

Hooks

After Hooks.cleanUpAfterTest() 413ms

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

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

And Verify that user is redirected to registration page 177ms

And Register to application "SUPPLIER" 1s 991ms

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

Hooks

After Hooks.cleanUpAfterTest() 334ms

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

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

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

And Verify that user is redirected to registration page 171ms

And Register to application "SUPPLIER" 2s 118ms

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

Hooks

After Hooks.cleanUpAfterTest() 371ms

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

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

And Verify that user is redirected to registration page 179ms

And Register to application "SUPPLIER" 2s 039ms

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

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

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

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

And Register to application "SUPPLIER" 2s 195ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 435ms

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

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

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

And Register to application "SUPPLIER" 2s 162ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 306ms

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

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

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

And Register to application "SUPPLIER" 2s 173ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 367ms

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

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

And Register to application "SUPPLIER" 2s 206ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 423ms

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

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

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

And Register to application "SUPPLIER" 2s 098ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 359ms

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

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

And Go to "USERS_TAB" 1s 068ms

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

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

And Save user details 468ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 459ms

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

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

And Go to "USERS_TAB" 953ms

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

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

And Save user details 276ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 189ms

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

And Go to "USERS_TAB" 948ms

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

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

And Save user details 337ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 573ms

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" 2s 361ms

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

And Go to "USERS_TAB" 994ms

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

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

And Save user details 484ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 328ms

	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 6s 188ms	Passed

Tag Report