Cucumber-JVM Reports - Feature: Filters

Project	Number	Date
ApolloFullRunnerReport	develop.411	06 maj 2021, 18:40

	Steps	Scenarios	Features
Filters	194	0	0	0	0	194	26	0	26	17m 2s 448ms	Passed

Scenario Outline Transport types filter

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 552ms

When Go to "TRANSPORT_TABLE" 121ms

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

Scenario Outline Transport types filter

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 097ms

When Go to "TRANSPORT_TABLE" 111ms

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

Scenario Outline Transport types filter

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-piast" 964ms

When Go to "TRANSPORT_TABLE" 107ms

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

Scenario Outline Transport types filter

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 048ms

When Go to "TRANSPORT_TABLE" 109ms

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

Scenario Outline Transport types filter

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 012ms

When Go to "TRANSPORT_TABLE" 108ms

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

Scenario Outline Check specific archive column filter

Steps

Given Login as "sempertrans-admin" and set token of apiUsername "super-admin-sempertrans" 1s 547ms

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

And Delete created transport by API 087ms

When Go to "ARCHIVE_TAB" 227ms

And Show all transport "false" 013ms

Then Check specific column "CONTRACTOR" 125ms

Scenario Outline Check specific archive column filter

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 007ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 270ms

And Delete created transport by API 084ms

When Go to "ARCHIVE_TAB" 195ms

And Show all transport "true" 077ms

Then Check specific column "CONTRACTOR" 693ms

@deleteAllTransportsAfterTest

Scenario Outline Check every filter in table

Steps

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

And Create transport "CREATE_DELIVERY_II" by JSON file as "super-admin-sempertrans" 15s 177ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" in "0" days 15s 197ms

And Get inputs from database "ADVICE_UNLOAD" "super-admin-sempertrans" 003ms

When Login as "sempertrans-admin" 1s 030ms

And Go to "TRANSPORT_TABLE" 206ms

And Select transportType "DELIVERY" 1s 082ms

And Click button advice in transport table "DELIVERY" 119ms

And Set advice window in schedule in the past 2s 439ms

And Fill advice form 9s 469ms

And Click advice save button and wait for advice form to disappear 30s 662ms

And Go to "TRANSPORT_TABLE" 282ms

And Select transportType "DELIVERY" 1s 064ms

Then Check if filters work properly 40s 065ms

Hooks

After Hooks.deleteAllTransports() 1m 1s 556ms

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

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

When Login as "sempertrans-admin" 963ms

And Go to "TRANSPORT_TABLE" 196ms

And Show all transport "false" 009ms

And Select transportType "DELIVERY" 1s 065ms

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

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

And Select transportType "DELIVERY" 1s 082ms

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

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

Hooks

After Hooks.deleteAllTransports() 1m 1s 590ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 311ms

When Login as "alrec-admin" 1s 053ms

And Go to "TRANSPORT_TABLE" 121ms

And Show all transport "true" 079ms

And Select transportType "DELIVERY" 1s 147ms

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

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

And Select transportType "DELIVERY" 1s 090ms

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

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

Hooks

After Hooks.deleteAllTransports() 46s 691ms

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

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

When Login as "sempertrans-admin" 994ms

And Go to "TRANSPORT_TABLE" 183ms

And Show all transport "false" 010ms

And Select transportType "DELIVERY" 1s 094ms

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

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

And Select transportType "DELIVERY" 1s 112ms

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

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

Hooks

After Hooks.deleteAllTransports() 1m 1s 557ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 308ms

When Login as "alrec-admin" 1s 055ms

And Go to "TRANSPORT_TABLE" 116ms

And Show all transport "true" 080ms

And Select transportType "DELIVERY" 1s 112ms

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

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

And Select transportType "DELIVERY" 1s 097ms

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

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

Hooks

After Hooks.deleteAllTransports() 46s 706ms

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 1s 235ms

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

When Go to "TRANSPORT_TABLE" 193ms

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

And Show all transport types 1s 067ms

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

Hooks

After Hooks.deleteTransportAfterTest() 095ms

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 1s 248ms

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

When Go to "TRANSPORT_TABLE" 168ms

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

And Show all transport types 1s 075ms

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

Hooks

After Hooks.deleteTransportAfterTest() 088ms

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 1s 249ms

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

