Cucumber-JVM Reports - Feature: Invitation

Project	Number	Date
ApolloFullRunnerReport	develop.310	19 lut 2021, 05:06

	Steps	Scenarios	Features
Invitation	151	0	0	0	0	151	27	0	27	8m 41s 802ms	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 262ms

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

Then Create invitation success alert is displayed 816ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 042ms

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

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

Then Create invitation success alert is displayed 252ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 029ms

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

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

Then Create invitation success alert is displayed 256ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 033ms

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

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

Then Create invitation success alert is displayed 267ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 030ms

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

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

Then Create invitation success alert is displayed 196ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 032ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 089ms

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

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

And Verify that user is redirected to registration page 189ms

And Register to application "SUPPLIER" 1s 972ms

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

Hooks

After Hooks.cleanUpAfterTest() 490ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 081ms

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

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

And Verify that user is redirected to registration page 160ms

And Register to application "SUPPLIER" 1s 985ms

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

Hooks

After Hooks.cleanUpAfterTest() 374ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 059ms

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

And Verify that user is redirected to registration page 187ms

And Register to application "SUPPLIER" 2s 022ms

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

Hooks

After Hooks.cleanUpAfterTest() 330ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 079ms

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

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

And Verify that user is redirected to registration page 179ms

And Register to application "SUPPLIER" 2s 063ms

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

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

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

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

And Verify that user is redirected to registration page 212ms

And Register to application "SUPPLIER" 2s 009ms

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

Hooks

After Hooks.cleanUpAfterTest() 361ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 073ms

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

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

And Register to application "SUPPLIER" 2s 570ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 457ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 091ms

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

And Register to application "SUPPLIER" 2s 193ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 334ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 094ms

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

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

And Register to application "SUPPLIER" 2s 187ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 353ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 097ms

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

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

And Register to application "SUPPLIER" 2s 218ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 423ms

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

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

And Register to application "SUPPLIER" 2s 199ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 348ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 088ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 030ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 042ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 046ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 042ms

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

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

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

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

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

And Go to "INVITATIONS_TAB" 162ms

And Accept invitation 15s 786ms

And If user is login then logout 119ms

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

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 269ms

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

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

And Go to "USERS_TAB" 1s 080ms

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

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

And Save user details 562ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 438ms

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

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

And Go to "USERS_TAB" 796ms

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

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

And Save user details 307ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 148ms

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

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

And Go to "USERS_TAB" 807ms

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

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

And Save user details 387ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 470ms

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

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

And Go to "USERS_TAB" 998ms

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

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

And Save user details 507ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 253ms

	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 41s 802ms	Passed

Feature Report