Cucumber-JVM Reports - Feature: Filters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.54	25 cze 2021, 06:22

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

Scenario Outline Transport types filter

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 931ms

When Go to "TRANSPORT_TABLE" 380ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 372ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 390ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 394ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 398ms

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

@deleteAllTransportsAfterTest

Scenario Outline Check specific archive column filter

Steps

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

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

And Delete created transport by API 811ms

When Go to "ARCHIVE_TAB" 465ms

And Show all transport "false" 165ms

Then Check specific column "CONTRACTOR" 464ms

Hooks

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

@deleteAllTransportsAfterTest

Scenario Outline Check specific archive column filter

Steps

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

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

And Delete created transport by API 660ms

When Go to "ARCHIVE_TAB" 505ms

And Show all transport "true" 304ms

Then Check specific column "CONTRACTOR" 1s 259ms

Hooks

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

@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" 1s 986ms

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

And Go to "TRANSPORT_TABLE" 491ms

And Show all transport "false" 163ms

And Select transportType "DELIVERY" 1s 268ms

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

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

And Select transportType "DELIVERY" 1s 248ms

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

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

Hooks

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

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

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

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

And Go to "TRANSPORT_TABLE" 431ms

And Show all transport "true" 344ms

And Select transportType "DELIVERY" 1s 291ms

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

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

And Select transportType "DELIVERY" 1s 242ms

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

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

Hooks

After Hooks.deleteAllTransports() 49s 047ms

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

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

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

And Go to "TRANSPORT_TABLE" 483ms

And Show all transport "false" 163ms

And Select transportType "DELIVERY" 1s 251ms

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

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

And Select transportType "DELIVERY" 1s 275ms

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

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

Hooks

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

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

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

And Go to "TRANSPORT_TABLE" 426ms

And Show all transport "true" 348ms

And Select transportType "DELIVERY" 1s 299ms

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

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

And Select transportType "DELIVERY" 1s 253ms

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

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

Hooks

After Hooks.deleteAllTransports() 48s 876ms

@deleteTransportAfterTest

Scenario Outline Check if transport 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 271ms

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

When Go to "TRANSPORT_TABLE" 460ms

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

And Show all transport types 1s 177ms

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

Hooks

After Hooks.deleteTransportAfterTest() 769ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 445ms

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

And Show all transport types 1s 180ms

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

Hooks

After Hooks.deleteTransportAfterTest() 675ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 391ms

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

And Show all transport types 1s 172ms

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

Hooks

After Hooks.deleteTransportAfterTest() 708ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 466ms

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

And Show all transport types 1s 191ms

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

Hooks

After Hooks.deleteTransportAfterTest() 748ms

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

And Delete created transport by API 714ms

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

When Go to "ARCHIVE_TAB" 470ms

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

And Show "SMALLS_IMPORT" 147ms

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

Hooks

After Hooks.deleteTransportAfterTest() 842ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 685ms

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

When Go to "ARCHIVE_TAB" 496ms

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

And Show "SMALLS_IMPORT" 185ms

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

Hooks

After Hooks.deleteTransportAfterTest() 844ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 763ms

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

When Go to "ARCHIVE_TAB" 461ms

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

And Show "SMALLS_IMPORT" 175ms

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 061ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 761ms

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

When Go to "ARCHIVE_TAB" 457ms

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

And Show "SMALLS_IMPORT" 160ms

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

Hooks

After Hooks.deleteTransportAfterTest() 820ms

@deleteAllTransportsAfterTest

Scenario Outline Check load and unload place columns

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 428ms

And Show all transport "true" 362ms

And Select transportType "TRANSPORT_ORDER" 1s 313ms

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

Hooks

After Hooks.deleteAllTransports() 48s 570ms

@deleteAllTransportsAfterTest

Scenario Outline Check load and unload place columns

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 424ms

And Show all transport "true" 349ms

And Select transportType "INBOUND" 1s 274ms

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

Hooks

After Hooks.deleteAllTransports() 48s 534ms

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

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

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

And Go to "TRANSPORT_TABLE" 428ms

And Show all transport "true" 325ms

And Select transportType "TRANSPORT_ORDER" 1s 288ms

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

Hooks

After Hooks.deleteTransportAfterTest() 782ms

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

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

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

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

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

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

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

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

@deleteTransportAfterTest

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

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 471ms

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

And Toggle transport table days limit filter 188ms

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

Hooks

After Hooks.deleteTransportAfterTest() 946ms

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

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

And Mark custom fields as not obligatory 006ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 481ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 2s 699ms

After Hooks.rollbackAllCustomFieldsSettings() 363ms

After Hooks.rollbackSettings() 133ms

	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 55s 237ms	Failed

Feature Report