Project Number Date
ApolloFullRunnerReport kapibary.45 18 cze 2021, 05:45

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 5s 429ms Failed
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Given Login by Api as "super-admin-piast" and get token and expect status "200" 345ms
And Set token of apiUsername "super-admin-piast" 317ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 265ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" 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 340ms
Then Login as "super-admin-piast" 8s 567ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 418ms
After Hooks.deleteTransportAfterApiTest() 865ms
After Hooks.rollbackSettings() 002ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Given Login by Api as "super-admin-piast" and get token and expect status "200" 262ms
And Set token of apiUsername "super-admin-piast" 258ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 182ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_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 262ms
Then Login as "super-admin-piast" 2s 444ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 355ms
After Hooks.deleteTransportAfterApiTest() 753ms
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" 268ms
And Set token of apiUsername "super-admin-piast" 313ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 167ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_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 292ms
Then Login as "super-admin-piast" 2s 333ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 391ms
After Hooks.deleteTransportAfterApiTest() 659ms
After Hooks.rollbackSettings() 000ms
View Feature Filters
@deleteTransportsAfterTest @rollbackSettings
Given Set token of apiUsername "super-admin-neuca" 250ms
And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 162ms
And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 028ms
When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 21s 096ms
Then Login as "neuca-admin" 2s 021ms
And Go to "TRANSPORT_TABLE" 474ms
And Confirm statuses until reach "process-ended" 18s 010ms
Then Check if sorting by 'Finished' status is working correctly 255ms
After Hooks.deleteTransportsAfterTest() 2s 370ms
After Hooks.rollbackSettings() 170ms
View Feature Invitation
@rollbackSettings @deleteInvitationAfterTest
Given Set token of apiUsername "super-admin-piast" 247ms
And Delete invitations with email "automaty31415@test.pl" 017ms
And If user is login then logout 15s 055ms
Given Set token of apiUsername "super-admin-piast" 273ms
And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 154ms
Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 200ms
And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 363ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 3s 021ms
Then Go to "INVITATIONS_TAB" 669ms
And Go to "EXPIRED_TAB" invitation status tab 276ms
Then Invitation is displayed on list "automaty31415@test.pl" 448ms
After Hooks.deleteInvitationAfterTest() 181ms
After Hooks.rollbackSettings() 148ms
View Feature DedicatedWindow
@rollbackSettings
Given Set token of apiUsername "super-admin-skz" 261ms
And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 236ms
And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 308ms
And Prepare setting for automatic time window delete with "super-admin-skz" 209ms
When Login as "swisskrono-admin" 2s 643ms
And Go to "WAREHOUSE_TAB" 861ms
Then Check if dedicated window is deleted from schedule 1m 316ms
After Hooks.rollbackSettings() 200ms
View Feature Move transport to archive
@rollbackSettings @deleteTransportAfterTest
Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 8s 578ms
And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 018ms
And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 143ms
And Set proper delay time to move order to archive after task timeout 130ms
When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 926ms
And Go to "WAREHOUSE_TAB" 1s 021ms
And Change warehouse in schedule to: "Katowice" 1s 496ms
And Wait "60" seconds 1m
And Verify that transport window is grey 084ms
And Verify that transport is in archive 6s 129ms
Then Restore transport from archive 2s 530ms
And Verify that transport has been successfully restored 15s 615ms
After Hooks.deleteTransportAfterTest() 825ms
After Hooks.rollbackSettings() 122ms
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 441ms
And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 049ms
And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 129ms
And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 026ms
When Go to "TRANSPORT_TABLE" 393ms
And Click button advice in transport table "OWN_COLLECTION" 1s 462ms
And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 45s 834ms
And Go to "TRANSPORT_TABLE" 435ms
And Find transport in table with status "planned-magazyn-tychy" 3s 689ms
And Confirm statuses until reach "process-ended" 13s 673ms
And Wait "12" seconds 12s
Then Go to "ARCHIVE_TAB" 500ms
And Show "OWN_COLLECTION" 165ms
And Verify that created transport is "true" in transport table 1m 32s 216ms
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() 760ms
After Hooks.rollbackSettings() 144ms