Cucumber-JVM Reports - Feature: Invitation

Project	Number	Date
ApolloFullRunnerReport	develop.376	11 kwi 2021, 05:27

	Steps	Scenarios	Features
Invitation	244	6	14	0	0	264	33	6	39	14m 55s 100ms	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 238ms

When Go to "INVITATIONS_TAB" 383ms

And Create invitation for "CARRIER" "CARRIER" "automatyy1@test.pl" "notFromPoland" 1s 491ms

Then Create invitation success alert is displayed 786ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 035ms

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

When Go to "INVITATIONS_TAB" 196ms

And Create invitation for "CARRIER" "CARRIER" "automatyy2@test.pl" "notFromPoland" 1s 168ms

Then Create invitation success alert is displayed 255ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 050ms

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

When Go to "INVITATIONS_TAB" 177ms

And Create invitation for "CARRIER" "CARRIER" "automatyy2@test.pl" "notFromPoland" 1s 133ms

Then Create invitation success alert is displayed 211ms

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

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

When Go to "INVITATIONS_TAB" 181ms

And Create invitation for "CARRIER" "CARRIER" "automatyy2@test.pl" "notFromPoland" 1s 116ms

Then Create invitation success alert is displayed 267ms

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

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

When Go to "INVITATIONS_TAB" 181ms

And Create invitation for "CARRIER" "CARRIER" "automatyy2@test.pl" "notFromPoland" 1s 119ms

Then Create invitation success alert is displayed 211ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 032ms

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

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

And Fill tax id registration page "byJSON" 384ms

And Verify that user is redirected to registration page 089ms

And Register to application "SUPPLIER" 1s 284ms

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

Hooks

After Hooks.cleanUpAfterTest() 527ms

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

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

And Fill tax id registration page "byJSON" 356ms

And Verify that user is redirected to registration page 087ms

And Register to application "SUPPLIER" 1s 510ms

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

Hooks

After Hooks.cleanUpAfterTest() 435ms

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

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

And Fill tax id registration page "byJSON" 371ms

And Verify that user is redirected to registration page 093ms

And Register to application "SUPPLIER" 1s 559ms

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

Hooks

After Hooks.cleanUpAfterTest() 416ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 070ms

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

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

And Fill tax id registration page "byJSON" 387ms

And Verify that user is redirected to registration page 094ms

And Register to application "SUPPLIER" 1s 310ms

Then Check if user can be logged "automatyy287q@test.pl" 3s 299ms

Hooks

After Hooks.cleanUpAfterTest() 456ms

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

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

And Fill tax id registration page "byJSON" 370ms

And Verify that user is redirected to registration page 092ms

And Register to application "SUPPLIER" 1s 552ms

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

Hooks

After Hooks.cleanUpAfterTest() 357ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 068ms

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

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

And Fill tax id registration page "byJSON" 370ms

And Register to application "SUPPLIER" 1s 558ms

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

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

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

Error message

java.lang.AssertionError: Użytkownik nie został przeniesiony do podstrony zaproszenia!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Invitation.InvitationTest.verifyThatUserIsRedirectedToInvitationPage(InvitationTest.java:65)
	at ✽.Verify that user is redirected to invitation page "automaty31415@test.pl"(file:Features/Atom/Invitations/Invitation.feature:44)

Hooks

After Hooks.cleanUpAfterTest() 379ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 15s 022ms

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

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

And Fill tax id registration page "byJSON" 379ms

And Register to application "SUPPLIER" 1s 410ms

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

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

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

Error message

java.lang.AssertionError: Użytkownik nie został przeniesiony do podstrony zaproszenia!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Invitation.InvitationTest.verifyThatUserIsRedirectedToInvitationPage(InvitationTest.java:65)
	at ✽.Verify that user is redirected to invitation page "automaty27182@test.pl"(file:Features/Atom/Invitations/Invitation.feature:44)

Hooks

After Hooks.cleanUpAfterTest() 320ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 15s 029ms

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

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

And Fill tax id registration page "byJSON" 378ms

