Cucumber-JVM Reports - Feature: Filters

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

	Steps	Scenarios	Features
Filters	176	2	10	0	0	188	24	2	26	12m 55s 622ms	Failed

Scenario Outline Transport types filter

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 131ms

When Go to "TRANSPORT_TABLE" 478ms

Then Check transport is loaded "DELIVERY" 1s 335ms

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 454ms

Then Check transport is loaded "DELIVERY" 1s 342ms

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 352ms

Then Check transport is loaded "DELIVERY" 1s 319ms

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 328ms

Then Check transport is loaded "LOAD" 1s 286ms

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 390ms

Then Check transport is loaded "DELIVERY" 1s 402ms

@deleteAllTransportsAfterTest

Scenario Outline Check specific archive column filter

Steps

Given Login as "sempertrans-admin" and set token of apiUsername "super-admin-sempertrans" 7s 197ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" 2s 030ms

And Delete created transport by API 673ms

When Go to "ARCHIVE_TAB" 427ms

And Show all transport "false" 166ms

Then Check specific column "CONTRACTOR" 368ms

Hooks

After Hooks.deleteAllTransports() 1m 16s 915ms

@deleteAllTransportsAfterTest

Scenario Outline Check specific archive column filter

Steps

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 392ms

And Delete created transport by API 623ms

When Go to "ARCHIVE_TAB" 538ms

And Show all transport "true" 343ms

Then Check specific column "CONTRACTOR" 1s 176ms

Hooks

After Hooks.deleteAllTransports() 48s 087ms

@deleteAllTransportsAfterTest

Scenario Outline Check if transports are visible in table when using filter that does\doesn't apply to all created transports

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" 1s 972ms

When Login as "sempertrans-admin" 2s 279ms

And Go to "TRANSPORT_TABLE" 472ms

And Show all transport "false" 164ms

And Select transportType "DELIVERY" 1s 259ms

And Fill text based "CONTRACTOR" filter with "DOST-ST" 281ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" in "2" days 2s 122ms

And Select transportType "DELIVERY" 1s 262ms

And Fill text based "CONTRACTOR" filter with "DOST-ST" 255ms

Then Verify if new transport appear in transport table with polling "true" 5s 132ms

Hooks

After Hooks.deleteAllTransports() 1m 3s 143ms

@deleteAllTransportsAfterTest

Scenario Outline Check if transports are visible in table when using filter that does\doesn't apply to all created transports

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 2s 785ms

When Login as "alrec-admin" 2s 141ms

And Go to "TRANSPORT_TABLE" 358ms

And Show all transport "true" 320ms

And Select transportType "DELIVERY" 1s 255ms

And Fill text based "CONTRACTOR" filter with "DAA1" 195ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" in "2" days 2s 796ms

And Select transportType "DELIVERY" 1s 240ms

And Fill text based "CONTRACTOR" filter with "DAA1" 283ms

Then Verify if new transport appear in transport table with polling "true" 5s 111ms

Hooks

After Hooks.deleteAllTransports() 48s 590ms

@deleteAllTransportsAfterTest

Scenario Outline Check if transports are visible in table when using filter that does\doesn't apply to all created transports

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" 2s 040ms

When Login as "sempertrans-admin" 2s 234ms

And Go to "TRANSPORT_TABLE" 420ms

And Show all transport "false" 162ms

And Select transportType "DELIVERY" 1s 202ms

And Fill text based "CONTRACTOR" filter with "DOST-ST" 237ms

And Create transport "CREATE_DELIVERY_II" by JSON file as "super-admin-sempertrans" in "2" days 1s 950ms

And Select transportType "DELIVERY" 1s 222ms

And Fill text based "CONTRACTOR" filter with "DOST-ST" 287ms

Then Verify if new transport appear in transport table with polling "false" 20s 086ms

Hooks

After Hooks.deleteAllTransports() 1m 3s 204ms

@deleteAllTransportsAfterTest

Scenario Outline Check if transports are visible in table when using filter that does\doesn't apply to all created transports

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 2s 807ms

When Login as "alrec-admin" 2s 301ms

And Go to "TRANSPORT_TABLE" 416ms

And Show all transport "true" 336ms

And Select transportType "DELIVERY" 1s 297ms

And Fill text based "CONTRACTOR" filter with "DAA1" 243ms

And Create transport "CREATE_DELIVERY_II" by JSON file as "super-admin-alrec" in "2" days 2s 742ms

And Select transportType "DELIVERY" 1s 242ms

And Fill text based "CONTRACTOR" filter with "DAA1" 239ms

Then Verify if new transport appear in transport table with polling "false" 20s 090ms

Hooks

After Hooks.deleteAllTransports() 48s 847ms

