Cucumber-JVM Reports - Tag: @deleteInvitationAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.82	16 lip 2021, 06:58

	Steps	Scenarios	Features
@deleteInvitationAfterTest	277	1	9	0	0	287	34	1	35	12m 2s 504ms	Failed

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Check if it possible to create invitation

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 683ms

And Delete invitations with email "automatyy1@test.pl" 021ms

When Go to "INVITATIONS_TAB" 616ms

And Create invitation for "new" user "CARRIER" "CARRIER" "automatyy1@test.pl" "notFromPoland" 2s 634ms

Then Create invitation success alert is displayed 1s 764ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 274ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Check if it possible to create invitation

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 157ms

And Delete invitations with email "automatyy2@test.pl" 015ms

When Go to "INVITATIONS_TAB" 453ms

And Create invitation for "new" user "CARRIER" "CARRIER" "automatyy2@test.pl" "notFromPoland" 2s 449ms

Then Create invitation success alert is displayed 1s 259ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 145ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Check if it possible to create invitation

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 4s 682ms

And Delete invitations with email "automatyy2@test.pl" 014ms

When Go to "INVITATIONS_TAB" 509ms

And Create invitation for "new" user "CARRIER" "CARRIER" "automatyy2@test.pl" "notFromPoland" 2s 531ms

Then Create invitation success alert is displayed 928ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 236ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Check if it possible to create invitation

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 5s 739ms

And Delete invitations with email "automatyy2@test.pl" 013ms

When Go to "INVITATIONS_TAB" 434ms

And Create invitation for "new" user "CARRIER" "CARRIER" "automatyy2@test.pl" "notFromPoland" 2s 512ms

Then Create invitation success alert is displayed 1s 146ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 146ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Check if it possible to create invitation

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 425ms

And Delete invitations with email "automatyy2@test.pl" 015ms

When Go to "INVITATIONS_TAB" 543ms

And Create invitation for "new" user "CARRIER" "CARRIER" "automatyy2@test.pl" "notFromPoland" 2s 596ms

Then Create invitation success alert is displayed 738ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 143ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Check if carrier gets invitation on mail address

Steps

Given Set token of apiUsername "super-admin-skz" 222ms

And Delete invitations with email "apolloautomattest@gmail.com" 014ms

And Create invitation by JSON file "super-admin-skz" for "apolloautomattest@gmail.com" "CREATE_CARRIER_INVITATION" 1s 564ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 190ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Check if carrier gets invitation on mail address

Steps

Given Set token of apiUsername "super-admin-lantmannen" 233ms

And Delete invitations with email "apolloautomattest@gmail.com" 014ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 180ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Check if carrier gets invitation on mail address

Steps

Given Set token of apiUsername "super-admin-keeeper" 235ms

And Delete invitations with email "apolloautomattest@gmail.com" 015ms

And Create invitation by JSON file "super-admin-keeeper" for "apolloautomattest@gmail.com" "CREATE_CARRIER_INVITATION" 1s 711ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 221ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Check if carrier gets invitation on mail address

Steps

Given Set token of apiUsername "super-admin-adama" 240ms

And Delete invitations with email "apolloautomattest@gmail.com" 017ms

And Create invitation by JSON file "super-admin-adama" for "apolloautomattest@gmail.com" "CREATE_CARRIER_INVITATION" 1s 406ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 153ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Check if carrier gets invitation on mail address

Steps

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

And Delete invitations with email "apolloautomattest@gmail.com" 017ms

And Create invitation by JSON file "super-admin-piast" for "apolloautomattest@gmail.com" "CREATE_CARRIER_INVITATION" 1s 411ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 164ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Check if carrier gets invitation on mail address

Steps

Given Set token of apiUsername "super-admin-alrec" 231ms

And Delete invitations with email "apolloautomattest@gmail.com" 014ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 262ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Check if carrier gets invitation on mail address

Steps

Given Set token of apiUsername "super-admin-sempertrans" 235ms

And Delete invitations with email "apolloautomattest@gmail.com" 015ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteInvitationAfterTest() 170ms

View Feature Invitation

@rollbackSettings @deleteInvitationAfterTest

Scenario Outline Check if expired invitation is visible in expired tab

Steps

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

