Project Number Date
ApolloFullRunnerReport apollo-test-2.47 20 cze 2021, 05:08

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@rollbackSettings 68 2 3 0 0 73 6 2 8 7m 4s 195ms Failed
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Given Login by Api as "super-admin-piast" and get token and expect status "200" 282ms
And Set token of apiUsername "super-admin-piast" 244ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 170ms
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 100ms
Then Login as "super-admin-piast" 6s 712ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 614ms
After Hooks.deleteTransportAfterApiTest() 606ms
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" 274ms
And Set token of apiUsername "super-admin-piast" 242ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 156ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 027ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 168ms
Then Login as "super-admin-piast" 2s 304ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 398ms
After Hooks.deleteTransportAfterApiTest() 675ms
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" 247ms
And Set token of apiUsername "super-admin-piast" 232ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 138ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 027ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 144ms
Then Login as "super-admin-piast" 2s 293ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 375ms
After Hooks.deleteTransportAfterApiTest() 624ms
After Hooks.rollbackSettings() 000ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings
Given Set token of apiUsername "super-admin-neuca" 214ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 118ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 025ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 20s 386ms
Then Login as "neuca-admin" 2s 195ms
And Go to "TRANSPORT_TABLE" 482ms
And Confirm statuses until reach "process-ended" 18s 366ms
Then Check if sorting by 'Finished' status is working correctly 300ms
After Hooks.deleteTransportsAfterTest() 2s 385ms
After Hooks.rollbackSettings() 126ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Given Set token of apiUsername "super-admin-piast" 218ms
And Delete invitations with email "automaty31415@test.pl" 012ms
And If user is login then logout 15s 060ms
Given Set token of apiUsername "super-admin-piast" 237ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 138ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 151ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 314ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 773ms
Then Go to "INVITATIONS_TAB" 731ms
And Go to "EXPIRED_TAB" invitation status tab 307ms
Then Invitation is displayed on list "automaty31415@test.pl" 439ms
After Hooks.deleteInvitationAfterTest() 138ms
After Hooks.rollbackSettings() 127ms
View Feature DedicatedWindow
@rollbackSettings
Given Set token of apiUsername "super-admin-skz" 280ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 129ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 302ms
And Prepare setting for automatic time window delete with "super-admin-skz" 219ms
When Login as "swisskrono-admin" 2s 548ms
And Go to "WAREHOUSE_TAB" 860ms
Then Check if dedicated window is deleted from schedule 1m 27s 134ms
After Hooks.rollbackSettings() 205ms
View Feature Move transport to archive
@rollbackSettings @deleteTransportAfterTest
Scenario Outline Check if delayed transport is moved to archived and can be restored
Steps
Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 8s 213ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 017ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 150ms
And Set proper delay time to move order to archive after task timeout 129ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 894ms
And Go to "WAREHOUSE_TAB" 960ms
And Change warehouse in schedule to: "Katowice" 1s 491ms
And Wait "60" seconds 1m
And Verify that transport window is grey 083ms
Error message 
java.lang.AssertionError: Okno zlecenia nie zrobiło się szare
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Warehouse.WarehouseTest.verifyThatTransportWindowIsGrey(WarehouseTest.java:118)
	at ✽.Verify that transport window is grey(file:Features/Atom/Transport/Archive.feature:13)
And Verify that transport is in archive 000ms
Then Restore transport from archive 000ms
And Verify that transport has been successfully restored 000ms
After Hooks.deleteTransportAfterTest() 897ms
After Hooks.rollbackSettings() 140ms
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 325ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 055ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 129ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 033ms
When Go to "TRANSPORT_TABLE" 378ms
And Click button advice in transport table "OWN_COLLECTION" 1s 492ms
And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 45s 947ms
And Go to "TRANSPORT_TABLE" 438ms
And Find transport in table with status "planned-magazyn-tychy" 3s 690ms
And Confirm statuses until reach "process-ended" 13s 582ms
And Wait "12" seconds 12s
Then Go to "ARCHIVE_TAB" 527ms
And Show "OWN_COLLECTION" 171ms
And Verify that created transport is "true" in transport table 1m 32s 344ms
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() 849ms
After Hooks.rollbackSettings() 127ms