Project Number Date
ApolloFullRunnerReport apollo-test-2.48 21 cze 2021, 05:22

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@rollbackSettings 72 1 0 0 0 73 7 1 8 7m 756ms Failed
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Given Login by Api as "super-admin-piast" and get token and expect status "200" 343ms
And Set token of apiUsername "super-admin-piast" 262ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 157ms
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 201ms
Then Login as "super-admin-piast" 6s 804ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 325ms
After Hooks.deleteTransportAfterApiTest() 592ms
After Hooks.rollbackSettings() 001ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Given Login by Api as "super-admin-piast" and get token and expect status "200" 276ms
And Set token of apiUsername "super-admin-piast" 237ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
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 076ms
Then Login as "super-admin-piast" 2s 141ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 319ms
After Hooks.deleteTransportAfterApiTest() 645ms
After Hooks.rollbackSettings() 000ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Given Login by Api as "super-admin-piast" and get token and expect status "200" 303ms
And Set token of apiUsername "super-admin-piast" 254ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
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 141ms
Then Login as "super-admin-piast" 2s 293ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 390ms
After Hooks.deleteTransportAfterApiTest() 637ms
After Hooks.rollbackSettings() 000ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings
Given Set token of apiUsername "super-admin-neuca" 226ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 146ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 027ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 20s 778ms
Then Login as "neuca-admin" 2s 169ms
And Go to "TRANSPORT_TABLE" 481ms
And Confirm statuses until reach "process-ended" 18s 203ms
Then Check if sorting by 'Finished' status is working correctly 267ms
After Hooks.deleteTransportsAfterTest() 2s 116ms
After Hooks.rollbackSettings() 128ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Given Set token of apiUsername "super-admin-piast" 258ms
And Delete invitations with email "automaty31415@test.pl" 013ms
And If user is login then logout 15s 054ms
Given Set token of apiUsername "super-admin-piast" 256ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 128ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 159ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 315ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 969ms
Then Go to "INVITATIONS_TAB" 769ms
And Go to "EXPIRED_TAB" invitation status tab 288ms
Then Invitation is displayed on list "automaty31415@test.pl" 455ms
After Hooks.deleteInvitationAfterTest() 141ms
After Hooks.rollbackSettings() 121ms
View Feature DedicatedWindow
@rollbackSettings
Given Set token of apiUsername "super-admin-skz" 259ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 123ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 290ms
And Prepare setting for automatic time window delete with "super-admin-skz" 200ms
When Login as "swisskrono-admin" 2s 592ms
And Go to "WAREHOUSE_TAB" 907ms
Then Check if dedicated window is deleted from schedule 56s 947ms
After Hooks.rollbackSettings() 283ms
View Feature Move transport to archive
@rollbackSettings @deleteTransportAfterTest
Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 8s 646ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 016ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 132ms
And Set proper delay time to move order to archive after task timeout 126ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 899ms
And Go to "WAREHOUSE_TAB" 1s 090ms
And Change warehouse in schedule to: "Katowice" 1s 634ms
And Wait "60" seconds 1m
And Verify that transport window is grey 082ms
And Verify that transport is in archive 7s 931ms
Then Restore transport from archive 2s 580ms
And Verify that transport has been successfully restored 15s 621ms
After Hooks.deleteTransportAfterTest() 734ms
After Hooks.rollbackSettings() 110ms
View Feature Move transport to archive
@deleteTransportAfterTest @rollbackSettings
Scenario Outline Check if confirming transport status removed it to the archive
Steps
Given Login as "dayco-admin" and set token of apiUsername "super-admin-dayco" 2s 433ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 090ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 134ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 028ms
When Go to "TRANSPORT_TABLE" 402ms
And Click button advice in transport table "OWN_COLLECTION" 1s 434ms
And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 45s 414ms
And Go to "TRANSPORT_TABLE" 445ms
And Find transport in table with status "planned-magazyn-tychy" 3s 693ms
And Confirm statuses until reach "process-ended" 13s 693ms
And Wait "12" seconds 12s
Then Go to "ARCHIVE_TAB" 508ms
And Show "OWN_COLLECTION" 164ms
And Verify that created transport is "true" in transport table 1m 32s 363ms
Error message 
java.lang.AssertionError: expected: but was:
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:834)
	at org.junit.Assert.assertEquals(Assert.java:118)
	at org.junit.Assert.assertEquals(Assert.java:144)
	at CucumberTests._PerformanceTests.TransportTableTest.verifyThatCreatedTransportIsInTransportTable(TransportTableTest.java:116)
	at ✽.Verify that created transport is "true" in transport table(file:Features/Atom/Transport/Archive.feature:51)
After Hooks.deleteTransportAfterTest() 813ms
After Hooks.rollbackSettings() 132ms