Cucumber-JVM Reports - Feature: Invitation

Project	Number	Date
ApolloFullRunnerReport	after_release_3_6_0.315	23 lut 2021, 00:04

	Steps	Scenarios	Features
Invitation	188	0	0	0	0	188	31	0	31	10m 25s 663ms	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 752ms

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

Then Create invitation success alert is displayed 1s 090ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 064ms

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

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

Then Create invitation success alert is displayed 418ms

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

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" 1s 278ms

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

Then Create invitation success alert is displayed 193ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 042ms

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

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

Then Create invitation success alert is displayed 250ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 040ms

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

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

Then Create invitation success alert is displayed 304ms

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

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

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

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

And Verify that user is redirected to registration page 374ms

And Register to application "SUPPLIER" 2s 369ms

Then Check if user can be logged "automatyy15q@test.pl" 5s 834ms

Hooks

After Hooks.cleanUpAfterTest() 1s 070ms

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

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

And Verify that user is redirected to registration page 166ms

And Register to application "SUPPLIER" 2s 345ms

Then Check if user can be logged "automatyy19q@test.pl" 4s 671ms

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

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

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

And Verify that user is redirected to registration page 390ms

And Register to application "SUPPLIER" 2s 241ms

Then Check if user can be logged "automatyy2545q@test.pl" 3s 563ms

Hooks

After Hooks.cleanUpAfterTest() 383ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 100ms

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

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

And Verify that user is redirected to registration page 353ms

And Register to application "SUPPLIER" 2s 212ms

Then Check if user can be logged "automatyy287q@test.pl" 4s 047ms

Hooks

After Hooks.cleanUpAfterTest() 624ms

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

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

And Verify that user is redirected to registration page 247ms

And Register to application "SUPPLIER" 2s 369ms

Then Check if user can be logged "automatyy2871q@test.pl" 3s 486ms

Hooks

After Hooks.cleanUpAfterTest() 543ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 080ms

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

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

And Register to application "SUPPLIER" 2s 470ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 667ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 117ms

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

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

And Register to application "SUPPLIER" 2s 547ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 500ms

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

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

And Register to application "SUPPLIER" 2s 559ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 418ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 138ms

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

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

And Register to application "SUPPLIER" 2s 677ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 491ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 122ms

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

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

And Register to application "SUPPLIER" 2s 488ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 374ms

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

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 037ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 045ms

@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" 43s 854ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 051ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 056ms

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

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

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

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

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

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

And Go to "INVITATIONS_TAB" 212ms

And Accept invitation 16s 334ms

And If user is login then logout 114ms

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

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 322ms

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

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

And Go to "USERS_TAB" 1s 479ms

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

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

And Save user details 700ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 2s 154ms

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

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

And Go to "USERS_TAB" 1s 157ms

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

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

And Save user details 496ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 843ms

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

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

And Go to "USERS_TAB" 1s 037ms

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

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

And Save user details 373ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 2s 176ms

@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" 3s 559ms

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

And Go to "USERS_TAB" 1s 362ms

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

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

And Save user details 639ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 704ms

@deleteCompanyAfterTest @deleteInvitationAfterTest

Scenario Outline Check if possible to create invitation to company by "Invite+" in company tab

Steps

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

And Go to "COMPANIES_TAB" 466ms

Given Create company "Firma Alrec" 1s 690ms

When Go to invite to company tab 141ms

And Create invitation to company for "automaty10@o2.pl" 206ms

Then Create invitation success alert is displayed 370ms

And Invitation is displayed on list "automaty10@o2.pl" 181ms

Hooks

After Hooks.deleteCompanyAfterTest() 082ms

After Hooks.deleteInvitationAfterTest() 039ms

@deleteRegistrationAfterTest

Scenario Outline Check if accepted invitation is visible in accepted tab

Steps

Given If user is login then logout 086ms

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

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

And Verify that user is redirected to registration page 141ms

And Register to application "SUPPLIER" 2s 381ms

Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 3s 222ms

When Go to "INVITATIONS_TAB" 221ms

Then Go to "ACCEPTED_TAB" invitation status tab 070ms

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

Hooks

After Hooks.cleanUpAfterTest() 1s 573ms

@rollbackSettings @deleteInvitationAfterTest

Scenario Outline Check if expired invitation is visible in expired tab

Steps

Given If user is login then logout 093ms

Given Set token of apiUsername "super-admin-piast" 180ms

And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 078ms

Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 499ms

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

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

Then Go to "INVITATIONS_TAB" 183ms

And Go to "EXPIRED_TAB" invitation status tab 049ms

Then Invitation is displayed on list "automaty31415@test.pl" 105ms

Hooks

After Hooks.deleteInvitationAfterTest() 025ms

After Hooks.rollbackSettings() 027ms

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if rejected invitation is visible in rejected tab

Steps

Given Set token of apiUsername "super-admin-piast" 085ms

And Prepare user "piast-admin" details with all notifications and "automaty31415@test.pl" by JSON file 214ms

Then Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 332ms

When Login as "piast-admin" 2s 604ms

Then Go to "INVITATIONS_TAB" 214ms

And Go to invitation details 062ms

Then Reject invitation by button as user 106ms

When If user is login then logout 070ms

Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 3s 266ms

And Go to "INVITATIONS_TAB" 175ms

And Go to "REJECTED_TAB" invitation status tab 051ms

Then Invitation is displayed on list "automaty31415@test.pl" 104ms

Hooks

After Hooks.deleteInvitationAfterTest() 030ms

After Hooks.cleanUserDetailsAfterTest() 186ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Invitation	188	0	0	0	0	188	31	0	31	10m 25s 663ms	Passed

Feature Report