Cucumber-JVM Reports - Feature: Invitation

Project	Number	Date
ApolloFullRunnerReport	develop-kapibary.320	24 lut 2021, 00:02

	Steps	Scenarios	Features
Invitation	151	0	0	0	0	151	27	0	27	8m 42s 422ms	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 301ms

When Create invitation for "CARRIER" "CARRIER" "automatyy1@test.pl" 999ms

Then Create invitation success alert is displayed 718ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 039ms

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

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

Then Create invitation success alert is displayed 267ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 030ms

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

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

Then Create invitation success alert is displayed 201ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 034ms

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

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

Then Create invitation success alert is displayed 267ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 031ms

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

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

Then Create invitation success alert is displayed 211ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 035ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 088ms

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

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

And Verify that user is redirected to registration page 205ms

And Register to application "SUPPLIER" 1s 990ms

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

Hooks

After Hooks.cleanUpAfterTest() 552ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 087ms

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

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

And Verify that user is redirected to registration page 183ms

And Register to application "SUPPLIER" 1s 871ms

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

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

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

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

And Verify that user is redirected to registration page 161ms

And Register to application "SUPPLIER" 1s 927ms

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

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

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

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

And Verify that user is redirected to registration page 182ms

And Register to application "SUPPLIER" 2s 026ms

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

Hooks

After Hooks.cleanUpAfterTest() 451ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 082ms

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

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

And Verify that user is redirected to registration page 144ms

And Register to application "SUPPLIER" 2s 057ms

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

Hooks

After Hooks.cleanUpAfterTest() 375ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 079ms

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

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

And Register to application "SUPPLIER" 2s 200ms

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

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

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

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

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

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

And Register to application "SUPPLIER" 2s 180ms

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

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

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

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

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

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

And Register to application "SUPPLIER" 1s 965ms

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

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

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

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

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

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

And Register to application "SUPPLIER" 2s 202ms

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

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

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

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

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

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

And Register to application "SUPPLIER" 2s 179ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 376ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 026ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 029ms

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

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

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

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

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-sempertrans" 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" 30s 920ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 032ms

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

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

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

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

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

And Go to "INVITATIONS_TAB" 174ms

And Accept invitation 15s 761ms

And If user is login then logout 108ms

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

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 303ms

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

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

And Go to "USERS_TAB" 1s 146ms

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

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

And Save user details 469ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 430ms

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

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

And Go to "USERS_TAB" 775ms

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

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

And Save user details 320ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 199ms

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

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

And Go to "USERS_TAB" 800ms

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

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

And Save user details 351ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 543ms

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

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

And Go to "USERS_TAB" 1s 011ms

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

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

And Save user details 493ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 359ms

	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 42s 422ms	Passed

Feature Report