Cucumber-JVM Reports - Feature: Invitation

Project	Number	Date
ApolloFullRunnerReport	develop.321	24 lut 2021, 12:43

	Steps	Scenarios	Features
Invitation	151	0	0	0	0	151	27	0	27	8m 23s 828ms	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 232ms

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

Then Create invitation success alert is displayed 885ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 046ms

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

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

Then Create invitation success alert is displayed 254ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 033ms

@deleteInvitationAfterTest

Scenario Outline Check if it possible to create invitation

Steps

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

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

Then Create invitation success alert is displayed 208ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 038ms

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

Then Create invitation success alert is displayed 266ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 026ms

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

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

Then Create invitation success alert is displayed 208ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 037ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 086ms

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

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

And Verify that user is redirected to registration page 187ms

And Register to application "SUPPLIER" 2s 045ms

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

Hooks

After Hooks.cleanUpAfterTest() 463ms

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

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

And Verify that user is redirected to registration page 180ms

And Register to application "SUPPLIER" 2s 040ms

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

Hooks

After Hooks.cleanUpAfterTest() 427ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 075ms

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

And Verify that user is redirected to registration page 154ms

And Register to application "SUPPLIER" 1s 940ms

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

Hooks

After Hooks.cleanUpAfterTest() 348ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 064ms

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

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

And Verify that user is redirected to registration page 151ms

And Register to application "SUPPLIER" 2s 102ms

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

Hooks

After Hooks.cleanUpAfterTest() 371ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 083ms

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

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

And Verify that user is redirected to registration page 147ms

And Register to application "SUPPLIER" 2s 020ms

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

Hooks

After Hooks.cleanUpAfterTest() 348ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 076ms

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

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

And Register to application "SUPPLIER" 2s 203ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 450ms

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

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

And Register to application "SUPPLIER" 2s 148ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 352ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 090ms

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

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

And Register to application "SUPPLIER" 2s 104ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 378ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 113ms

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

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

And Register to application "SUPPLIER" 2s 081ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 385ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 109ms

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

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

And Register to application "SUPPLIER" 2s 195ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 355ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 039ms

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

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

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-keeeper" 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" 39s 197ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 033ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And Go to "INVITATIONS_TAB" 157ms

And Accept invitation 15s 775ms

And If user is login then logout 118ms

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

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 291ms

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

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

And Go to "USERS_TAB" 1s 110ms

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

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

And Save user details 519ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 586ms

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

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

And Go to "USERS_TAB" 788ms

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

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

And Save user details 328ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 313ms

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

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

And Go to "USERS_TAB" 785ms

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

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

And Save user details 330ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 556ms

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

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

And Go to "USERS_TAB" 1s 067ms

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

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

And Save user details 546ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 446ms

	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 23s 828ms	Passed

Feature Report