@deleteTransportAfterTest

Scenario Outline Check if transport is marked based on the creating user

Steps

Given Set token of apiUsername "swisskrono-purchasing-department" 225ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 2s 318ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 9s 671ms

When Go to "TRANSPORT_TABLE" 422ms

And Sort transports by "show-mine" 1s 136ms

And Show all transport types 1s 166ms

Then Verify that created transport is "true" in transport table 1s 234ms

Hooks

After Hooks.deleteTransportAfterTest() 721ms

@deleteTransportAfterTest

Scenario Outline Check if transport is marked based on the creating user

Steps

Given Set token of apiUsername "swisskrono-purchasing-department" 242ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 2s 215ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 2s 855ms

When Go to "TRANSPORT_TABLE" 461ms

And Sort transports by "show-all" 1s 169ms

And Show all transport types 1s 192ms

Then Verify that created transport is "true" in transport table 1s 270ms

Hooks

After Hooks.deleteTransportAfterTest() 630ms

@deleteTransportAfterTest

Scenario Outline Check if transport is marked based on the creating user

Steps

Given Set token of apiUsername "swisskrono-admin" 233ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 2s 250ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 2s 838ms

When Go to "TRANSPORT_TABLE" 390ms

And Sort transports by "show-mine" 1s 150ms

And Show all transport types 1s 168ms

Then Verify that created transport is "false" in transport table 1m 18s 448ms

Hooks

After Hooks.deleteTransportAfterTest() 731ms

@deleteTransportAfterTest

Scenario Outline Check if transport is marked based on the creating user

Steps

Given Set token of apiUsername "swisskrono-admin" 246ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 2s 256ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 2s 870ms

When Go to "TRANSPORT_TABLE" 402ms

And Sort transports by "show-all" 1s 155ms

And Show all transport types 1s 182ms

Then Verify that created transport is "true" in transport table 1s 290ms

Hooks

After Hooks.deleteTransportAfterTest() 688ms

@deleteTransportAfterTest

Scenario Outline Check if transport in archive is marked based on the creating user

Steps

Given Set token of apiUsername "swisskrono-purchasing-department" 226ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 2s 141ms

And Delete created transport by API 709ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 2s 584ms

When Go to "ARCHIVE_TAB" 491ms

And Sort transports by "show-mine" 1s 136ms

And Show "SMALLS_IMPORT" 146ms

Then Verify that created transport is "true" in transport table 15s 136ms

Hooks

After Hooks.deleteTransportAfterTest() 732ms

@deleteTransportAfterTest

Scenario Outline Check if transport in archive is marked based on the creating user

Steps

Given Set token of apiUsername "swisskrono-purchasing-department" 242ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 16s 096ms

And Delete created transport by API 671ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 2s 780ms

When Go to "ARCHIVE_TAB" 482ms

And Sort transports by "show-all" 1s 140ms

And Show "SMALLS_IMPORT" 175ms

Then Verify that created transport is "true" in transport table 15s 141ms

Hooks

After Hooks.deleteTransportAfterTest() 624ms

@deleteTransportAfterTest

Scenario Outline Check if transport in archive is marked based on the creating user

Steps

Given Set token of apiUsername "swisskrono-admin" 232ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 16s 030ms

And Delete created transport by API 674ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 2s 814ms

When Go to "ARCHIVE_TAB" 464ms

And Sort transports by "show-mine" 1s 145ms

And Show "SMALLS_IMPORT" 178ms

Then Verify that created transport is "false" in transport table 1m 32s 396ms

Hooks

After Hooks.deleteTransportAfterTest() 774ms

@deleteTransportAfterTest

Scenario Outline Check if transport in archive is marked based on the creating user

Steps

Given Set token of apiUsername "swisskrono-admin" 278ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 16s 132ms

And Delete created transport by API 708ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 3s 013ms

When Go to "ARCHIVE_TAB" 477ms

And Sort transports by "show-all" 1s 150ms

And Show "SMALLS_IMPORT" 176ms

Then Verify that created transport is "true" in transport table 15s 132ms

Hooks

After Hooks.deleteTransportAfterTest() 706ms

@deleteAllTransportsAfterTest

Scenario Outline Check load and unload place columns

Steps

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

And Create transport "CREATE_TRANSPORT_FIRST_SUPPLIER" by JSON file as "super-admin-alrec" 16s 115ms

And Create transport "CREATE_TRANSPORT_SECOND_SUPPLIER" by JSON file as "super-admin-alrec" 16s 149ms

When Login as "alrec-admin" 2s 162ms

And Go to "TRANSPORT_TABLE" 356ms

And Show all transport "true" 299ms

And Select transportType "TRANSPORT_ORDER" 1s 260ms

