Cucumber-JVM Reports - Feature: Invitation

Project	Number	Date
ApolloFullRunnerReport	develop.307	16 lut 2021, 05:08

	Steps	Scenarios	Features
Invitation	151	0	0	0	0	151	27	0	27	9m 32s 349ms	Passed

@deleteInvitationAfterTest

Scenario Outline Check if it possible to create invitation

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 241ms

When Create invitation for "CARRIER" "CARRIER" "automatyy1@test.pl" 1s 099ms

Then Create invitation success alert is displayed 783ms

And Invitation is displayed on list "automatyy1@test.pl" 155ms

Hooks

After Hooks.deleteInvitationAfterTest() 036ms

@deleteInvitationAfterTest

Scenario Outline Check if it possible to create invitation

Steps

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

When Create invitation for "CARRIER" "CARRIER" "automatyy2@test.pl" 691ms

Then Create invitation success alert is displayed 270ms

And Invitation is displayed on list "automatyy2@test.pl" 168ms

Hooks

After Hooks.deleteInvitationAfterTest() 034ms

@deleteInvitationAfterTest

Scenario Outline Check if it possible to create invitation

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 992ms

When Create invitation for "CARRIER" "CARRIER" "automatyy2@test.pl" 663ms

Then Create invitation success alert is displayed 209ms

And Invitation is displayed on list "automatyy2@test.pl" 176ms

Hooks

After Hooks.deleteInvitationAfterTest() 034ms

@deleteInvitationAfterTest

Scenario Outline Check if it possible to create invitation

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 097ms

When Create invitation for "CARRIER" "CARRIER" "automatyy2@test.pl" 651ms

Then Create invitation success alert is displayed 205ms

And Invitation is displayed on list "automatyy2@test.pl" 170ms

Hooks

After Hooks.deleteInvitationAfterTest() 034ms

@deleteInvitationAfterTest

Scenario Outline Check if it possible to create invitation

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 133ms

When Create invitation for "CARRIER" "CARRIER" "automatyy2@test.pl" 658ms

Then Create invitation success alert is displayed 206ms

And Invitation is displayed on list "automatyy2@test.pl" 169ms

Hooks

After Hooks.deleteInvitationAfterTest() 035ms

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

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

And Verify that user is redirected to registration page 183ms

And Register to application "SUPPLIER" 2s 018ms

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

Hooks

After Hooks.cleanUpAfterTest() 487ms

@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" 295ms

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

And Verify that user is redirected to registration page 163ms

And Register to application "SUPPLIER" 2s 011ms

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

Hooks

After Hooks.cleanUpAfterTest() 446ms

@deleteRegistrationAfterTest

Scenario Outline Check if it possible registration after click link from invitation email

Steps

Given If user is login then logout 069ms

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

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

And Verify that user is redirected to registration page 145ms

And Register to application "SUPPLIER" 2s 089ms

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

Hooks

After Hooks.cleanUpAfterTest() 337ms

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

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

And Verify that user is redirected to registration page 160ms

And Register to application "SUPPLIER" 2s 048ms

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

Hooks

After Hooks.cleanUpAfterTest() 339ms

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

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

And Verify that user is redirected to registration page 146ms

And Register to application "SUPPLIER" 2s 057ms

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

Hooks

After Hooks.cleanUpAfterTest() 372ms

@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" 282ms

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

And Register to application "SUPPLIER" 2s 177ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 383ms

@deleteRegistrationAfterTest

Scenario Outline Check if logged user is redirected from registration link to invitation tab

Steps

Given If user is login then logout 115ms

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

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

And Register to application "SUPPLIER" 2s 161ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 308ms

@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" 292ms

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

And Register to application "SUPPLIER" 1s 964ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 363ms

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

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

And Register to application "SUPPLIER" 2s 209ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 372ms

@deleteRegistrationAfterTest

Scenario Outline Check if logged user is redirected from registration link to invitation tab

Steps

Given If user is login then logout 088ms

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

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

And Register to application "SUPPLIER" 2s 163ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 359ms

