Cucumber-JVM Reports - Tag: @deleteRegistrationAfterTest

Project	Number	Date
ApolloFullRunnerReport	master.314	20 lut 2021, 00:05

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

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

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

And Verify that user is redirected to registration page 219ms

And Register to application "SUPPLIER" 1s 957ms

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

Hooks

After Hooks.cleanUpAfterTest() 535ms

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

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

And Verify that user is redirected to registration page 202ms

And Register to application "SUPPLIER" 1s 919ms

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

Hooks

After Hooks.cleanUpAfterTest() 425ms

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

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

And Verify that user is redirected to registration page 222ms

And Register to application "SUPPLIER" 2s 031ms

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

Hooks

After Hooks.cleanUpAfterTest() 314ms

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

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

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

And Verify that user is redirected to registration page 175ms

And Register to application "SUPPLIER" 2s 058ms

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

Hooks

After Hooks.cleanUpAfterTest() 341ms

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

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

And Verify that user is redirected to registration page 144ms

And Register to application "SUPPLIER" 2s 056ms

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

Hooks

After Hooks.cleanUpAfterTest() 333ms

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

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

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

And Register to application "SUPPLIER" 2s 185ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 393ms

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

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

And Register to application "SUPPLIER" 2s 161ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 314ms

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

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

And Register to application "SUPPLIER" 2s 172ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 347ms

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

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

And Register to application "SUPPLIER" 2s 002ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 420ms

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

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

And Register to application "SUPPLIER" 2s 235ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 337ms

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

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

And Go to "USERS_TAB" 1s 093ms

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

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

And Save user details 527ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 303ms

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

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

And Go to "USERS_TAB" 977ms

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

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

And Save user details 280ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 218ms

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

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

And Go to "USERS_TAB" 935ms

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

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

And Save user details 354ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 360ms

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

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

And Go to "USERS_TAB" 1s 023ms

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

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

And Save user details 514ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 327ms

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

Tag Report