Cucumber-JVM Reports - Feature: Invitation

Project	Number	Date
ApolloFullRunnerReport	master.311	19 lut 2021, 10:44

	Steps	Scenarios	Features
Invitation	151	0	0	0	0	151	27	0	27	8m 53s 919ms	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 258ms

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

Then Create invitation success alert is displayed 812ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 048ms

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

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

Then Create invitation success alert is displayed 282ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 037ms

@deleteInvitationAfterTest

Scenario Outline Check if it possible to create invitation

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 012ms

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

Then Create invitation success alert is displayed 255ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 031ms

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

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

Then Create invitation success alert is displayed 260ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 029ms

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

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

Then Create invitation success alert is displayed 205ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 039ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 196ms

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

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

And Verify that user is redirected to registration page 190ms

And Register to application "SUPPLIER" 2s 115ms

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

Hooks

After Hooks.cleanUpAfterTest() 503ms

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

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

And Verify that user is redirected to registration page 165ms

And Register to application "SUPPLIER" 2s 147ms

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

Hooks

After Hooks.cleanUpAfterTest() 404ms

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

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

And Verify that user is redirected to registration page 181ms

And Register to application "SUPPLIER" 2s 030ms

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

Hooks

After Hooks.cleanUpAfterTest() 329ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 073ms

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

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

And Verify that user is redirected to registration page 226ms

And Register to application "SUPPLIER" 1s 990ms

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

Hooks

After Hooks.cleanUpAfterTest() 373ms

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

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

And Verify that user is redirected to registration page 156ms

And Register to application "SUPPLIER" 2s 042ms

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

Hooks

After Hooks.cleanUpAfterTest() 382ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 089ms

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

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

And Register to application "SUPPLIER" 2s 156ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 645ms

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

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

And Register to application "SUPPLIER" 2s 263ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 359ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 082ms

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

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

And Register to application "SUPPLIER" 2s 211ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 384ms

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

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

And Register to application "SUPPLIER" 2s 112ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 380ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 082ms

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

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

And Register to application "SUPPLIER" 2s 226ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 334ms

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

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

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-lantmannen" for "apolloautomattest@gmail.com" "CREATE_CARRIER_INVITATION" 255ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 057ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 043ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 035ms

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

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

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

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

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-sempertrans" for "apolloautomattest@gmail.com" "CREATE_CARRIER_INVITATION" 292ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 037ms

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

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

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

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

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

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

And Go to "INVITATIONS_TAB" 188ms

And Accept invitation 15s 782ms

And If user is login then logout 115ms

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

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 273ms

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

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

And Go to "USERS_TAB" 1s 083ms

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

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

And Save user details 536ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 610ms

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

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

And Go to "USERS_TAB" 884ms

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

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

And Save user details 344ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 214ms

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

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

And Go to "USERS_TAB" 915ms

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

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

And Save user details 380ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 332ms

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

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

And Go to "USERS_TAB" 999ms

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

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

And Save user details 525ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 472ms

	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	8m 53s 919ms	Passed

Feature Report