And Register to application "SUPPLIER" 1s 397ms

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

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: Nie udalo sie poprawnie zalogowac automaty6022@test.pl (tried for 20 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:166)
	at Pages.LoginPage.loginAs(LoginPage.java:38)
	at CucumberTests.BaseTest.loginAs(BaseTest.java:101)
	at CucumberTests.LoginTest.loginAsAndSetTokenOfApiUsername(LoginTest.java:72)
	at ✽.Login as "automaty6022@test.pl" and set token of apiUsername "super-admin-keeeper"(file:Features/Atom/Invitations/Invitation.feature:42)
Caused by: org.openqa.selenium.NoSuchElementException: Cannot locate an element using By.xpath: //a[text()='Logout'] | //a[text()='Wyloguj']
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:166)
	at Pages.LoginPage.loginAs(LoginPage.java:38)
	at CucumberTests.BaseTest.loginAs(BaseTest.java:101)
	at CucumberTests.LoginTest.loginAsAndSetTokenOfApiUsername(LoginTest.java:72)
	at sun.reflect.GeneratedMethodAccessor204.invoke(Unknown Source)
	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)

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 562ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 15s 035ms

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

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

And Fill tax id registration page "byJSON" 367ms

And Register to application "SUPPLIER" 1s 548ms

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

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

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

Error message

java.lang.AssertionError: Użytkownik nie został przeniesiony do podstrony zaproszenia!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Invitation.InvitationTest.verifyThatUserIsRedirectedToInvitationPage(InvitationTest.java:65)
	at ✽.Verify that user is redirected to invitation page "automaty666@test.pl"(file:Features/Atom/Invitations/Invitation.feature:44)

Hooks

After Hooks.cleanUpAfterTest() 384ms

@deleteRegistrationAfterTest

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

Steps

Given If user is login then logout 15s 044ms

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

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

And Fill tax id registration page "byJSON" 392ms

And Register to application "SUPPLIER" 1s 600ms

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

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: Nie udalo sie poprawnie zalogowac automaty2871q@test.pl (tried for 20 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:166)
	at Pages.LoginPage.loginAs(LoginPage.java:38)
	at CucumberTests.BaseTest.loginAs(BaseTest.java:101)
	at CucumberTests.LoginTest.loginAsAndSetTokenOfApiUsername(LoginTest.java:72)
	at ✽.Login as "automaty2871q@test.pl" and set token of apiUsername "super-admin-alrec"(file:Features/Atom/Invitations/Invitation.feature:42)
Caused by: org.openqa.selenium.NoSuchElementException: Cannot locate an element using By.xpath: //a[text()='Logout'] | //a[text()='Wyloguj']
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:166)
	at Pages.LoginPage.loginAs(LoginPage.java:38)
	at CucumberTests.BaseTest.loginAs(BaseTest.java:101)
	at CucumberTests.LoginTest.loginAsAndSetTokenOfApiUsername(LoginTest.java:72)
	at sun.reflect.GeneratedMethodAccessor204.invoke(Unknown Source)
	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)

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

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

Hooks

After Hooks.cleanUpAfterTest() 1s 543ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 042ms

@deleteInvitationAfterTest

Scenario Outline Check if carrier gets invitation on mail address

Steps

And Create invitation by JSON file "super-admin-lantmannen" for "apolloautomattest@gmail.com" "CREATE_CARRIER_INVITATION" 851ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 052ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 047ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 033ms

@deleteInvitationAfterTest

Scenario Outline Check if carrier gets invitation on mail address

Steps

And Create invitation by JSON file "super-admin-alrec" for "apolloautomattest@gmail.com" "CREATE_CARRIER_INVITATION" 259ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 035ms

@deleteInvitationAfterTest

Scenario Outline Check if carrier gets invitation on mail address

Steps

And Create invitation by JSON file "super-admin-sempertrans" for "apolloautomattest@gmail.com" "CREATE_CARRIER_INVITATION" 305ms

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

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

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

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

Error message

java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <422>.

	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:59)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:238)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy:175)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:64)
	at CucumberTests.Invitation.RegistrationTest.createInvitationByJSONFile(RegistrationTest.java:59)
	at ✽.Create invitation by JSON file "super-admin-farmacol" for "automaty314153@test.pl" "CREATE_SUPPLIER_INVITATION"(file:Features/Atom/Invitations/Invitation.feature:72)

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

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

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

And Go to "INVITATIONS_TAB" 000ms

And Accept invitation 000ms

