Cucumber-JVM Reports - Feature: Filters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.48	21 cze 2021, 05:22

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 499ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 611ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 467ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 485ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 400ms

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

@deleteAllTransportsAfterTest

Scenario Outline Check specific archive column filter

Steps

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

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

And Delete created transport by API 626ms

When Go to "ARCHIVE_TAB" 404ms

And Show all transport "false" 166ms

Then Check specific column "CONTRACTOR" 5s 736ms

Hooks

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

@deleteAllTransportsAfterTest

Scenario Outline Check specific archive column filter

Steps

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

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

And Delete created transport by API 601ms

When Go to "ARCHIVE_TAB" 507ms

And Show all transport "true" 328ms

Then Check specific column "CONTRACTOR" 7s 302ms

Hooks

After Hooks.deleteAllTransports() 47s 915ms

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

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

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

And Go to "TRANSPORT_TABLE" 477ms

And Show all transport "false" 164ms

And Select transportType "DELIVERY" 1s 250ms

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

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

And Select transportType "DELIVERY" 1s 210ms

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

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

Hooks

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

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

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

And Go to "TRANSPORT_TABLE" 419ms

And Show all transport "true" 349ms

And Select transportType "DELIVERY" 1s 307ms

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

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

And Select transportType "DELIVERY" 1s 236ms

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

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

Hooks

After Hooks.deleteAllTransports() 48s 778ms

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

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

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

And Go to "TRANSPORT_TABLE" 488ms

And Show all transport "false" 161ms

And Select transportType "DELIVERY" 1s 260ms

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

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

And Select transportType "DELIVERY" 1s 259ms

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

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

Hooks

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

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

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

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

And Go to "TRANSPORT_TABLE" 412ms

And Show all transport "true" 348ms

And Select transportType "DELIVERY" 1s 293ms

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

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

And Select transportType "DELIVERY" 1s 250ms

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

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

Hooks

After Hooks.deleteAllTransports() 48s 763ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 450ms

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

And Show all transport types 1s 183ms

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

Hooks

After Hooks.deleteTransportAfterTest() 570ms

@deleteTransportAfterTest

Scenario Outline Check if transport 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" 2s 053ms

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

When Go to "TRANSPORT_TABLE" 441ms

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

And Show all transport types 1s 153ms

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

Hooks

After Hooks.deleteTransportAfterTest() 597ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 379ms

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

And Show all transport types 1s 157ms

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

Hooks

After Hooks.deleteTransportAfterTest() 672ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 396ms

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

And Show all transport types 1s 190ms

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

Hooks

After Hooks.deleteTransportAfterTest() 700ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 657ms

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

When Go to "ARCHIVE_TAB" 477ms

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

And Show "SMALLS_IMPORT" 174ms

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

Hooks

After Hooks.deleteTransportAfterTest() 663ms

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

And Delete created transport by API 655ms

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

When Go to "ARCHIVE_TAB" 483ms

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

And Show "SMALLS_IMPORT" 172ms

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

Hooks

After Hooks.deleteTransportAfterTest() 602ms

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

And Delete created transport by API 568ms

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

When Go to "ARCHIVE_TAB" 478ms

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

And Show "SMALLS_IMPORT" 142ms

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

Hooks

After Hooks.deleteTransportAfterTest() 668ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 625ms

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

When Go to "ARCHIVE_TAB" 466ms

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

And Show "SMALLS_IMPORT" 564ms

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

Hooks

After Hooks.deleteTransportAfterTest() 725ms

@deleteAllTransportsAfterTest

Scenario Outline Check load and unload place columns

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 411ms

And Show all transport "true" 346ms

And Select transportType "TRANSPORT_ORDER" 1s 322ms

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

Hooks

After Hooks.deleteAllTransports() 48s 215ms

@deleteAllTransportsAfterTest

Scenario Outline Check load and unload place columns

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 411ms

And Show all transport "true" 349ms

And Select transportType "INBOUND" 1s 248ms

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

Hooks

After Hooks.deleteAllTransports() 48s 366ms

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

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

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

And Go to "TRANSPORT_TABLE" 408ms

And Show all transport "true" 341ms

And Select transportType "TRANSPORT_ORDER" 1s 294ms

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

Hooks

After Hooks.deleteTransportAfterTest() 573ms

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

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

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

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

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

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

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

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

@deleteTransportAfterTest

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

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 455ms

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

And Toggle transport table days limit filter 147ms

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

Hooks

After Hooks.deleteTransportAfterTest() 944ms

@deleteTransportsAfterTest @rollbackSettings

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

Steps

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 481ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 2s 116ms

After Hooks.rollbackSettings() 128ms

	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 5s 158ms	Failed

Feature Report