Cucumber-JVM Reports - Feature: Invitation

Project	Number	Date
ApolloFullRunnerReport	develop.343	17 mar 2021, 05:04

	Steps	Scenarios	Features
Invitation	193	1	3	0	0	197	30	1	31	8m 27s 240ms	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 262ms

When Go to "INVITATIONS_TAB" 332ms

And Create invitation for "CARRIER" "CARRIER" "automatyy1@test.pl" 882ms

Then Create invitation success alert is displayed 728ms

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

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

When Go to "INVITATIONS_TAB" 196ms

And Create invitation for "CARRIER" "CARRIER" "automatyy2@test.pl" 512ms

Then Create invitation success alert is displayed 277ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 024ms

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

When Go to "INVITATIONS_TAB" 187ms

And Create invitation for "CARRIER" "CARRIER" "automatyy2@test.pl" 483ms

Then Create invitation success alert is displayed 209ms

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

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

When Go to "INVITATIONS_TAB" 192ms

And Create invitation for "CARRIER" "CARRIER" "automatyy2@test.pl" 486ms

Then Create invitation success alert is displayed 264ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 032ms

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

When Go to "INVITATIONS_TAB" 180ms

And Create invitation for "CARRIER" "CARRIER" "automatyy2@test.pl" 461ms

Then Create invitation success alert is displayed 237ms

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

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

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

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

And Verify that user is redirected to registration page 202ms

And Register to application "SUPPLIER" 2s 018ms

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

Hooks

After Hooks.cleanUpAfterTest() 499ms

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

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

And Verify that user is redirected to registration page 183ms

And Register to application "SUPPLIER" 2s 068ms

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

Hooks

After Hooks.cleanUpAfterTest() 413ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 085ms

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

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

And Verify that user is redirected to registration page 195ms

And Register to application "SUPPLIER" 2s 104ms

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

Hooks

After Hooks.cleanUpAfterTest() 313ms

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

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

And Verify that user is redirected to registration page 181ms

And Register to application "SUPPLIER" 2s 075ms

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

Hooks

After Hooks.cleanUpAfterTest() 347ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 073ms

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

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

And Verify that user is redirected to registration page 203ms

And Register to application "SUPPLIER" 1s 846ms

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

Hooks

After Hooks.cleanUpAfterTest() 324ms

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

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

And Register to application "SUPPLIER" 2s 229ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 498ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 132ms

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

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

And Register to application "SUPPLIER" 2s 193ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 321ms

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

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

And Register to application "SUPPLIER" 2s 247ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 358ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 111ms

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

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

And Register to application "SUPPLIER" 2s 134ms

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

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

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

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

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

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

And Register to application "SUPPLIER" 2s 044ms

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

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

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

Hooks

After Hooks.cleanUpAfterTest() 351ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 048ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 024ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 026ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 045ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 024ms

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

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

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

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

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

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

And Go to "INVITATIONS_TAB" 150ms

And Accept invitation 15s 756ms

And If user is login then logout 101ms

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

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 292ms

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

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

And Go to "USERS_TAB" 1s 163ms

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

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

And Save user details 503ms

When Go to "INVITATIONS_TAB" 180ms

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

Then Verify that invitation can't be sent on already used username 096ms

Hooks

After Hooks.cleanUpAfterTest() 1s 508ms

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

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

And Go to "USERS_TAB" 852ms

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

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

And Save user details 297ms

When Go to "INVITATIONS_TAB" 178ms

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 158ms

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

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

And Go to "USERS_TAB" 839ms

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

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

And Save user details 333ms

When Go to "INVITATIONS_TAB" 153ms

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

Then Verify that invitation can't be sent on already used username 087ms

Hooks

After Hooks.cleanUpAfterTest() 1s 887ms

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

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

And Go to "USERS_TAB" 1s 020ms

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

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

And Save user details 480ms

When Go to "INVITATIONS_TAB" 194ms

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

Then Verify that invitation can't be sent on already used username 091ms

Hooks

After Hooks.cleanUpAfterTest() 1s 337ms

@deleteCompanyAfterTest @deleteInvitationAfterTest @NIE_DZIAŁA_PRZEZ_A-7200

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

And Go to "COMPANIES_TAB" 315ms

Given Create company "Firma Alrec" 1s 535ms

When Go to invite to company tab 30s 618ms

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:108)
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() 060ms

After Hooks.deleteInvitationAfterTest() 028ms

@deleteRegistrationAfterTest

Scenario Outline Check if accepted invitation is visible in accepted tab

Steps

Given If user is login then logout 107ms

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

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

And Verify that user is redirected to registration page 201ms

And Register to application "SUPPLIER" 2s 123ms

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

When Go to "INVITATIONS_TAB" 201ms

Then Go to "ACCEPTED_TAB" invitation status tab 106ms

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

Hooks

After Hooks.cleanUpAfterTest() 1s 173ms

@rollbackSettings @deleteInvitationAfterTest

Scenario Outline Check if expired invitation is visible in expired tab

Steps

Given If user is login then logout 079ms

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

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

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

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

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

Then Go to "INVITATIONS_TAB" 184ms

And Go to "EXPIRED_TAB" invitation status tab 090ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 030ms

After Hooks.rollbackSettings() 032ms

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if rejected invitation is visible in rejected tab

Steps

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

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

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

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

Then Go to "INVITATIONS_TAB" 193ms

And Go to invitation details 062ms

Then Reject invitation by button as user 105ms

When If user is login then logout 080ms

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

And Go to "INVITATIONS_TAB" 164ms

And Go to "REJECTED_TAB" invitation status tab 062ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 021ms

After Hooks.cleanUserDetailsAfterTest() 130ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Invitation	193	1	3	0	0	197	30	1	31	8m 27s 240ms	Failed

Feature Report