When Go to "TRANSPORT_TABLE" 101ms

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

And Show all transport types 1s 085ms

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

Hooks

After Hooks.deleteTransportAfterTest() 085ms

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 1s 225ms

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

When Go to "TRANSPORT_TABLE" 112ms

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

And Show all transport types 1s 068ms

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

Hooks

After Hooks.deleteTransportAfterTest() 076ms

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 1s 232ms

And Delete created transport by API 070ms

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

When Go to "ARCHIVE_TAB" 225ms

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

And Show "SMALLS_IMPORT" 072ms

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

Hooks

After Hooks.deleteTransportAfterTest() 099ms

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 15s 235ms

And Delete created transport by API 084ms

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

When Go to "ARCHIVE_TAB" 199ms

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

And Show "SMALLS_IMPORT" 077ms

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

Hooks

After Hooks.deleteTransportAfterTest() 067ms

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 086ms

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

When Go to "ARCHIVE_TAB" 215ms

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

And Show "SMALLS_IMPORT" 065ms

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

Hooks

After Hooks.deleteTransportAfterTest() 090ms

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 15s 208ms

And Delete created transport by API 088ms

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

When Go to "ARCHIVE_TAB" 205ms

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

And Show "SMALLS_IMPORT" 070ms

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

Hooks

After Hooks.deleteTransportAfterTest() 090ms

@deleteAllTransportsAfterTest

Scenario Outline Check load and unload place columns

Steps

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

And Create transport "CREATE_TRANSPORT_FIRST_SUPPLIER" by JSON file as "super-admin-alrec" 15s 274ms

And Create transport "CREATE_TRANSPORT_SECOND_SUPPLIER" by JSON file as "super-admin-alrec" 15s 228ms

When Login as "alrec-admin" 1s 388ms

And Go to "TRANSPORT_TABLE" 116ms

And Show all transport "true" 062ms

And Select transportType "TRANSPORT_ORDER" 1s 151ms

Then Check if load and unload place filters work properly "UNLOAD_PLACE" 24s 729ms

Hooks

After Hooks.deleteAllTransports() 46s 650ms

@deleteAllTransportsAfterTest

Scenario Outline Check load and unload place columns

Steps

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

And Create transport "CREATE_INBOUND_FIRST_SUPPLIER" by JSON file as "super-admin-alrec" 1s 265ms

And Create transport "CREATE_INBOUND_SECOND_SUPPLIER" by JSON file as "super-admin-alrec" 1s 256ms

When Login as "alrec-admin" 948ms

And Go to "TRANSPORT_TABLE" 118ms

And Show all transport "true" 063ms

And Select transportType "INBOUND" 1s 077ms

Then Check if load and unload place filters work properly "LOAD_PLACE" 24s 748ms

Hooks

After Hooks.deleteAllTransports() 46s 663ms

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

And Create transport "CREATE_TRANSPORT_FIRST_SUPPLIER" by JSON file as "super-admin-alrec" 1s 222ms

When Login as "alrec-admin" 1s 010ms

And Go to "TRANSPORT_TABLE" 111ms

And Show all transport "true" 082ms

And Select transportType "TRANSPORT_ORDER" 1s 112ms

Then Check if load and unload time filters work properly "LOAD_TIME_WINDOW" 36s 533ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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" 1s 318ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 259ms

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

And Accept transferred transport by Api 102ms

And Create advice "ADVICE_SMALLS" "SMALLS_IMPORT" "super-admin-skz" 50s 042ms

And Delete created transport by API 137ms

When Go to "ARCHIVE_TAB" 225ms

And Show "SMALLS_IMPORT" 106ms

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

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" 1s 267ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 279ms

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

And Accept transferred transport by Api 093ms

And Create advice "ADVICE_SMALLS" "SMALLS_EXPORT" "super-admin-skz" 50s 043ms

And Delete created transport by API 135ms

When Go to "ARCHIVE_TAB" 270ms

And Show "SMALLS_EXPORT" 096ms

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

@deleteTransportAfterTest

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

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 238ms

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

And Toggle transport table days limit filter 066ms

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

Hooks

After Hooks.deleteTransportAfterTest() 126ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Filters	194	0	0	0	0	194	26	0	26	17m 2s 448ms	Passed

Feature Report