And If user is login then logout 000ms

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

And Verify if user has visible "no waiting" invitation 000ms

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 237ms

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

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

And Go to "USERS_TAB" 1s 230ms

And Find user "automaty1591qa@test.pl" 2s 249ms

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

And Save user details 563ms

When Go to "INVITATIONS_TAB" 146ms

And Create invitation for "CARRIER" "CARRIER" "automaty1591qa@test.pl" "notFromPoland" 1s 101ms

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

Hooks

After Hooks.cleanUpAfterTest() 1s 873ms

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

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

And Go to "USERS_TAB" 798ms

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

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

And Save user details 357ms

When Go to "INVITATIONS_TAB" 150ms

And Create invitation for "CARRIER" "CARRIER" "automaty1231qa@test.pl" "notFromPoland" 1s 080ms

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

Hooks

After Hooks.cleanUpAfterTest() 1s 215ms

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

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

And Go to "USERS_TAB" 823ms

And Find user "automaty9231qa@test.pl" 2s 266ms

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

And Save user details 403ms

When Go to "INVITATIONS_TAB" 200ms

And Create invitation for "CARRIER" "CARRIER" "automaty9231qa@test.pl" "notFromPoland" 1s 141ms

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

Hooks

After Hooks.cleanUpAfterTest() 1s 390ms

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

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

And Go to "USERS_TAB" 1s 041ms

And Find user "automaty7221qa@test.pl" 2s 262ms

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

And Save user details 518ms

When Go to "INVITATIONS_TAB" 194ms

And Create invitation for "CARRIER" "CARRIER" "automaty7221qa@test.pl" "notFromPoland" 1s 152ms

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

Hooks

After Hooks.cleanUpAfterTest() 1s 605ms

@deleteRegistrationAfterTest

Scenario Outline Check if accepted invitation is visible in accepted tab

Steps

Given If user is login then logout 070ms

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

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

And Verify that user is redirected to registration page 190ms

And Fill tax id registration page "byJSON" 206ms

And Register to application "SUPPLIER" 1s 607ms

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

When Go to "INVITATIONS_TAB" 183ms

Then Go to "ACCEPTED_TAB" invitation status tab 094ms

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

Hooks

After Hooks.cleanUpAfterTest() 1s 229ms

@rollbackSettings @deleteInvitationAfterTest

Scenario Outline Check if expired invitation is visible in expired tab

Steps

Given If user is login then logout 075ms

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

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

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

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

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

Then Go to "INVITATIONS_TAB" 186ms

And Go to "EXPIRED_TAB" invitation status tab 067ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 022ms

After Hooks.rollbackSettings() 030ms

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if rejected invitation is visible in rejected tab

Steps

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

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

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

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

Then Go to "INVITATIONS_TAB" 167ms

And Go to invitation details 055ms

Then Reject invitation by button as user 218ms

When If user is login then logout 075ms

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

And Go to "INVITATIONS_TAB" 153ms

And Go to "REJECTED_TAB" invitation status tab 093ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 023ms

After Hooks.cleanUserDetailsAfterTest() 162ms

@deleteRegistrationAfterTest

Scenario Outline Check if new company from Poland is correctly verified in GUS [A-7282]

Steps

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

When Go to "INVITATIONS_TAB" 184ms

And Create invitation for "CARRIER" "CARRIER" "automatyy4@test.pl" "PL" 1s 169ms

Then Check if company has been verified by GUS 861ms

When Mock invitation email by admin panel "piast-admin" "automatyy4@test.pl" 5s 609ms

And Verify that user is redirected to registration page 201ms

And Fill tax id registration page "notByJSON" 199ms

Then Verify that user is redirected to registration page 089ms

And Check if data from GUS are automatically completed 2s 078ms

Hooks

After Hooks.cleanUpAfterTest() 001ms

@deleteRegistrationAfterTest

Scenario Outline Check if new company from Poland is correctly verified in GUS [A-7282]

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 050ms

When Go to "INVITATIONS_TAB" 200ms

And Create invitation for "CARRIER" "CARRIER" "automatyy4@test.pl" "PL" 1s 192ms

Then Check if company has been verified by GUS 231ms

When Mock invitation email by admin panel "lantmannen-admin" "automatyy4@test.pl" 5s 521ms

