Cucumber-JVM Reports - Feature: Invitation

Project	Number	Date
ApolloFullRunnerReport	master.333	05 mar 2021, 05:03

	Steps	Scenarios	Features
Invitation	184	1	3	0	0	188	30	1	31	9m 47s 115ms	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 228ms

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

Then Create invitation success alert is displayed 832ms

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

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

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

Then Create invitation success alert is displayed 262ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 035ms

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

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

Then Create invitation success alert is displayed 206ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 024ms

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

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

Then Create invitation success alert is displayed 269ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 031ms

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

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

Then Create invitation success alert is displayed 198ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 053ms

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

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

And Verify that user is redirected to registration page 217ms

And Register to application "SUPPLIER" 2s 055ms

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

Hooks

After Hooks.cleanUpAfterTest() 555ms

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

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

And Verify that user is redirected to registration page 195ms

And Register to application "SUPPLIER" 2s 056ms

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

Hooks

After Hooks.cleanUpAfterTest() 430ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 072ms

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

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

And Verify that user is redirected to registration page 175ms

And Register to application "SUPPLIER" 2s 080ms

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

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

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

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

And Verify that user is redirected to registration page 172ms

And Register to application "SUPPLIER" 2s 063ms

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

Hooks

After Hooks.cleanUpAfterTest() 411ms

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

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

And Verify that user is redirected to registration page 178ms

And Register to application "SUPPLIER" 2s 006ms

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

Hooks

After Hooks.cleanUpAfterTest() 436ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 073ms

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

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

And Register to application "SUPPLIER" 2s 145ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 427ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 081ms

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

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

And Register to application "SUPPLIER" 2s 195ms

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

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

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

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

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

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

And Register to application "SUPPLIER" 2s 247ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 346ms

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

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

And Register to application "SUPPLIER" 2s 012ms

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

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

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

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

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

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

And Register to application "SUPPLIER" 2s 181ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 390ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 063ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 051ms

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

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

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

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 028ms

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

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

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

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

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

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

And Go to "INVITATIONS_TAB" 182ms

And Accept invitation 15s 785ms

And If user is login then logout 114ms

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

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 285ms

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

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

And Go to "USERS_TAB" 1s 171ms

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

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

And Save user details 508ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 400ms

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

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

And Go to "USERS_TAB" 799ms

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

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

And Save user details 321ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 248ms

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

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

And Go to "USERS_TAB" 793ms

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

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

And Save user details 417ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 838ms

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

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

And Go to "USERS_TAB" 998ms

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

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

And Save user details 525ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 517ms

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

And Go to "COMPANIES_TAB" 325ms

Given Create company "Firma Alrec" 1s 321ms

When Go to invite to company tab 30s 563ms

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

After Hooks.deleteInvitationAfterTest() 023ms

@deleteRegistrationAfterTest

Scenario Outline Check if accepted invitation is visible in accepted tab

Steps

Given If user is login then logout 088ms

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

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

And Verify that user is redirected to registration page 158ms

And Register to application "SUPPLIER" 2s 056ms

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

When Go to "INVITATIONS_TAB" 164ms

Then Go to "ACCEPTED_TAB" invitation status tab 045ms

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

Hooks

After Hooks.cleanUpAfterTest() 1s 291ms

@rollbackSettings @deleteInvitationAfterTest

Scenario Outline Check if expired invitation is visible in expired tab

Steps

Given If user is login then logout 081ms

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

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

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

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

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

Then Go to "INVITATIONS_TAB" 157ms

And Go to "EXPIRED_TAB" invitation status tab 054ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 032ms

After Hooks.rollbackSettings() 041ms

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

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

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

Then Go to "INVITATIONS_TAB" 162ms

And Go to invitation details 063ms

Then Reject invitation by button as user 098ms

When If user is login then logout 100ms

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

And Go to "INVITATIONS_TAB" 147ms

And Go to "REJECTED_TAB" invitation status tab 050ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 030ms

After Hooks.cleanUserDetailsAfterTest() 156ms

	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 47s 115ms	Failed

Feature Report