Project Number Date
ApolloFullRunnerReport apollo-test-2.91 23 lip 2021, 04:22

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@rollbackSettings 73 1 4 0 0 78 7 1 8 6m 40s 064ms Failed
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 266ms
And Set token of apiUsername "super-admin-piast" 246ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 239ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 029ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 478ms
Then Login as "super-admin-piast" 8s 281ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 394ms
After Hooks.deleteTransportAfterApiTest() 679ms
After Hooks.rollbackSettings() 003ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 280ms
And Set token of apiUsername "super-admin-piast" 248ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 161ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 025ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 411ms
Then Login as "super-admin-piast" 2s 286ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 373ms
After Hooks.deleteTransportAfterApiTest() 705ms
After Hooks.rollbackSettings() 000ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 262ms
And Set token of apiUsername "super-admin-piast" 243ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 163ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 026ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 515ms
Then Login as "super-admin-piast" 2s 310ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 342ms
After Hooks.deleteTransportAfterApiTest() 676ms
After Hooks.rollbackSettings() 000ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 230ms
And Get custom field settings for "DELIVERY" transport type and "neuca" company 181ms
And Mark custom fields as not obligatory 006ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 132ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 029ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 21s 023ms
Then Login as "neuca-admin" 2s 271ms
And Go to "TRANSPORT_TABLE" 548ms
And Confirm statuses until reach "process-ended" 22s 282ms
Then Check if sorting by 'Finished' status is working correctly 195ms
After Hooks.deleteTransportsAfterTest() 4s 580ms
After Hooks.rollbackAllCustomFieldsSettings() 392ms
After Hooks.rollbackSettings() 154ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Scenario Outline Check if expired invitation is visible in expired tab
Before Hooks.showScenarioName(Scenario) 000ms
Steps
Given Set token of apiUsername "super-admin-piast" 250ms
And Delete invitations with email "automaty31415@test.pl" 013ms
And If user is login then logout 15s 084ms
Given Set token of apiUsername "super-admin-piast" 264ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 117ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 144ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 509ms
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 JQLXL, 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-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION"(file:Features/Atom/Invitations/Invitation.feature:161)
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 000ms
Then Go to "INVITATIONS_TAB" 000ms
And Go to "EXPIRED_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:260)
	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.rollbackSettings() 118ms
View Feature DedicatedWindow
@rollbackSettings
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-skz" 237ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 130ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 349ms
And Prepare setting for automatic time window delete with "super-admin-skz" 223ms
When Login as "swisskrono-admin" 7s 872ms
And Go to "WAREHOUSE_TAB" 945ms
Then Check if dedicated window is deleted from schedule 1m 18s 115ms
After Hooks.rollbackSettings() 283ms
View Feature Move transport to archive
@rollbackSettings @deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 8s 512ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 020ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 147ms
And Set proper delay time to move order to archive after task timeout 118ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 902ms
And Go to "WAREHOUSE_TAB" 965ms
And Change warehouse in schedule to: "Katowice" 1s 670ms
And Wait "60" seconds 1m
And Verify that transport window is grey 077ms
And Verify that transport is in archive 7s 027ms
Then Restore transport from archive 2s 779ms
And Verify that transport has been successfully restored 15s 602ms
After Hooks.deleteTransportAfterTest() 823ms
After Hooks.rollbackSettings() 124ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-dayco" 242ms
And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 112ms
And Mark custom fields as not obligatory 005ms
And Login as "dayco-admin" 2s 140ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 070ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 129ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 032ms
When Go to "TRANSPORT_TABLE" 343ms
And Click button advice in transport table "OWN_COLLECTION" 1s 499ms
And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 45s 588ms
And Go to "TRANSPORT_TABLE" 440ms
And Find transport in table with status "planned-magazyn-tychy" 3s 656ms
And Confirm statuses until reach "process-ended" 16s 553ms
And Wait until transport disappear from transport table 37s 904ms
Then Go to "ARCHIVE_TAB" 506ms
And Show "OWN_COLLECTION" 167ms
And Verify that created transport is "true" in transport table 15s 099ms
After Hooks.deleteTransportAfterTest() 820ms
After Hooks.rollbackAllCustomFieldsSettings() 476ms
After Hooks.rollbackSettings() 139ms