Cucumber-JVM Reports - Feature: Filters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.46	19 cze 2021, 05:43

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 460ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 476ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 401ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 394ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 409ms

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

@deleteAllTransportsAfterTest

Scenario Outline Check specific archive column filter

Steps

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

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

And Delete created transport by API 730ms

When Go to "ARCHIVE_TAB" 472ms

And Show all transport "false" 167ms

Then Check specific column "CONTRACTOR" 360ms

Hooks

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

@deleteAllTransportsAfterTest

Scenario Outline Check specific archive column filter

Steps

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

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

And Delete created transport by API 579ms

When Go to "ARCHIVE_TAB" 528ms

And Show all transport "true" 338ms

Then Check specific column "CONTRACTOR" 1s 185ms

Hooks

After Hooks.deleteAllTransports() 48s 035ms

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

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

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

And Go to "TRANSPORT_TABLE" 485ms

And Show all transport "false" 164ms

And Select transportType "DELIVERY" 1s 262ms

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

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

And Select transportType "DELIVERY" 1s 263ms

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

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

Hooks

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

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

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

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

And Go to "TRANSPORT_TABLE" 354ms

And Show all transport "true" 299ms

And Select transportType "DELIVERY" 1s 240ms

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

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

And Select transportType "DELIVERY" 1s 243ms

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

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

Hooks

After Hooks.deleteAllTransports() 48s 543ms

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

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

And Go to "TRANSPORT_TABLE" 485ms

And Show all transport "false" 167ms

And Select transportType "DELIVERY" 1s 254ms

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

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

And Select transportType "DELIVERY" 1s 262ms

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

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

Hooks

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

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

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

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

And Go to "TRANSPORT_TABLE" 401ms

And Show all transport "true" 351ms

And Select transportType "DELIVERY" 1s 298ms

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

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

And Select transportType "DELIVERY" 1s 248ms

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

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

Hooks

After Hooks.deleteAllTransports() 48s 596ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 460ms

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

And Show all transport types 1s 185ms

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

Hooks

After Hooks.deleteTransportAfterTest() 670ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 437ms

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

And Show all transport types 1s 180ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 395ms

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

And Show all transport types 1s 158ms

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

Hooks

After Hooks.deleteTransportAfterTest() 724ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 387ms

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

And Show all transport types 1s 155ms

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

Hooks

After Hooks.deleteTransportAfterTest() 552ms

@deleteTransportAfterTest

Scenario Outline Check if transport in archive 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 152ms

And Delete created transport by API 578ms

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

When Go to "ARCHIVE_TAB" 485ms

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

And Show "SMALLS_IMPORT" 177ms

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

Hooks

After Hooks.deleteTransportAfterTest() 622ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 646ms

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

When Go to "ARCHIVE_TAB" 505ms

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

And Show "SMALLS_IMPORT" 174ms

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

Hooks

After Hooks.deleteTransportAfterTest() 571ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 652ms

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

When Go to "ARCHIVE_TAB" 487ms

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

And Show "SMALLS_IMPORT" 173ms

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

Hooks

After Hooks.deleteTransportAfterTest() 705ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 664ms

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

When Go to "ARCHIVE_TAB" 476ms

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

And Show "SMALLS_IMPORT" 172ms

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

Hooks

After Hooks.deleteTransportAfterTest() 689ms

@deleteAllTransportsAfterTest

Scenario Outline Check load and unload place columns

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 425ms

And Show all transport "true" 331ms

And Select transportType "TRANSPORT_ORDER" 1s 304ms

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

Hooks

After Hooks.deleteAllTransports() 48s 462ms

@deleteAllTransportsAfterTest

Scenario Outline Check load and unload place columns

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 420ms

And Show all transport "true" 337ms

And Select transportType "INBOUND" 1s 256ms

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

Hooks

After Hooks.deleteAllTransports() 48s 424ms

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

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

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

And Go to "TRANSPORT_TABLE" 362ms

And Show all transport "true" 326ms

And Select transportType "TRANSPORT_ORDER" 1s 282ms

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

Hooks

After Hooks.deleteTransportAfterTest() 565ms

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

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

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

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

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

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

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

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

@deleteTransportAfterTest

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

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 492ms

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

And Toggle transport table days limit filter 181ms

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

Hooks

After Hooks.deleteTransportAfterTest() 842ms

@deleteTransportsAfterTest @rollbackSettings

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

Steps

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 472ms

And Confirm statuses until reach "process-ended" 18s 327ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 2s 389ms

After Hooks.rollbackSettings() 119ms

	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 54s 302ms	Failed

Feature Report