Cucumber-JVM Reports - Feature: Filters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.47	20 cze 2021, 05:08

	Steps	Scenarios	Features
Filters	176	2	10	0	0	188	24	2	26	13m 188ms	Failed

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 459ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 553ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 458ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 453ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 399ms

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

@deleteAllTransportsAfterTest

Scenario Outline Check specific archive column filter

Steps

Given Login as "sempertrans-admin" and set token of apiUsername "super-admin-sempertrans" 6s 954ms

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

And Delete created transport by API 728ms

When Go to "ARCHIVE_TAB" 465ms

And Show all transport "false" 166ms

Then Check specific column "CONTRACTOR" 3s 383ms

Hooks

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

@deleteAllTransportsAfterTest

Scenario Outline Check specific archive column filter

Steps

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

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

And Delete created transport by API 595ms

When Go to "ARCHIVE_TAB" 470ms

And Show all transport "true" 311ms

Then Check specific column "CONTRACTOR" 5s 542ms

Hooks

After Hooks.deleteAllTransports() 48s 066ms

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

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

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

And Go to "TRANSPORT_TABLE" 398ms

And Show all transport "false" 160ms

And Select transportType "DELIVERY" 1s 241ms

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

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

And Select transportType "DELIVERY" 1s 221ms

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

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

Hooks

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

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

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

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

And Go to "TRANSPORT_TABLE" 441ms

And Show all transport "true" 344ms

And Select transportType "DELIVERY" 1s 303ms

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

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

And Select transportType "DELIVERY" 1s 243ms

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

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

Hooks

After Hooks.deleteAllTransports() 48s 736ms

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

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

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

And Go to "TRANSPORT_TABLE" 496ms

And Show all transport "false" 171ms

And Select transportType "DELIVERY" 1s 211ms

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

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

And Select transportType "DELIVERY" 1s 253ms

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

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

Hooks

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

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

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

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

And Go to "TRANSPORT_TABLE" 383ms

And Show all transport "true" 310ms

And Select transportType "DELIVERY" 1s 248ms

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

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

And Select transportType "DELIVERY" 1s 213ms

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

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

Hooks

After Hooks.deleteAllTransports() 48s 695ms

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

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

When Go to "TRANSPORT_TABLE" 417ms

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

And Show all transport types 1s 146ms

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

Hooks

After Hooks.deleteTransportAfterTest() 643ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 465ms

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

And Show all transport types 1s 193ms

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

Hooks

After Hooks.deleteTransportAfterTest() 680ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 387ms

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

And Show all transport types 1s 178ms

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

Hooks

After Hooks.deleteTransportAfterTest() 631ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 411ms

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

And Show all transport types 1s 192ms

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

Hooks

After Hooks.deleteTransportAfterTest() 673ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 633ms

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

When Go to "ARCHIVE_TAB" 467ms

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

And Show "SMALLS_IMPORT" 210ms

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

Hooks

After Hooks.deleteTransportAfterTest() 696ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 616ms

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

When Go to "ARCHIVE_TAB" 438ms

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

And Show "SMALLS_IMPORT" 165ms

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

Hooks

After Hooks.deleteTransportAfterTest() 718ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 651ms

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

When Go to "ARCHIVE_TAB" 487ms

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

And Show "SMALLS_IMPORT" 177ms

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

Hooks

After Hooks.deleteTransportAfterTest() 665ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 645ms

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

When Go to "ARCHIVE_TAB" 480ms

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

And Show "SMALLS_IMPORT" 275ms

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

Hooks

After Hooks.deleteTransportAfterTest() 609ms

@deleteAllTransportsAfterTest

Scenario Outline Check load and unload place columns

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 412ms

And Show all transport "true" 339ms

And Select transportType "TRANSPORT_ORDER" 1s 279ms

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

Hooks

After Hooks.deleteAllTransports() 48s 473ms

@deleteAllTransportsAfterTest

Scenario Outline Check load and unload place columns

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 427ms

And Show all transport "true" 341ms

And Select transportType "INBOUND" 1s 254ms

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

Hooks

After Hooks.deleteAllTransports() 48s 405ms

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

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

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

And Go to "TRANSPORT_TABLE" 419ms

And Show all transport "true" 340ms

And Select transportType "TRANSPORT_ORDER" 1s 325ms

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

Hooks

After Hooks.deleteTransportAfterTest() 566ms

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

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

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

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

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

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

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

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

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 083ms

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

And Go to "TRANSPORT_TABLE" 476ms

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

And Toggle transport table days limit filter 172ms

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

Hooks

After Hooks.deleteTransportAfterTest() 935ms

@deleteTransportsAfterTest @rollbackSettings

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

Steps

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 482ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 2s 385ms

After Hooks.rollbackSettings() 126ms

	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	13m 188ms	Failed

Feature Report