@deleteInvitationAfterTest

Scenario Outline Check if carrier gets invitation on mail address

Steps

And Create invitation by JSON file "super-admin-skz" for "apolloautomattest@gmail.com" "CREATE_CARRIER_INVITATION" 284ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zaproszenie do nawiązania współpracy" 7s 391ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 034ms

@deleteInvitationAfterTest

Scenario Outline Check if carrier gets invitation on mail address

Steps

And Create invitation by JSON file "super-admin-lantmannen" for "apolloautomattest@gmail.com" "CREATE_CARRIER_INVITATION" 257ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zaproszenie do nawiązania współpracy" 47s 082ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 041ms

@deleteInvitationAfterTest

Scenario Outline Check if carrier gets invitation on mail address

Steps

And Create invitation by JSON file "super-admin-keeeper" for "apolloautomattest@gmail.com" "CREATE_CARRIER_INVITATION" 287ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zaproszenie do nawiązania współpracy" 39s 721ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 044ms

@deleteInvitationAfterTest

Scenario Outline Check if carrier gets invitation on mail address

Steps

And Create invitation by JSON file "super-admin-adama" for "apolloautomattest@gmail.com" "CREATE_CARRIER_INVITATION" 244ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zaproszenie do nawiązania współpracy" 43s 220ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 034ms

@deleteInvitationAfterTest

Scenario Outline Check if carrier gets invitation on mail address

Steps

And Create invitation by JSON file "super-admin-piast" for "apolloautomattest@gmail.com" "CREATE_CARRIER_INVITATION" 311ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zaproszenie do nawiązania współpracy" 44s 256ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 038ms

@deleteInvitationAfterTest

Scenario Outline Check if carrier gets invitation on mail address

Steps

And Create invitation by JSON file "super-admin-alrec" for "apolloautomattest@gmail.com" "CREATE_CARRIER_INVITATION" 268ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zaproszenie do nawiązania współpracy" 55s 870ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 040ms

@deleteInvitationAfterTest

Scenario Outline Check if carrier gets invitation on mail address

Steps

And Create invitation by JSON file "super-admin-sempertrans" for "apolloautomattest@gmail.com" "CREATE_CARRIER_INVITATION" 259ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zaproszenie do nawiązania współpracy" 37s 247ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 035ms

@cleanUserDetailsAfterTest

Scenario Outline Check if user has accepted invitation from principal after accepting invitation by another user from company

Steps

Given Set token of apiUsername "super-admin-farmacol" 093ms

And Prepare user "dnfa1-supplier" details with all notifications and "automaty314153@test.pl" by JSON file 333ms

And Create invitation by JSON file "super-admin-farmacol" for "automaty314153@test.pl" "CREATE_SUPPLIER_INVITATION" 392ms

And Prepare user "dnfa1-supplier-2" details with all notifications and "automaty214152@test.pl" by JSON file 263ms

And Create invitation by JSON file "super-admin-farmacol" for "automaty214152@test.pl" "CREATE_SUPPLIER_INVITATION" 364ms

When Login as "dnfa1-supplier" and set token of apiUsername "super-admin-farmacol" 2s 627ms

And Go to "INVITATIONS_TAB" 157ms

And Accept invitation 15s 762ms

And If user is login then logout 090ms

And Login as "dnfa1-supplier-2" and set token of apiUsername "super-admin-farmacol" 2s 331ms

And Verify if user has visible "no waiting" invitation 15s 276ms

And Verify if user has visible "accepted" invitation 334ms

And Verify if user can see "Farmacol" on principal switch dropdown 091ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 301ms

@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 228ms

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

And Go to "USERS_TAB" 1s 104ms

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

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

And Save user details 516ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 302ms

@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 127ms

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

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

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

And Save user details 285ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 158ms

@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 152ms

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

And Go to "USERS_TAB" 773ms

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

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

And Save user details 358ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 538ms

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

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

And Go to "USERS_TAB" 1s 033ms

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

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

And Save user details 517ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 362ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Invitation	151	0	0	0	0	151	27	0	27	9m 32s 349ms	Passed

Feature Report