Cucumber-JVM Reports - Feature: Filters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.157	14 wrz 2021, 06:50

	Steps	Scenarios	Features
Filters	175	0	0	0	0	175	24	0	24	12m 31s 804ms	Passed

Scenario Outline Transport types filter

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 691ms

When Go to "TRANSPORT_TABLE" 402ms

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

Scenario Outline Transport types filter

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 5s 686ms

When Go to "TRANSPORT_TABLE" 405ms

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

Scenario Outline Transport types filter

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to "TRANSPORT_TABLE" 448ms

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

Scenario Outline Transport types filter

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 7s 448ms

When Go to "TRANSPORT_TABLE" 403ms

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

Scenario Outline Transport types filter

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 4s 190ms

When Go to "TRANSPORT_TABLE" 420ms

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

@deleteTransportsAfterTest

Scenario Outline Check specific archive column filter

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Delete created transport by API 563ms

When Go to "ARCHIVE_TAB" 539ms

And Show all transport "true" 150ms

Then Check specific column "CONTRACTOR" 1s 183ms

Hooks

After Hooks.deleteTransportsAfterTest() 498ms

@deleteTransportsAfterTest

Scenario Outline Check if transports are visible in table when using filter that does\doesn't apply to all created transports

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-sempertrans" 260ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" 15s 755ms

When Login as "sempertrans-admin" 6s 486ms

And Go to "TRANSPORT_TABLE" 471ms

And Show all transport "false" 000ms

And Select transportType "DELIVERY" 1s 242ms

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

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

And Select transportType "DELIVERY" 1s 225ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 020ms

@deleteTransportsAfterTest

Scenario Outline Check if transports are visible in table when using filter that does\doesn't apply to all created transports

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Go to "TRANSPORT_TABLE" 428ms

And Show all transport "true" 173ms

And Select transportType "DELIVERY" 1s 303ms

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

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

And Select transportType "DELIVERY" 1s 251ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 346ms

@deleteTransportsAfterTest

Scenario Outline Check if transports are visible in table when using filter that does\doesn't apply to all created transports

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Go to "TRANSPORT_TABLE" 449ms

And Show all transport "false" 000ms

And Select transportType "DELIVERY" 1s 206ms

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

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

And Select transportType "DELIVERY" 1s 251ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 946ms

@deleteTransportsAfterTest

Scenario Outline Check if transports are visible in table when using filter that does\doesn't apply to all created transports

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Go to "TRANSPORT_TABLE" 438ms

And Show all transport "true" 165ms

And Select transportType "DELIVERY" 1s 275ms

And Fill text based "CONTRACTOR" filter with "DAAA1" 263ms

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

And Select transportType "DELIVERY" 1s 243ms

And Fill text based "CONTRACTOR" filter with "DAAA1" 240ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 367ms

@deleteTransportAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 480ms

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

And Show all transport types 1s 187ms

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

Hooks

After Hooks.deleteTransportAfterTest() 635ms

@deleteTransportAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 433ms

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

And Show all transport types 1s 180ms

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

Hooks

After Hooks.deleteTransportAfterTest() 590ms

@deleteTransportAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 443ms

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

And Show all transport types 1s 192ms

Then Verify that created transport is "false" in transport table 31s 774ms

Hooks

After Hooks.deleteTransportAfterTest() 588ms

@deleteTransportAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 402ms

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

And Show all transport types 1s 186ms

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

Hooks

After Hooks.deleteTransportAfterTest() 664ms

@deleteTransportAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Delete created transport by API 627ms

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

When Go to "ARCHIVE_TAB" 491ms

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

And Show "SMALLS_IMPORT" 187ms

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

Hooks

After Hooks.deleteTransportAfterTest() 575ms

@deleteTransportAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Delete created transport by API 614ms

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

When Go to "ARCHIVE_TAB" 477ms

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

And Show "SMALLS_IMPORT" 194ms

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

Hooks

After Hooks.deleteTransportAfterTest() 565ms

@deleteTransportAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Delete created transport by API 560ms

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

When Go to "ARCHIVE_TAB" 497ms

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

And Show "SMALLS_IMPORT" 182ms

Then Verify that created transport is "false" in transport table 45s 643ms

Hooks

After Hooks.deleteTransportAfterTest() 551ms

@deleteTransportAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Delete created transport by API 558ms

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

When Go to "ARCHIVE_TAB" 483ms

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

And Show "SMALLS_IMPORT" 190ms

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

Hooks

After Hooks.deleteTransportAfterTest() 560ms

@deleteTransportsAfterTest

Scenario Outline Check load and unload place columns

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 414ms

And Show all transport "true" 171ms

And Select transportType "TRANSPORT_ORDER" 1s 307ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 986ms

@deleteTransportsAfterTest

Scenario Outline Check load and unload place columns

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 410ms

And Show all transport "true" 165ms

And Select transportType "INBOUND" 1s 231ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 025ms

@deleteTransportAfterTest @FLAKY-A-8288

Scenario Outline Check if order is visible after filter load or unload time column in specific time range

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Go to "TRANSPORT_TABLE" 418ms

And Show all transport "true" 162ms

And Select transportType "TRANSPORT_ORDER" 1s 311ms

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

Hooks

After Hooks.deleteTransportAfterTest() 504ms

@deleteTransportAfterTest @FLAKY-A-8288

Scenario Outline Check if it is possible to choose what the search in the archive applies to

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 102ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 913ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 487ms

And Accept transferred transport by Api 409ms

And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-adama" 3s 332ms

And Delete created transport by API 847ms

When Go to "ARCHIVE_TAB" 465ms

And Show "CONTAINER" 178ms

Then Check if it is possible to search with different date property selects 1m 47s 221ms

Hooks

After Hooks.deleteTransportAfterTest() 629ms

@deleteTransportAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

And Login as "neuca-admin" 7s 237ms

And Go to "TRANSPORT_TABLE" 490ms

Then Verify that created transport is "false" in transport table 31s 814ms

And Toggle transport table days limit filter 163ms

And Verify that created transport is "true" in transport table 1s 226ms

Hooks

After Hooks.deleteTransportAfterTest() 746ms

@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Mark custom fields as not obligatory 006ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 489ms

And Confirm statuses until reach "process-ended" 21s 557ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 4s 220ms

After Hooks.rollbackAllCustomFieldsSettings() 334ms

After Hooks.rollbackSettings() 102ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Filters	175	0	0	0	0	175	24	0	24	12m 31s 804ms	Passed

Feature Report