Then Check if load and unload place filters work properly "UNLOAD_PLACE" 26s 255ms

Hooks

After Hooks.deleteAllTransports() 48s 365ms

@deleteAllTransportsAfterTest

Scenario Outline Check load and unload place columns

Steps

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

And Create transport "CREATE_INBOUND_FIRST_SUPPLIER" by JSON file as "super-admin-alrec" 2s 230ms

And Create transport "CREATE_INBOUND_SECOND_SUPPLIER" by JSON file as "super-admin-alrec" 2s 276ms

When Login as "alrec-admin" 2s 264ms

And Go to "TRANSPORT_TABLE" 421ms

And Show all transport "true" 347ms

And Select transportType "INBOUND" 1s 252ms

Then Check if load and unload place filters work properly "LOAD_PLACE" 26s 381ms

Hooks

After Hooks.deleteAllTransports() 48s 397ms

@deleteTransportAfterTest

Scenario Outline Check if order is visible after filter load or unload time column in specific time range

Steps

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

And Create transport "CREATE_TRANSPORT_FIRST_SUPPLIER" by JSON file as "super-admin-alrec" 2s 264ms

When Login as "alrec-admin" 2s 251ms

And Go to "TRANSPORT_TABLE" 403ms

And Show all transport "true" 310ms

And Select transportType "TRANSPORT_ORDER" 1s 282ms

Then Check if load and unload time filters work properly "LOAD_TIME_WINDOW" 37s 307ms

Hooks

After Hooks.deleteTransportAfterTest() 592ms

@deleteTransportAfterTest

Scenario Outline Check if it is possible to choose what the search in the archive applies to

Steps

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 186ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 796ms

And Accept transferred transport by Api 012ms

Error message

java.lang.AssertionError: Nie znaleziono szukanego zasobu w Apollo!
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.getBigIntegerResult(ApolloSelectDbService.java:123)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.getLongResult(ApolloSelectDbService.java:113)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.findIdBy(ApolloSelectDbService.java:19)
	at CucumberTests.Transport.CarrierTransportAction.acceptTransferredTransportByApi(CarrierTransportAction.java:77)
	at ✽.Accept transferred transport by Api(file:Features/Atom/Filters/Filter.feature:135)

And Create advice "ADVICE_SMALLS" "SMALLS_IMPORT" "super-admin-skz" 000ms

And Delete created transport by API 000ms

When Go to "ARCHIVE_TAB" 000ms

And Show "SMALLS_IMPORT" 000ms

Then Check if it is possible to search with different date property selects 000ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 006ms

@deleteTransportAfterTest

Scenario Outline Check if it is possible to choose what the search in the archive applies to

Steps

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

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 173ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 669ms

And Accept transferred transport by Api 013ms

Error message

java.lang.AssertionError: Nie znaleziono szukanego zasobu w Apollo!
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.getBigIntegerResult(ApolloSelectDbService.java:123)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.getLongResult(ApolloSelectDbService.java:113)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.findIdBy(ApolloSelectDbService.java:19)
	at CucumberTests.Transport.CarrierTransportAction.acceptTransferredTransportByApi(CarrierTransportAction.java:77)
	at ✽.Accept transferred transport by Api(file:Features/Atom/Filters/Filter.feature:135)

And Create advice "ADVICE_SMALLS" "SMALLS_EXPORT" "super-admin-skz" 000ms

And Delete created transport by API 000ms

When Go to "ARCHIVE_TAB" 000ms

And Show "SMALLS_EXPORT" 000ms

Then Check if it is possible to search with different date property selects 000ms

Hooks

After Hooks.deleteTransportAfterTest() 910ms

@deleteTransportAfterTest

Scenario Outline Check if transport table days limit filter displays correct transport

Steps

Given Set token of apiUsername "super-admin-neuca" 259ms

And Prepare setting: "TRANSPORT_TABLE_DAYS_LIMIT" with value: "7d" with "super-admin-neuca" 026ms

When Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "8" days 3s 162ms

And Login as "neuca-admin" 2s 064ms

And Go to "TRANSPORT_TABLE" 461ms

Then Verify that created transport is "false" in transport table 1m 32s 398ms

And Toggle transport table days limit filter 183ms

And Verify that created transport is "true" in transport table 15s 101ms

Hooks

After Hooks.deleteTransportAfterTest() 902ms

@deleteTransportsAfterTest @rollbackSettings

Scenario Outline Check if sorting by "Finished" status is working correctly [A-7517]

Steps

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

Hooks

After Hooks.deleteTransportsAfterTest() 2s 370ms

After Hooks.rollbackSettings() 170ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Filters	176	2	10	0	0	188	24	2	26	12m 55s 622ms	Failed

Feature Report