Cucumber-JVM Reports - Feature: Invitation

Project	Number	Date
ApolloFullRunnerReport	develop.309	18 lut 2021, 05:09

	Steps	Scenarios	Features
Invitation	151	0	0	0	0	151	27	0	27	9m 40s 719ms	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 257ms

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

Then Create invitation success alert is displayed 754ms

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

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

Then Create invitation success alert is displayed 264ms

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 "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 917ms

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

Then Create invitation success alert is displayed 209ms

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

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

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

Then Create invitation success alert is displayed 269ms

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

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

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

Then Create invitation success alert is displayed 213ms

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

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

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

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

And Verify that user is redirected to registration page 212ms

And Register to application "SUPPLIER" 1s 887ms

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

Hooks

After Hooks.cleanUpAfterTest() 497ms

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

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

And Verify that user is redirected to registration page 180ms

And Register to application "SUPPLIER" 2s 036ms

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

Hooks

After Hooks.cleanUpAfterTest() 404ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 068ms

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

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

And Verify that user is redirected to registration page 160ms

And Register to application "SUPPLIER" 1s 980ms

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

Hooks

After Hooks.cleanUpAfterTest() 304ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 068ms

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

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

And Verify that user is redirected to registration page 165ms

And Register to application "SUPPLIER" 2s 046ms

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

Hooks

After Hooks.cleanUpAfterTest() 378ms

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

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

And Verify that user is redirected to registration page 145ms

And Register to application "SUPPLIER" 2s 009ms

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

Hooks

After Hooks.cleanUpAfterTest() 362ms

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

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

And Register to application "SUPPLIER" 2s 198ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 386ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 116ms

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

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

And Register to application "SUPPLIER" 2s 145ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 314ms

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

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

And Register to application "SUPPLIER" 2s 195ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 370ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 105ms

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

And Register to application "SUPPLIER" 1s 926ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 415ms

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

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

And Register to application "SUPPLIER" 2s 218ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 346ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 049ms

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

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 032ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 030ms

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

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

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

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

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

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

And Go to "INVITATIONS_TAB" 141ms

And Accept invitation 15s 825ms

And If user is login then logout 090ms

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

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 273ms

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

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

And Go to "USERS_TAB" 996ms

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

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

And Save user details 525ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 401ms

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

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

And Go to "USERS_TAB" 757ms

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

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

And Save user details 340ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 212ms

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

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

And Go to "USERS_TAB" 774ms

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

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

And Save user details 376ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 578ms

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

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

And Go to "USERS_TAB" 1s 018ms

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

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

And Save user details 530ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 495ms

	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 40s 719ms	Passed

Feature Report