Cucumber-JVM Reports - Tag: @deleteRegistrationAfterTest

Project	Number	Date
ApolloFullRunnerReport	develop.315	20 lut 2021, 12:52

	Steps	Scenarios	Features
@deleteRegistrationAfterTest	97	0	0	0	0	97	14	0	14	4m 5s 611ms	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 093ms

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

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

And Verify that user is redirected to registration page 191ms

And Register to application "SUPPLIER" 2s 070ms

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

Hooks

After Hooks.cleanUpAfterTest() 553ms

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

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

And Verify that user is redirected to registration page 149ms

And Register to application "SUPPLIER" 2s 081ms

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

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

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

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

And Verify that user is redirected to registration page 174ms

And Register to application "SUPPLIER" 2s 007ms

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

Hooks

After Hooks.cleanUpAfterTest() 353ms

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

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

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

And Verify that user is redirected to registration page 150ms

And Register to application "SUPPLIER" 2s 068ms

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

Hooks

After Hooks.cleanUpAfterTest() 361ms

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

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

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

And Verify that user is redirected to registration page 162ms

And Register to application "SUPPLIER" 2s 061ms

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

Hooks

After Hooks.cleanUpAfterTest() 400ms

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

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

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

And Register to application "SUPPLIER" 2s 110ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 491ms

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

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

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

And Register to application "SUPPLIER" 2s 106ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 328ms

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

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

And Register to application "SUPPLIER" 2s 218ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 385ms

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

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

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

And Register to application "SUPPLIER" 2s 175ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 427ms

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

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

And Register to application "SUPPLIER" 2s 159ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 387ms

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

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

And Go to "USERS_TAB" 1s 053ms

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

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

And Save user details 505ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 554ms

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

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

And Go to "USERS_TAB" 1s 017ms

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

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

And Save user details 269ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 037ms

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

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

And Go to "USERS_TAB" 945ms

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

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

And Save user details 346ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 435ms

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

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

And Go to "USERS_TAB" 1s 010ms

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

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

And Save user details 505ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 522ms

	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 5s 611ms	Passed

Tag Report