And Delete invitations with email "automaty31415@test.pl" 016ms

And If user is login then logout 273ms

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

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

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

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

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

Then Go to "INVITATIONS_TAB" 496ms

And Go to "EXPIRED_TAB" invitation status tab 244ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 139ms

After Hooks.rollbackSettings() 123ms

View Feature Invitation

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if rejected invitation is visible in rejected tab

Steps

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

And Delete invitations with email "automaty31415@test.pl" 015ms

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

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

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania POST pod adresem /invitations; status: 422, komunikat: [errors:[Niezgodny numer NIP! W platformie istnieje już użytkownik z podanym adresem mailowym (loginem). Jest on przypisany do firmy Piast Cargo Transport Sp. z o.o., NIP: . Prosimy o poprawienie danych.]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:86)
	at CucumberTests.Invitation.RegistrationTest.createInvitationByJSONFile(RegistrationTest.java:64)
	at ✽.Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION"(file:Features/Atom/Invitations/Invitation.feature:174)

When Login as "piast-admin" 000ms

Then Go to "INVITATIONS_TAB" 000ms

And Go to invitation details 000ms

Then Reject invitation by button as user 000ms

When If user is login then logout 000ms

Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 000ms

And Go to "INVITATIONS_TAB" 000ms

And Go to "REJECTED_TAB" invitation status tab 000ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 000ms

Error message

java.lang.NullPointerException
	at CucumberTests.Hooks.deleteInvitationAfterTest(Hooks.java:245)
	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.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	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)

After Hooks.cleanUserDetailsAfterTest() 964ms

View Feature Invitation

@deleteInvitationAfterTest

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" 5s 410ms

And Delete invitations with email "automatyy43@test.pl" 014ms

When Go to "INVITATIONS_TAB" 528ms

And Create invitation for "new" user "CARRIER" "CARRIER" "automatyy43@test.pl" "PL" 2s 466ms

Then Check content of message about invitation "GUSAlert" 1s 440ms

And If user is login then logout 261ms

When Mock invitation email by admin panel "piast-admin" "automatyy43@test.pl" 7s 380ms

And Verify that user is redirected to registration page 469ms

And Fill tax id registration page "notByJSON" 655ms

Then Verify that user is redirected to registration page 165ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 030ms

View Feature Invitation

@deleteInvitationAfterTest

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" 2s 264ms

And Delete invitations with email "automatyy45@test.pl" 012ms

When Go to "INVITATIONS_TAB" 416ms

And Create invitation for "new" user "CARRIER" "CARRIER" "automatyy45@test.pl" "PL" 2s 427ms

Then Check content of message about invitation "GUSAlert" 1s 041ms

And If user is login then logout 222ms

When Mock invitation email by admin panel "lantmannen-admin" "automatyy45@test.pl" 7s 542ms

And Verify that user is redirected to registration page 322ms

And Fill tax id registration page "notByJSON" 610ms

Then Verify that user is redirected to registration page 151ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 029ms

View Feature Invitation

@deleteInvitationAfterTest

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" 2s 445ms

And Delete invitations with email "automatyy46@test.pl" 015ms

When Go to "INVITATIONS_TAB" 467ms

And Create invitation for "new" user "CARRIER" "CARRIER" "automatyy46@test.pl" "PL" 2s 504ms

Then Check content of message about invitation "GUSAlert" 1s 232ms

And If user is login then logout 261ms

When Mock invitation email by admin panel "keeeper-admin" "automatyy46@test.pl" 7s 398ms

And Verify that user is redirected to registration page 449ms

And Fill tax id registration page "notByJSON" 625ms

Then Verify that user is redirected to registration page 155ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 027ms

View Feature Invitation

@deleteInvitationAfterTest

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" 8s 421ms

And Delete invitations with email "automatyy47@test.pl" 012ms

When Go to "INVITATIONS_TAB" 486ms

And Create invitation for "new" user "CARRIER" "CARRIER" "automatyy47@test.pl" "PL" 2s 485ms

Then Check content of message about invitation "GUSAlert" 1s 822ms

And If user is login then logout 275ms

When Mock invitation email by admin panel "neuca-admin" "automatyy47@test.pl" 7s 437ms

