Cucumber-JVM Reports - Tag: @deleteRegistrationAfterTest

Project	Number	Date
ApolloFullRunnerReport	after_release_3_6_0.327	01 mar 2021, 06:19

	Steps	Scenarios	Features
@deleteRegistrationAfterTest	106	0	0	0	0	106	15	0	15	4m 8s 580ms	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 074ms

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

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

And Verify that user is redirected to registration page 184ms

And Register to application "SUPPLIER" 2s 001ms

Then Check if user can be logged "automatyy15q@test.pl" 2s 725ms

Hooks

After Hooks.cleanUpAfterTest() 382ms

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

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

And Verify that user is redirected to registration page 183ms

And Register to application "SUPPLIER" 2s 060ms

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

Hooks

After Hooks.cleanUpAfterTest() 395ms

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

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

And Verify that user is redirected to registration page 180ms

And Register to application "SUPPLIER" 2s 053ms

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

Hooks

After Hooks.cleanUpAfterTest() 339ms

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

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

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

And Verify that user is redirected to registration page 147ms

And Register to application "SUPPLIER" 2s 059ms

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

Hooks

After Hooks.cleanUpAfterTest() 348ms

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

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

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

And Verify that user is redirected to registration page 148ms

And Register to application "SUPPLIER" 2s 084ms

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

Hooks

After Hooks.cleanUpAfterTest() 358ms

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

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

And Register to application "SUPPLIER" 2s 101ms

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

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

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

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

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

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

And Register to application "SUPPLIER" 2s 030ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 338ms

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

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

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

And Register to application "SUPPLIER" 2s 197ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 362ms

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-skz" for "automaty666@test.pl" "CREATE_SUPPLIER_INVITATION" 247ms

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

And Register to application "SUPPLIER" 2s 211ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 374ms

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

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

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

And Register to application "SUPPLIER" 2s 202ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 352ms

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

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

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

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

And Save user details 494ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 169ms

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

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

And Go to "USERS_TAB" 806ms

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

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

And Save user details 330ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 891ms

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

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

And Go to "USERS_TAB" 798ms

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

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

And Save user details 341ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 155ms

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

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

And Go to "USERS_TAB" 976ms

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

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

And Save user details 507ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 226ms

View Feature Invitation

@deleteRegistrationAfterTest

Scenario Outline Check if accepted invitation is visible in accepted tab

Steps

Given If user is login then logout 091ms

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

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

And Verify that user is redirected to registration page 157ms

And Register to application "SUPPLIER" 2s 062ms

Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 1s 796ms

When Go to "INVITATIONS_TAB" 184ms

Then Go to "ACCEPTED_TAB" invitation status tab 057ms

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

Hooks

After Hooks.cleanUpAfterTest() 1s 007ms

	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 8s 580ms	Passed

Tag Report