Cucumber-JVM Reports - Feature: Filters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.53	24 cze 2021, 06:22

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 359ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 358ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 401ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 374ms

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

Scenario Outline Transport types filter

Steps

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

When Go to "TRANSPORT_TABLE" 396ms

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

@deleteAllTransportsAfterTest

Scenario Outline Check specific archive column filter

Steps

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

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

And Delete created transport by API 660ms

When Go to "ARCHIVE_TAB" 445ms

And Show all transport "false" 167ms

Then Check specific column "CONTRACTOR" 451ms

Hooks

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

@deleteAllTransportsAfterTest

Scenario Outline Check specific archive column filter

Steps

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

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

And Delete created transport by API 617ms

When Go to "ARCHIVE_TAB" 538ms

And Show all transport "true" 330ms

Then Check specific column "CONTRACTOR" 1s 173ms

Hooks

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

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

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

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

And Go to "TRANSPORT_TABLE" 435ms

And Show all transport "false" 163ms

And Select transportType "DELIVERY" 1s 210ms

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

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

And Select transportType "DELIVERY" 1s 210ms

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

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

Hooks

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

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

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

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

And Go to "TRANSPORT_TABLE" 414ms

And Show all transport "true" 337ms

And Select transportType "DELIVERY" 1s 286ms

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

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

And Select transportType "DELIVERY" 1s 227ms

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

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

Hooks

After Hooks.deleteAllTransports() 48s 745ms

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

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

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

And Go to "TRANSPORT_TABLE" 470ms

And Show all transport "false" 163ms

And Select transportType "DELIVERY" 1s 267ms

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

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

And Select transportType "DELIVERY" 1s 259ms

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

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

Hooks

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

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

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

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

And Go to "TRANSPORT_TABLE" 359ms

And Show all transport "true" 290ms

And Select transportType "DELIVERY" 1s 235ms

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

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

And Select transportType "DELIVERY" 1s 210ms

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

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

Hooks

After Hooks.deleteAllTransports() 48s 794ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 455ms

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

And Show all transport types 1s 189ms

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

Hooks

After Hooks.deleteTransportAfterTest() 701ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 437ms

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

And Show all transport types 1s 179ms

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

Hooks

After Hooks.deleteTransportAfterTest() 659ms

@deleteTransportAfterTest

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

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

When Go to "TRANSPORT_TABLE" 396ms

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

And Show all transport types 1s 183ms

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

Hooks

After Hooks.deleteTransportAfterTest() 645ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 328ms

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

And Show all transport types 1s 158ms

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

Hooks

After Hooks.deleteTransportAfterTest() 716ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 676ms

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

When Go to "ARCHIVE_TAB" 498ms

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

And Show "SMALLS_IMPORT" 175ms

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

Hooks

After Hooks.deleteTransportAfterTest() 727ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 672ms

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

When Go to "ARCHIVE_TAB" 472ms

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

And Show "SMALLS_IMPORT" 166ms

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

Hooks

After Hooks.deleteTransportAfterTest() 717ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 653ms

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

When Go to "ARCHIVE_TAB" 497ms

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

And Show "SMALLS_IMPORT" 191ms

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

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

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

And Delete created transport by API 674ms

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

When Go to "ARCHIVE_TAB" 460ms

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

And Show "SMALLS_IMPORT" 168ms

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

Hooks

After Hooks.deleteTransportAfterTest() 632ms

@deleteAllTransportsAfterTest

Scenario Outline Check load and unload place columns

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 431ms

And Show all transport "true" 347ms

And Select transportType "TRANSPORT_ORDER" 1s 309ms

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

Hooks

After Hooks.deleteAllTransports() 48s 480ms

@deleteAllTransportsAfterTest

Scenario Outline Check load and unload place columns

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 415ms

And Show all transport "true" 338ms

And Select transportType "INBOUND" 1s 254ms

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

Hooks

After Hooks.deleteAllTransports() 48s 511ms

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

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

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

And Go to "TRANSPORT_TABLE" 342ms

And Show all transport "true" 310ms

And Select transportType "TRANSPORT_ORDER" 1s 276ms

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

Hooks

After Hooks.deleteTransportAfterTest() 576ms

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

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

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

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

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

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

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

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

@deleteTransportAfterTest

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

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 473ms

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

And Toggle transport table days limit filter 193ms

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

Hooks

After Hooks.deleteTransportAfterTest() 774ms

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

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

And Mark custom fields as not obligatory 006ms

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

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

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

And Go to "TRANSPORT_TABLE" 513ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 2s 525ms

After Hooks.rollbackAllCustomFieldsSettings() 470ms

After Hooks.rollbackSettings() 150ms

	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 57s 658ms	Failed

Feature Report