Cucumber-JVM Reports - Feature: Invitation

Project	Number	Date
ApolloFullRunnerReport	develop.308	17 lut 2021, 05:08

	Steps	Scenarios	Features
Invitation	151	0	0	0	0	151	27	0	27	9m 21s 923ms	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 221ms

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

Then Create invitation success alert is displayed 842ms

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

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

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

Then Create invitation success alert is displayed 259ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 035ms

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

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

Then Create invitation success alert is displayed 193ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 028ms

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

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

Then Create invitation success alert is displayed 256ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 025ms

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

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

Then Create invitation success alert is displayed 205ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 038ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 131ms

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

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

And Verify that user is redirected to registration page 167ms

And Register to application "SUPPLIER" 1s 789ms

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

Hooks

After Hooks.cleanUpAfterTest() 506ms

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

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

And Verify that user is redirected to registration page 146ms

And Register to application "SUPPLIER" 1s 996ms

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

Hooks

After Hooks.cleanUpAfterTest() 540ms

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

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

And Verify that user is redirected to registration page 157ms

And Register to application "SUPPLIER" 2s 044ms

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

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

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

And Verify that user is redirected to registration page 175ms

And Register to application "SUPPLIER" 2s 044ms

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

Hooks

After Hooks.cleanUpAfterTest() 369ms

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

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

And Verify that user is redirected to registration page 159ms

And Register to application "SUPPLIER" 2s 056ms

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

Hooks

After Hooks.cleanUpAfterTest() 341ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 065ms

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

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

And Register to application "SUPPLIER" 2s 185ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 392ms

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

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

And Register to application "SUPPLIER" 2s 185ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 317ms

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

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

And Register to application "SUPPLIER" 2s 124ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 369ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 092ms

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

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

And Register to application "SUPPLIER" 2s 130ms

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

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

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

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

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

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

And Register to application "SUPPLIER" 2s 192ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 347ms

@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" 14s 132ms

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

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 028ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 050ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 033ms

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

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

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

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

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

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

And Go to "INVITATIONS_TAB" 176ms

And Accept invitation 15s 804ms

And If user is login then logout 110ms

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

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 302ms

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

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

And Go to "USERS_TAB" 1s 088ms

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

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

And Save user details 522ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 500ms

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

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

And Go to "USERS_TAB" 794ms

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

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

And Save user details 321ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 162ms

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

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

And Go to "USERS_TAB" 769ms

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

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

And Save user details 381ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 484ms

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

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

And Go to "USERS_TAB" 1s 006ms

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

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

And Save user details 565ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 497ms

	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 21s 923ms	Passed

Feature Report