Cucumber-JVM Reports - Tag: @deleteRegistrationAfterTest

Project	Number	Date
ApolloFullRunnerReport	master.311	19 lut 2021, 10:44

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

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

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

And Verify that user is redirected to registration page 190ms

And Register to application "SUPPLIER" 2s 115ms

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

Hooks

After Hooks.cleanUpAfterTest() 503ms

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

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

And Verify that user is redirected to registration page 165ms

And Register to application "SUPPLIER" 2s 147ms

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

Hooks

After Hooks.cleanUpAfterTest() 404ms

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

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

And Verify that user is redirected to registration page 181ms

And Register to application "SUPPLIER" 2s 030ms

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

Hooks

After Hooks.cleanUpAfterTest() 329ms

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

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

And Verify that user is redirected to registration page 226ms

And Register to application "SUPPLIER" 1s 990ms

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

Hooks

After Hooks.cleanUpAfterTest() 373ms

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

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

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

And Verify that user is redirected to registration page 156ms

And Register to application "SUPPLIER" 2s 042ms

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

Hooks

After Hooks.cleanUpAfterTest() 382ms

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

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

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

And Register to application "SUPPLIER" 2s 156ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 645ms

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

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

And Register to application "SUPPLIER" 2s 263ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 359ms

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

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

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

And Register to application "SUPPLIER" 2s 211ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 384ms

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

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

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

And Register to application "SUPPLIER" 2s 112ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 380ms

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

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

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

And Register to application "SUPPLIER" 2s 226ms

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

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

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

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

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

And Go to "USERS_TAB" 1s 083ms

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

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

And Save user details 536ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 610ms

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

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

And Go to "USERS_TAB" 884ms

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

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

And Save user details 344ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 214ms

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

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

And Go to "USERS_TAB" 915ms

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

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

And Save user details 380ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 332ms

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

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

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

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

And Save user details 525ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 472ms

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

Tag Report