And Verify that user is redirected to registration page 272ms

And Fill tax id registration page "notByJSON" 620ms

Then Verify that user is redirected to registration page 151ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 028ms

View Feature Invitation

@deleteInvitationAfterTest

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" 6s 686ms

And Delete invitations with email "automatyy48@test.pl" 016ms

When Go to "INVITATIONS_TAB" 447ms

And Create invitation for "new" user "CARRIER" "CARRIER" "automatyy48@test.pl" "PL" 2s 494ms

Then Check content of message about invitation "GUSAlert" 2s 085ms

And If user is login then logout 217ms

When Mock invitation email by admin panel "farmacol-admin" "automatyy48@test.pl" 7s 501ms

And Verify that user is redirected to registration page 445ms

And Fill tax id registration page "notByJSON" 614ms

Then Verify that user is redirected to registration page 162ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 030ms

View Feature Invitation

@deleteInvitationAfterTest

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

Steps

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

And Delete invitations with email "automatyy99@test.pl" 012ms

And If user is login then logout 15s 065ms

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

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

And Verify that user is redirected to registration page 469ms

And Fill tax id registration page "notbyJSON" 601ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 150ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Check if inviting a person to your company does not require NIP [A-7392]

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 8s 145ms

And Delete invitations with email "aaaa@keeeper.pl" 014ms

When Go to "INVITATIONS_TAB" 509ms

And Go to create invitation form 234ms

And Fill part of invitation page for existed company in Apollo "JOIN_COMPANY" "PRODUCER" "null" "aaaa@keeeper.pl" 1s 138ms

Then Check if NIP is not required to inviting to your company 30s 117ms

When Send invitation 188ms

Then Create invitation success alert is displayed 1s 111ms

And Invitation is displayed on list "aaaa@keeeper.pl" 708ms

Hooks

After Hooks.deleteInvitationAfterTest() 233ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Check if inviting a person to your company does not require NIP [A-7392]

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 9s 644ms

And Delete invitations with email "aaaa@neuca.pl" 015ms

When Go to "INVITATIONS_TAB" 437ms

And Go to create invitation form 211ms

And Fill part of invitation page for existed company in Apollo "JOIN_COMPANY" "WAREHOUSEMAN" "null" "aaaa@neuca.pl" 1s 105ms

Then Check if NIP is not required to inviting to your company 30s 098ms

When Send invitation 182ms

Then Create invitation success alert is displayed 1s 849ms

And Invitation is displayed on list "aaaa@neuca.pl" 745ms

Hooks

After Hooks.deleteInvitationAfterTest() 249ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Check if inviting a person to your company does not require NIP [A-7392]

Steps

Given Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 9s 572ms

And Delete invitations with email "aaaa@farmacol.com.pl" 013ms

When Go to "INVITATIONS_TAB" 487ms

And Go to create invitation form 204ms

And Fill part of invitation page for existed company in Apollo "JOIN_COMPANY" "WAREHOUSE_MANAGER" "null" "aaaa@farmacol.com.pl" 1s 326ms

Then Check if NIP is not required to inviting to your company 30s 097ms

When Send invitation 203ms

Then Create invitation success alert is displayed 2s 009ms

And Invitation is displayed on list "aaaa@farmacol.com.pl" 720ms

Hooks

After Hooks.deleteInvitationAfterTest() 222ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Checking if inviting the user to your company is working correctly [A-7430]

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 569ms

And Delete invitations with email "aaaa@keeeper.pl" 016ms

When Go to "INVITATIONS_TAB" 479ms

And Go to create invitation form 257ms

And Fill part of invitation page for existed company in Apollo "JOIN_COMPANY" "PRODUCER" "null" "aaaa@keeeper.pl" 1s 156ms

When Send invitation 142ms

Then Create invitation success alert is displayed 1s 120ms

And Check content of message about invitation "ownCompany" 171ms

And Invitation is displayed on list "aaaa@keeeper.pl" 597ms

Hooks

After Hooks.deleteInvitationAfterTest() 147ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Checking if inviting the user to your company is working correctly [A-7430]

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 2s 323ms

And Delete invitations with email "aaaa@neuca.pl" 016ms

