Cucumber-JVM Reports - Feature: Invitation

Project	Number	Date
ApolloFullRunnerReport	develop.316	21 lut 2021, 04:24

	Steps	Scenarios	Features
Invitation	151	0	0	0	0	151	27	0	27	8m 49s 359ms	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 224ms

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

Then Create invitation success alert is displayed 761ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 038ms

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

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

Then Create invitation success alert is displayed 262ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 033ms

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

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

Then Create invitation success alert is displayed 209ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 031ms

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

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

Then Create invitation success alert is displayed 267ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 033ms

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

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

Then Create invitation success alert is displayed 204ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 033ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 111ms

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

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

And Verify that user is redirected to registration page 213ms

And Register to application "SUPPLIER" 1s 903ms

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

Hooks

After Hooks.cleanUpAfterTest() 477ms

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

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

And Verify that user is redirected to registration page 175ms

And Register to application "SUPPLIER" 2s 029ms

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

Hooks

After Hooks.cleanUpAfterTest() 375ms

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

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

And Verify that user is redirected to registration page 206ms

And Register to application "SUPPLIER" 1s 769ms

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

Hooks

After Hooks.cleanUpAfterTest() 311ms

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

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

And Verify that user is redirected to registration page 160ms

And Register to application "SUPPLIER" 2s 045ms

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

Hooks

After Hooks.cleanUpAfterTest() 390ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 074ms

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

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

And Verify that user is redirected to registration page 182ms

And Register to application "SUPPLIER" 2s 027ms

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

Hooks

After Hooks.cleanUpAfterTest() 348ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 070ms

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

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

And Register to application "SUPPLIER" 2s 145ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 364ms

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

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

And Register to application "SUPPLIER" 2s 129ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 337ms

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

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

And Register to application "SUPPLIER" 2s 074ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 351ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 099ms

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

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

And Register to application "SUPPLIER" 2s 200ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 405ms

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

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

And Register to application "SUPPLIER" 2s 176ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 373ms

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

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

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-lantmannen" 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" 43s 731ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 036ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 036ms

@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" 32s 365ms

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

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

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-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" 33s 112ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 036ms

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

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

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

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

And Go to "INVITATIONS_TAB" 159ms

And Accept invitation 15s 749ms

And If user is login then logout 113ms

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

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 274ms

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

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

And Go to "USERS_TAB" 1s 091ms

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

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

And Save user details 521ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 369ms

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

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

And Go to "USERS_TAB" 966ms

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

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

And Save user details 310ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 241ms

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

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

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

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

And Save user details 349ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 497ms

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

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

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

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

And Save user details 549ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 544ms

	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 49s 359ms	Passed

Feature Report