Cucumber-JVM Reports - Feature: Invitation

Project	Number	Date
ApolloFullRunnerReport	master.325	08 mar 2021, 20:42

	Steps	Scenarios	Features
Invitation	184	1	3	0	0	188	30	1	31	10m 2s 758ms	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 314ms

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

Then Create invitation success alert is displayed 667ms

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

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

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

Then Create invitation success alert is displayed 271ms

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

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" 1s

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

Then Create invitation success alert is displayed 200ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 028ms

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

Then Create invitation success alert is displayed 200ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 023ms

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

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

Then Create invitation success alert is displayed 207ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 031ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 093ms

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

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

And Verify that user is redirected to registration page 171ms

And Register to application "SUPPLIER" 2s 051ms

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

Hooks

After Hooks.cleanUpAfterTest() 485ms

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

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

And Verify that user is redirected to registration page 167ms

And Register to application "SUPPLIER" 2s 016ms

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

Hooks

After Hooks.cleanUpAfterTest() 423ms

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

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

And Verify that user is redirected to registration page 183ms

And Register to application "SUPPLIER" 2s 018ms

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

Hooks

After Hooks.cleanUpAfterTest() 324ms

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

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

And Verify that user is redirected to registration page 160ms

And Register to application "SUPPLIER" 2s 074ms

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

Hooks

After Hooks.cleanUpAfterTest() 372ms

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

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

And Verify that user is redirected to registration page 157ms

And Register to application "SUPPLIER" 2s 020ms

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

Hooks

After Hooks.cleanUpAfterTest() 354ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 083ms

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

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

And Register to application "SUPPLIER" 2s 110ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 380ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 074ms

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

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

And Register to application "SUPPLIER" 2s 027ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 332ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 110ms

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

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

And Register to application "SUPPLIER" 2s 254ms

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

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

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

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

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

And Register to application "SUPPLIER" 2s 205ms

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

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

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

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

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

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

And Register to application "SUPPLIER" 2s 170ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 344ms

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

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

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

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

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

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 044ms

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

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

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

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

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

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

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

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

And Go to "INVITATIONS_TAB" 159ms

And Accept invitation 15s 805ms

And If user is login then logout 108ms

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

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 316ms

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

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

And Go to "USERS_TAB" 973ms

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

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

And Save user details 487ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 366ms

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

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

And Go to "USERS_TAB" 927ms

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

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

And Save user details 282ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 167ms

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

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

And Go to "USERS_TAB" 885ms

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

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

And Save user details 328ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 427ms

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

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

And Go to "USERS_TAB" 947ms

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

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

And Save user details 515ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 398ms

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

And Go to "COMPANIES_TAB" 300ms

Given Create company "Firma Alrec" 1s 423ms

When Go to invite to company tab 30s 598ms

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() 066ms

After Hooks.deleteInvitationAfterTest() 020ms

@deleteRegistrationAfterTest

Scenario Outline Check if accepted invitation is visible in accepted tab

Steps

Given If user is login then logout 121ms

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

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

And Verify that user is redirected to registration page 189ms

And Register to application "SUPPLIER" 2s 085ms

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

When Go to "INVITATIONS_TAB" 172ms

Then Go to "ACCEPTED_TAB" invitation status tab 063ms

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

Hooks

After Hooks.cleanUpAfterTest() 1s 219ms

@rollbackSettings @deleteInvitationAfterTest

Scenario Outline Check if expired invitation is visible in expired tab

Steps

Given If user is login then logout 089ms

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

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

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

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

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

Then Go to "INVITATIONS_TAB" 162ms

And Go to "EXPIRED_TAB" invitation status tab 051ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 030ms

After Hooks.rollbackSettings() 036ms

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if rejected invitation is visible in rejected tab

Steps

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

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

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

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

Then Go to "INVITATIONS_TAB" 177ms

And Go to invitation details 059ms

Then Reject invitation by button as user 098ms

When If user is login then logout 094ms

Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 2s 111ms

And Go to "INVITATIONS_TAB" 152ms

And Go to "REJECTED_TAB" invitation status tab 052ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 027ms

After Hooks.cleanUserDetailsAfterTest() 141ms

	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	10m 2s 758ms	Failed

Feature Report