When Go to "INVITATIONS_TAB" 428ms

And Go to create invitation form 219ms

And Fill part of invitation page for existed company in Apollo "JOIN_COMPANY" "WAREHOUSEMAN" "null" "aaaa@neuca.pl" 1s 082ms

When Send invitation 164ms

Then Create invitation success alert is displayed 1s 673ms

And Check content of message about invitation "ownCompany" 161ms

And Invitation is displayed on list "aaaa@neuca.pl" 599ms

Hooks

After Hooks.deleteInvitationAfterTest() 142ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Checking if inviting the user to your company is working correctly [A-7430]

Steps

Given Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 2s 307ms

And Delete invitations with email "aaaa@farmacol.com.pl" 015ms

When Go to "INVITATIONS_TAB" 468ms

And Go to create invitation form 245ms

And Fill part of invitation page for existed company in Apollo "JOIN_COMPANY" "WAREHOUSE_MANAGER" "null" "aaaa@farmacol.com.pl" 1s 286ms

When Send invitation 182ms

Then Create invitation success alert is displayed 1s 898ms

And Check content of message about invitation "ownCompany" 132ms

And Invitation is displayed on list "aaaa@farmacol.com.pl" 512ms

Hooks

After Hooks.deleteInvitationAfterTest() 141ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Limiting possibility of inviting user to own company - checking mail domain [A-7434]

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 419ms

And Delete invitations with email "abc@keeeper.pl" 013ms

When Go to "INVITATIONS_TAB" 477ms

And Go to create invitation form 246ms

And Fill part of invitation page for existed company in Apollo "JOIN_COMPANY" "PRODUCER" "null" "aaaa@kper.pl" 1s 062ms

When Send invitation 133ms

Then Verify that wrong mail domain alert is displayed 185ms

When Fill part of invitation page for existed company in Apollo "null" "null" "null" "abc@keeeper.pl" 315ms

And Send invitation 132ms

Then Create invitation success alert is displayed 1s 101ms

And Check content of message about invitation "ownCompany" 166ms

And Invitation is displayed on list "abc@keeeper.pl" 588ms

Hooks

After Hooks.deleteInvitationAfterTest() 141ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Limiting possibility of inviting user to own company - checking mail domain [A-7434]

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 2s 292ms

And Delete invitations with email "abcd@neuca.pl" 017ms

When Go to "INVITATIONS_TAB" 435ms

And Go to create invitation form 223ms

And Fill part of invitation page for existed company in Apollo "JOIN_COMPANY" "WAREHOUSEMAN" "null" "aaaa@neeeuca.pl" 1s 317ms

When Send invitation 193ms

Then Verify that wrong mail domain alert is displayed 182ms

When Fill part of invitation page for existed company in Apollo "null" "null" "null" "abcd@neuca.pl" 347ms

And Send invitation 154ms

Then Create invitation success alert is displayed 1s 680ms

And Check content of message about invitation "ownCompany" 131ms

And Invitation is displayed on list "abcd@neuca.pl" 551ms

Hooks

After Hooks.deleteInvitationAfterTest() 239ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Limiting possibility of inviting user to own company - checking mail domain [A-7434]

Steps

Given Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 2s 312ms

And Delete invitations with email "abcde@farmacol.com.pl" 014ms

When Go to "INVITATIONS_TAB" 485ms

And Go to create invitation form 247ms

And Fill part of invitation page for existed company in Apollo "JOIN_COMPANY" "WAREHOUSE_MANAGER" "null" "aaaa@farrrmacol.com.pl" 1s 231ms

When Send invitation 178ms

Then Verify that wrong mail domain alert is displayed 146ms

When Fill part of invitation page for existed company in Apollo "null" "null" "null" "abcde@farmacol.com.pl" 376ms

And Send invitation 134ms

Then Create invitation success alert is displayed 1s 968ms

And Check content of message about invitation "ownCompany" 181ms

And Invitation is displayed on list "abcde@farmacol.com.pl" 595ms

Hooks

After Hooks.deleteInvitationAfterTest() 142ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Check if is always take into account NIP provided in invitation - e-mail address used by another user [A-7390]

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 7s 133ms

