Cucumber-JVM Reports - Tag: @deleteRegistrationAfterTest

Project	Number	Date
ApolloFullRunnerReport	master.333	05 mar 2021, 05:03

	Steps	Scenarios	Features
@deleteRegistrationAfterTest	106	0	0	0	0	106	15	0	15	4m 14s 727ms	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 087ms

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

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

And Verify that user is redirected to registration page 217ms

And Register to application "SUPPLIER" 2s 055ms

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

Hooks

After Hooks.cleanUpAfterTest() 555ms

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

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

And Verify that user is redirected to registration page 195ms

And Register to application "SUPPLIER" 2s 056ms

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

Hooks

After Hooks.cleanUpAfterTest() 430ms

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

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

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

And Verify that user is redirected to registration page 175ms

And Register to application "SUPPLIER" 2s 080ms

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

Hooks

After Hooks.cleanUpAfterTest() 304ms

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

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

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

And Verify that user is redirected to registration page 172ms

And Register to application "SUPPLIER" 2s 063ms

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

Hooks

After Hooks.cleanUpAfterTest() 411ms

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

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

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

And Verify that user is redirected to registration page 178ms

And Register to application "SUPPLIER" 2s 006ms

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

Hooks

After Hooks.cleanUpAfterTest() 436ms

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

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

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

And Register to application "SUPPLIER" 2s 145ms

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

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

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

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

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

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

And Register to application "SUPPLIER" 2s 195ms

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

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

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

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

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

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

And Register to application "SUPPLIER" 2s 247ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 346ms

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

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

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

And Register to application "SUPPLIER" 2s 012ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 386ms

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

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

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

And Register to application "SUPPLIER" 2s 181ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 390ms

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

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

And Go to "USERS_TAB" 1s 171ms

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

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

And Save user details 508ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 400ms

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

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

And Go to "USERS_TAB" 799ms

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

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

And Save user details 321ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 248ms

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

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

And Go to "USERS_TAB" 793ms

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

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

And Save user details 417ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 838ms

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

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

And Go to "USERS_TAB" 998ms

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

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

And Save user details 525ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 517ms

View Feature Invitation

@deleteRegistrationAfterTest

Scenario Outline Check if accepted invitation is visible in accepted tab

Steps

Given If user is login then logout 088ms

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

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

And Verify that user is redirected to registration page 158ms

And Register to application "SUPPLIER" 2s 056ms

Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 213ms

When Go to "INVITATIONS_TAB" 164ms

Then Go to "ACCEPTED_TAB" invitation status tab 045ms

And Invitation is displayed on list "automaty31415@test.pl" 100ms

Hooks

After Hooks.cleanUpAfterTest() 1s 291ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@deleteRegistrationAfterTest	106	0	0	0	0	106	15	0	15	4m 14s 727ms	Passed

Tag Report