Cucumber-JVM Reports - Feature: Invitation

Project	Number	Date
ApolloFullRunnerReport	master.336	06 mar 2021, 05:01

	Steps	Scenarios	Features
Invitation	184	1	3	0	0	188	30	1	31	8m 29s 611ms	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 210ms

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

Then Create invitation success alert is displayed 761ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 037ms

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

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

Then Create invitation success alert is displayed 206ms

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

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

Then Create invitation success alert is displayed 198ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 036ms

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

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

Then Create invitation success alert is displayed 271ms

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 "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 030ms

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

Then Create invitation success alert is displayed 202ms

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

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

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

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

And Verify that user is redirected to registration page 209ms

And Register to application "SUPPLIER" 2s 075ms

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

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

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

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

And Verify that user is redirected to registration page 150ms

And Register to application "SUPPLIER" 1s 966ms

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

Hooks

After Hooks.cleanUpAfterTest() 418ms

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

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

And Verify that user is redirected to registration page 159ms

And Register to application "SUPPLIER" 1s 994ms

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

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

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

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

And Verify that user is redirected to registration page 146ms

And Register to application "SUPPLIER" 2s 084ms

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

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

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

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

And Verify that user is redirected to registration page 167ms

And Register to application "SUPPLIER" 2s 074ms

Then Check if user can be logged "automatyy2871q@test.pl" 3s 082ms

Hooks

After Hooks.cleanUpAfterTest() 414ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 072ms

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

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

And Register to application "SUPPLIER" 2s 186ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 396ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 098ms

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

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

And Register to application "SUPPLIER" 2s 193ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 339ms

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

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

And Register to application "SUPPLIER" 1s 890ms

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

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

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

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

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

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

And Register to application "SUPPLIER" 2s 014ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 411ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 123ms

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

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

And Register to application "SUPPLIER" 2s 160ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 353ms

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

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

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

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 038ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 046ms

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

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

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

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

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

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

And Go to "INVITATIONS_TAB" 156ms

And Accept invitation 15s 744ms

And If user is login then logout 118ms

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

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 310ms

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

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

And Go to "USERS_TAB" 1s 067ms

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

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

And Save user details 483ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 544ms

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

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

And Go to "USERS_TAB" 928ms

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

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

And Save user details 277ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 232ms

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

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

And Go to "USERS_TAB" 908ms

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

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

And Save user details 347ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 512ms

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

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

And Go to "USERS_TAB" 994ms

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

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

And Save user details 544ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 520ms

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

And Go to "COMPANIES_TAB" 339ms

Given Create company "Firma Alrec" 1s 386ms

When Go to invite to company tab 30s 643ms

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

After Hooks.deleteInvitationAfterTest() 024ms

@deleteRegistrationAfterTest

Scenario Outline Check if accepted invitation is visible in accepted tab

Steps

Given If user is login then logout 125ms

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

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

And Verify that user is redirected to registration page 163ms

And Register to application "SUPPLIER" 1s 944ms

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

When Go to "INVITATIONS_TAB" 148ms

Then Go to "ACCEPTED_TAB" invitation status tab 057ms

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

Hooks

After Hooks.cleanUpAfterTest() 1s 359ms

@rollbackSettings @deleteInvitationAfterTest

Scenario Outline Check if expired invitation is visible in expired tab

Steps

Given If user is login then logout 065ms

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

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

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

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

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

Then Go to "INVITATIONS_TAB" 147ms

And Go to "EXPIRED_TAB" invitation status tab 049ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 031ms

After Hooks.rollbackSettings() 024ms

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if rejected invitation is visible in rejected tab

Steps

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

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

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

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

Then Go to "INVITATIONS_TAB" 151ms

And Go to invitation details 052ms

Then Reject invitation by button as user 096ms

When If user is login then logout 085ms

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

And Go to "INVITATIONS_TAB" 136ms

And Go to "REJECTED_TAB" invitation status tab 051ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 028ms

After Hooks.cleanUserDetailsAfterTest() 135ms

	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	8m 29s 611ms	Failed

Feature Report