And Delete invitations with email "dha1-supplier-2@qa.qa-test" 013ms

When Go to "INVITATIONS_TAB" 491ms

And Create invitation for "new" user "CARRIER" "CARRIER" "dha1-supplier-2@qa.qa-test" "AL" 2s 649ms

Then Check content of message about invitation "incompatibleNIP" 436ms

Hooks

After Hooks.deleteInvitationAfterTest() 028ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Check if is always take into account NIP provided in invitation - e-mail address used by another user [A-7390]

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 4s 962ms

And Delete invitations with email "dha1-supplier-2@qa.qa-test" 014ms

When Go to "INVITATIONS_TAB" 450ms

And Create invitation for "new" user "CARRIER" "CARRIER" "dha1-supplier-2@qa.qa-test" "AL" 2s 557ms

Then Check content of message about invitation "incompatibleNIP" 303ms

Hooks

After Hooks.deleteInvitationAfterTest() 025ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Check if is always take into account NIP provided in invitation - existed NIP in apollo and e-mail address used by another user [A-7390]

Steps

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

And Delete invitations with email "dha1-supplier-2@qa.qa-test" 014ms

When Go to "INVITATIONS_TAB" 465ms

And Go to create invitation form 254ms

And Fill part of invitation page for existed company in Apollo "CARRIER" "CARRIER" "PL" "dha1-supplier-2@qa.qa-test" 2s 215ms

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

When Send invitation 158ms

Then Check content of message about invitation "incompatibleNIP" 432ms

Hooks

After Hooks.deleteInvitationAfterTest() 026ms

View Feature Invitation

@deleteInvitationAfterTest

Scenario Outline Check if is always take into account NIP provided in invitation - existed NIP in apollo and e-mail address used by another user [A-7390]

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 268ms

And Delete invitations with email "dha1-supplier-2@qa.qa-test" 013ms

When Go to "INVITATIONS_TAB" 544ms

And Go to create invitation form 236ms

And Fill part of invitation page for existed company in Apollo "CARRIER" "CARRIER" "PL" "dha1-supplier-2@qa.qa-test" 2s 209ms

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

When Send invitation 134ms

Then Check content of message about invitation "incompatibleNIP" 329ms

Hooks

After Hooks.deleteInvitationAfterTest() 026ms

View Feature Invitation

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it is possible to invite existing user in order to associate him with principal company [A-7315]

Steps

Given Set token of apiUsername "super-admin-alrec" 213ms

And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "automatyy3333@test.pl" by JSON file 1s 619ms

When Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 2s 253ms

And Go to "INVITATIONS_TAB" 508ms

And Create invitation for "existing" user "SUPPLIER" "SUPPLIER" "automatyy3333@test.pl" "PL" 2s 505ms

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 094ms

Hooks

After Hooks.deleteInvitationAfterTest() 029ms

After Hooks.cleanUserDetailsAfterTest() 1s 308ms

View Feature Invitation

@deleteCompanyAfterTest @deleteInvitationAfterTest

Scenario Outline Check if new user can be registered to company existing in different principal space

Steps

Given Login as "super-admin-farmacol" and set token of apiUsername "super-admin-farmacol" 8s 478ms

When Create company "Farmacol-NEU" with given nip "DE" "12344321123" "Dostawca \ Odbiorca" 5s 492ms

And If user is login then logout 230ms

And Login as "super-admin-neuca" 9s 926ms

And Go to "INVITATIONS_TAB" 464ms

And Create invitation with given nip "SUPPLIER" "SUPPLIER" "farmacol-neu@qp.pl" "DE" "12344321123" 2s 567ms

And If user is login then logout 247ms

And Mock invitation email by admin panel "super-admin-neuca" "farmacol-neu@qp.pl" 7s 539ms

And Register to application "SUPPLIER" 19s 141ms

And Wait "4" seconds 4s

And Login as "farmacol-neu@qp.pl" 7s 914ms

And User is successfully logged 048ms

Hooks

After Hooks.deleteCompanyAfterTest() 510ms

After Hooks.deleteInvitationAfterTest() 028ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@deleteInvitationAfterTest	277	1	9	0	0	287	34	1	35	12m 2s 504ms	Failed

Tag Report