Cucumber-JVM Reports - Feature: Filters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.57	27 cze 2021, 06:33

	Steps	Scenarios	Features
Filters	178	2	10	0	0	190	24	2	26	12m 54s 437ms	Failed

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 398ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 388ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 399ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 408ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 404ms

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

@deleteAllTransportsAfterTest

Scenario Outline Check specific archive column filter

Steps

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

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

And Delete created transport by API 701ms

When Go to "ARCHIVE_TAB" 464ms

And Show all transport "false" 090ms

Then Check specific column "CONTRACTOR" 594ms

Hooks

After Hooks.deleteAllTransports() 1m 17s 077ms

@deleteAllTransportsAfterTest

Scenario Outline Check specific archive column filter

Steps

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

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

And Delete created transport by API 720ms

When Go to "ARCHIVE_TAB" 462ms

And Show all transport "true" 221ms

Then Check specific column "CONTRACTOR" 1s 314ms

Hooks

After Hooks.deleteAllTransports() 1m 2s 215ms

@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" 343ms

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

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

And Go to "TRANSPORT_TABLE" 493ms

And Show all transport "false" 084ms

And Select transportType "DELIVERY" 1s 260ms

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

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

And Select transportType "DELIVERY" 1s 258ms

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

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

Hooks

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

@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" 241ms

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

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

And Go to "TRANSPORT_TABLE" 421ms

And Show all transport "true" 262ms

And Select transportType "DELIVERY" 1s 303ms

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

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

And Select transportType "DELIVERY" 1s 250ms

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

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

Hooks

After Hooks.deleteAllTransports() 49s 027ms

@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" 259ms

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

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

And Go to "TRANSPORT_TABLE" 467ms

And Show all transport "false" 082ms

And Select transportType "DELIVERY" 1s 261ms

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

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

And Select transportType "DELIVERY" 1s 256ms

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

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

Hooks

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

@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" 232ms

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

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

And Go to "TRANSPORT_TABLE" 423ms

And Show all transport "true" 263ms

And Select transportType "DELIVERY" 1s 290ms

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

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

And Select transportType "DELIVERY" 1s 239ms

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

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

Hooks

After Hooks.deleteAllTransports() 48s 911ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 474ms

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

And Show all transport types 1s 179ms

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

Hooks

After Hooks.deleteTransportAfterTest() 755ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 436ms

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

And Show all transport types 1s 186ms

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

Hooks

After Hooks.deleteTransportAfterTest() 761ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 379ms

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

And Show all transport types 1s 173ms

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

Hooks

After Hooks.deleteTransportAfterTest() 776ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 400ms

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

And Show all transport types 1s 192ms

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

Hooks

After Hooks.deleteTransportAfterTest() 775ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 736ms

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

When Go to "ARCHIVE_TAB" 485ms

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

And Show "SMALLS_IMPORT" 167ms

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

Hooks

After Hooks.deleteTransportAfterTest() 829ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 722ms

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

When Go to "ARCHIVE_TAB" 496ms

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

And Show "SMALLS_IMPORT" 170ms

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

Hooks

After Hooks.deleteTransportAfterTest() 910ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 676ms

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

When Go to "ARCHIVE_TAB" 493ms

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

And Show "SMALLS_IMPORT" 171ms

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

Hooks

After Hooks.deleteTransportAfterTest() 908ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 739ms

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

When Go to "ARCHIVE_TAB" 500ms

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

And Show "SMALLS_IMPORT" 179ms

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

Hooks

After Hooks.deleteTransportAfterTest() 912ms

@deleteAllTransportsAfterTest

Scenario Outline Check load and unload place columns

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 433ms

And Show all transport "true" 271ms

And Select transportType "TRANSPORT_ORDER" 1s 323ms

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

Hooks

After Hooks.deleteAllTransports() 48s 658ms

@deleteAllTransportsAfterTest

Scenario Outline Check load and unload place columns

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 339ms

And Show all transport "true" 210ms

And Select transportType "INBOUND" 1s 221ms

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

Hooks

After Hooks.deleteAllTransports() 48s 535ms

@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" 227ms

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

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

And Go to "TRANSPORT_TABLE" 423ms

And Show all transport "true" 267ms

And Select transportType "TRANSPORT_ORDER" 1s 306ms

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

Hooks

After Hooks.deleteTransportAfterTest() 690ms

@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 362ms

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

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

And Accept transferred transport by Api 014ms

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() 962ms

@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 529ms

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

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

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_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() 959ms

@deleteTransportAfterTest

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

Steps

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

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

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

And Login as "neuca-admin" 1s 999ms

And Go to "TRANSPORT_TABLE" 480ms

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

And Toggle transport table days limit filter 183ms

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 041ms

@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings

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

Steps

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

And Get custom field settings for "DELIVERY" transport type and "neuca" company 175ms

And Mark custom fields as not obligatory 006ms

And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 138ms

And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 031ms

When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 21s 152ms

Then Login as "neuca-admin" 2s 230ms

And Go to "TRANSPORT_TABLE" 482ms

And Confirm statuses until reach "process-ended" 17s 171ms

Then Check if sorting by 'Finished' status is working correctly 295ms

Hooks

After Hooks.deleteTransportsAfterTest() 2s 762ms

After Hooks.rollbackAllCustomFieldsSettings() 390ms

After Hooks.rollbackSettings() 122ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Filters	178	2	10	0	0	190	24	2	26	12m 54s 437ms	Failed

Feature Report