Cucumber-JVM Reports - Feature: Invitation

Project	Number	Date
ApolloFullRunnerReport	master.338	08 mar 2021, 05:02

	Steps	Scenarios	Features
Invitation	184	1	3	0	0	188	30	1	31	9m 20s 459ms	Failed

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

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

Then Create invitation success alert is displayed 778ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 041ms

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

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

Then Create invitation success alert is displayed 259ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 036ms

@deleteInvitationAfterTest

Scenario Outline Check if it possible to create invitation

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 979ms

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

Then Create invitation success alert is displayed 207ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 035ms

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

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

Then Create invitation success alert is displayed 204ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 028ms

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

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

Then Create invitation success alert is displayed 328ms

And Invitation is displayed on list "automatyy2@test.pl" 4s 952ms

Hooks

After Hooks.deleteInvitationAfterTest() 030ms

@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-skz" for "automatyy15q@test.pl" "CREATE_SUPPLIER_INVITATION" 263ms

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

And Verify that user is redirected to registration page 242ms

And Register to application "SUPPLIER" 1s 845ms

Then Check if user can be logged "automatyy15q@test.pl" 4s 012ms

Hooks

After Hooks.cleanUpAfterTest() 516ms

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

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

And Verify that user is redirected to registration page 157ms

And Register to application "SUPPLIER" 1s 970ms

Then Check if user can be logged "automatyy19q@test.pl" 3s 096ms

Hooks

After Hooks.cleanUpAfterTest() 394ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 071ms

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

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

And Verify that user is redirected to registration page 165ms

And Register to application "SUPPLIER" 2s 004ms

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

Hooks

After Hooks.cleanUpAfterTest() 331ms

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

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

And Verify that user is redirected to registration page 156ms

And Register to application "SUPPLIER" 2s 063ms

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

Hooks

After Hooks.cleanUpAfterTest() 356ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 064ms

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

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

And Verify that user is redirected to registration page 156ms

And Register to application "SUPPLIER" 2s 070ms

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

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

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

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

And Register to application "SUPPLIER" 2s 217ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 379ms

@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-lantmannen" for "automaty27182@test.pl" "CREATE_SUPPLIER_INVITATION" 259ms

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

And Register to application "SUPPLIER" 1s 863ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 319ms

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

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

And Register to application "SUPPLIER" 2s 141ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 341ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 121ms

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

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

And Register to application "SUPPLIER" 2s 186ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 421ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 119ms

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

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

And Register to application "SUPPLIER" 1s 923ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 342ms

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

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

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-lantmannen" 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" 44s 174ms

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-keeeper" 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" 55s 692ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 039ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 031ms

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

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

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

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

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

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

And Go to "INVITATIONS_TAB" 145ms

And Accept invitation 15s 784ms

And If user is login then logout 114ms

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

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 294ms

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

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

And Go to "USERS_TAB" 1s 016ms

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

And Change user details "email" to "apolloautomattest@test.pl" 5s 537ms

And Save user details 505ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 638ms

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

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

And Go to "USERS_TAB" 780ms

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

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

And Save user details 324ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 322ms

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

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

And Go to "USERS_TAB" 771ms

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

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

And Save user details 351ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 521ms

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

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

And Go to "USERS_TAB" 984ms

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

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

And Save user details 506ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 539ms

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

And Go to "COMPANIES_TAB" 442ms

Given Create company "Firma Alrec" 1s 282ms

When Go to invite to company tab 30s 596ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for visibility of element located by By.xpath: //label[@for='invitation-type-select']/following-sibling::div (tried for 30 second(s) with 500 MILLISECONDS interval)
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.checkElementIsVisible(BasePage.java:159)
	at CucumberTests.Company.CompanyInvitationTest.goToInviteToCompanyTab(CompanyInvitationTest.java:22)
	at ✽.Go to invite to company tab(file:Features/Atom/Invitations/Invitation.feature:106)
Caused by: org.openqa.selenium.NoSuchElementException: Cannot locate an element using By.xpath: //label[@for='invitation-type-select']/following-sibling::div
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: driver.version: unknown
	at org.openqa.selenium.support.ui.ExpectedConditions.lambda$findElement$0(ExpectedConditions.java:882)
	at java.util.Optional.orElseThrow(Optional.java:290)
	at org.openqa.selenium.support.ui.ExpectedConditions.findElement(ExpectedConditions.java:881)
	at org.openqa.selenium.support.ui.ExpectedConditions.access$000(ExpectedConditions.java:43)
	at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:205)
	at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:201)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208)
	at Pages.BasePage.checkElementIsVisible(BasePage.java:159)
	at CucumberTests.Company.CompanyInvitationTest.goToInviteToCompanyTab(CompanyInvitationTest.java:22)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaStepDefinition.execute(JavaStepDefinition.java:57)
	at cucumber.runner.PickleStepDefinitionMatch.runStep(PickleStepDefinitionMatch.java:50)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.PickleStepTestStep.run(PickleStepTestStep.java:43)
	at cucumber.runner.TestCase.run(TestCase.java:45)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

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

Then Create invitation success alert is displayed 000ms

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

Hooks

After Hooks.deleteCompanyAfterTest() 073ms

After Hooks.deleteInvitationAfterTest() 015ms

@deleteRegistrationAfterTest

Scenario Outline Check if accepted invitation is visible in accepted tab

Steps

Given If user is login then logout 106ms

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

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

And Verify that user is redirected to registration page 163ms

And Register to application "SUPPLIER" 1s 947ms

Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 228ms

When Go to "INVITATIONS_TAB" 158ms

Then Go to "ACCEPTED_TAB" invitation status tab 037ms

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

Hooks

After Hooks.cleanUpAfterTest() 1s 362ms

@rollbackSettings @deleteInvitationAfterTest

Scenario Outline Check if expired invitation is visible in expired tab

Steps

Given If user is login then logout 077ms

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

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

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

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

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

Then Go to "INVITATIONS_TAB" 150ms

And Go to "EXPIRED_TAB" invitation status tab 055ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 042ms

After Hooks.rollbackSettings() 022ms

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if rejected invitation is visible in rejected tab

Steps

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

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

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

When Login as "piast-admin" 1s 892ms

Then Go to "INVITATIONS_TAB" 143ms

And Go to invitation details 055ms

Then Reject invitation by button as user 100ms

When If user is login then logout 095ms

Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 1s 958ms

And Go to "INVITATIONS_TAB" 155ms

And Go to "REJECTED_TAB" invitation status tab 054ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 027ms

After Hooks.cleanUserDetailsAfterTest() 160ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Invitation	184	1	3	0	0	188	30	1	31	9m 20s 459ms	Failed

Feature Report