Cucumber-JVM Reports - Feature: Filters

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.158	15 wrz 2021, 06:58

	Steps	Scenarios	Features
Filters	175	0	0	0	0	175	24	0	24	12m 32s 090ms	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 808ms

When Go to "TRANSPORT_TABLE" 401ms

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

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

When Go to "TRANSPORT_TABLE" 420ms

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

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

When Go to "TRANSPORT_TABLE" 446ms

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

Scenario Outline Transport types filter

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

When Go to "TRANSPORT_TABLE" 367ms

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

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

When Go to "TRANSPORT_TABLE" 388ms

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

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

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

And Delete created transport by API 557ms

When Go to "ARCHIVE_TAB" 538ms

And Show all transport "true" 153ms

Then Check specific column "CONTRACTOR" 1s 182ms

Hooks

After Hooks.deleteTransportsAfterTest() 499ms

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

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

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

And Go to "TRANSPORT_TABLE" 461ms

And Show all transport "false" 000ms

And Select transportType "DELIVERY" 1s 247ms

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

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

And Select transportType "DELIVERY" 1s 251ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 047ms

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

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

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

And Go to "TRANSPORT_TABLE" 375ms

And Show all transport "true" 146ms

And Select transportType "DELIVERY" 1s 301ms

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

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

And Select transportType "DELIVERY" 1s 218ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 356ms

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

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

And Go to "TRANSPORT_TABLE" 490ms

And Show all transport "false" 000ms

And Select transportType "DELIVERY" 1s 257ms

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

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

And Select transportType "DELIVERY" 1s 261ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 956ms

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

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

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

And Go to "TRANSPORT_TABLE" 354ms

And Show all transport "true" 143ms

And Select transportType "DELIVERY" 1s 270ms

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

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

And Select transportType "DELIVERY" 1s 237ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 440ms

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

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

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

When Go to "TRANSPORT_TABLE" 451ms

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

And Show all transport types 1s 183ms

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

Hooks

After Hooks.deleteTransportAfterTest() 621ms

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

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

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

When Go to "TRANSPORT_TABLE" 357ms

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

And Show all transport types 1s 181ms

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

Hooks

After Hooks.deleteTransportAfterTest() 544ms

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

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

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

When Go to "TRANSPORT_TABLE" 375ms

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

And Show all transport types 1s 145ms

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

Hooks

After Hooks.deleteTransportAfterTest() 577ms

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

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

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

When Go to "TRANSPORT_TABLE" 370ms

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

And Show all transport types 1s 187ms

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

Hooks

After Hooks.deleteTransportAfterTest() 617ms

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

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

And Delete created transport by API 614ms

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

When Go to "ARCHIVE_TAB" 486ms

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

And Show "SMALLS_IMPORT" 178ms

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

Hooks

After Hooks.deleteTransportAfterTest() 539ms

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

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

And Delete created transport by API 599ms

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

When Go to "ARCHIVE_TAB" 494ms

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

And Show "SMALLS_IMPORT" 141ms

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

Hooks

After Hooks.deleteTransportAfterTest() 567ms

@deleteTransportAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

And Delete created transport by API 548ms

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

When Go to "ARCHIVE_TAB" 487ms

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

And Show "SMALLS_IMPORT" 183ms

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

Hooks

After Hooks.deleteTransportAfterTest() 548ms

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

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

And Delete created transport by API 665ms

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

When Go to "ARCHIVE_TAB" 494ms

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

And Show "SMALLS_IMPORT" 153ms

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

Hooks

After Hooks.deleteTransportAfterTest() 568ms

@deleteTransportsAfterTest

Scenario Outline Check load and unload place columns

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 381ms

And Show all transport "true" 135ms

And Select transportType "TRANSPORT_ORDER" 1s 293ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 1s 003ms

@deleteTransportsAfterTest

Scenario Outline Check load and unload place columns

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 431ms

And Show all transport "true" 179ms

And Select transportType "INBOUND" 1s 265ms

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

Hooks

After Hooks.deleteTransportsAfterTest() 980ms

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

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

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

And Go to "TRANSPORT_TABLE" 373ms

And Show all transport "true" 150ms

And Select transportType "TRANSPORT_ORDER" 1s 308ms

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

Hooks

After Hooks.deleteTransportAfterTest() 494ms

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

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

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

And Accept transferred transport by Api 472ms

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

And Delete created transport by API 828ms

When Go to "ARCHIVE_TAB" 471ms

And Show "CONTAINER" 196ms

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

Hooks

After Hooks.deleteTransportAfterTest() 683ms

@deleteTransportAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 493ms

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

And Toggle transport table days limit filter 181ms

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

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

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

And Mark custom fields as not obligatory 005ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 492ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 4s 177ms

After Hooks.rollbackAllCustomFieldsSettings() 332ms

After Hooks.rollbackSettings() 103ms

	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 32s 090ms	Passed

Feature Report