And Verify that user is redirected to registration page 175ms

And Fill tax id registration page "notByJSON" 207ms

Then Verify that user is redirected to registration page 087ms

And Check if data from GUS are automatically completed 2s 087ms

Hooks

After Hooks.cleanUpAfterTest() 001ms

@deleteRegistrationAfterTest

Scenario Outline Check if new company from Poland is correctly verified in GUS [A-7282]

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 112ms

When Go to "INVITATIONS_TAB" 204ms

And Create invitation for "CARRIER" "CARRIER" "automatyy4@test.pl" "PL" 1s 091ms

Then Check if company has been verified by GUS 228ms

When Mock invitation email by admin panel "keeeper-admin" "automatyy4@test.pl" 5s 389ms

And Verify that user is redirected to registration page 130ms

And Fill tax id registration page "notByJSON" 263ms

Then Verify that user is redirected to registration page 088ms

And Check if data from GUS are automatically completed 2s 086ms

Hooks

After Hooks.cleanUpAfterTest() 001ms

@deleteRegistrationAfterTest

Scenario Outline Check if new company from Poland is correctly verified in GUS [A-7282]

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 1s 008ms

When Go to "INVITATIONS_TAB" 180ms

And Create invitation for "CARRIER" "CARRIER" "automatyy4@test.pl" "PL" 1s 227ms

Then Check if company has been verified by GUS 395ms

When Mock invitation email by admin panel "neuca-admin" "automatyy4@test.pl" 5s 493ms

And Verify that user is redirected to registration page 143ms

And Fill tax id registration page "notByJSON" 231ms

Then Verify that user is redirected to registration page 088ms

And Check if data from GUS are automatically completed 2s 095ms

Hooks

After Hooks.cleanUpAfterTest() 000ms

@deleteRegistrationAfterTest

Scenario Outline Check if new company from Poland is correctly verified in GUS [A-7282]

Steps

Given Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 184ms

When Go to "INVITATIONS_TAB" 187ms

And Create invitation for "CARRIER" "CARRIER" "automatyy4@test.pl" "PL" 1s 257ms

Then Check if company has been verified by GUS 414ms

When Mock invitation email by admin panel "farmacol-admin" "automatyy4@test.pl" 5s 481ms

And Verify that user is redirected to registration page 188ms

And Fill tax id registration page "notByJSON" 219ms

Then Verify that user is redirected to registration page 087ms

And Check if data from GUS are automatically completed 2s 087ms

Hooks

After Hooks.cleanUpAfterTest() 001ms

@deleteInvitationAfterTest

Scenario Outline Check if the registrant provided a non-compliant NIP, the appropriate message will be displayed [A-7285]

Steps

Given If user is login then logout 15s 041ms

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

When Mock invitation email by admin panel "super-admin-piast" "automatyy99@test.pl" 20s 415ms

And Verify that user is redirected to registration page 197ms

And Fill tax id registration page "notbyJSON" 229ms

Then Check if non-compliant NIP message is displayed 2s 038ms

Hooks

After Hooks.deleteInvitationAfterTest() 029ms

Scenario Outline Check if the new company for the principal, but existed in apollo is suggest correctly [A-7283]

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 136ms

When Go to "INVITATIONS_TAB" 198ms

And Fill part of invitation page for existed company in Apollo "CARRIER" "CARRIER" "PL" 1s 022ms

Then Check if company existed in apollo is suggest correctly 841ms

Scenario Outline Check if the new company for the principal, but existed in apollo is suggest correctly [A-7283]

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 955ms

When Go to "INVITATIONS_TAB" 170ms

And Fill part of invitation page for existed company in Apollo "SUPPLIER" "SUPPLIER" "PL" 986ms

Then Check if company existed in apollo is suggest correctly 103ms

Scenario Outline Check if the new company for the principal, but existed in apollo is suggest correctly [A-7283]

Steps

Given Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 091ms

When Go to "INVITATIONS_TAB" 177ms

And Fill part of invitation page for existed company in Apollo "CARRIER" "CARRIER" "PL" 920ms

Then Check if company existed in apollo is suggest correctly 121ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Invitation	244	6	14	0	0	264	33	6	39	14m 55s 100ms	Failed

Feature Report