Cucumber-JVM Reports - Tag: @deleteTransportAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.68	05 lip 2021, 06:38

	Steps	Scenarios	Features
@deleteTransportAfterTest	3869	18	16	0	0	3903	386	18	404	6h 39m 12s 077ms	Failed

View Feature Advice transport

Scenario Outline Check if it isn't possible to advice transport in the past when advice is created from transports table.

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 511ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 2s 108ms

And Get inputs from database "CREATE_ADVICE_CONTAINER" "super-admin-adama" 2s 658ms

And Check is transport "CONTAINER" created in transport table and set transport id 1s 368ms

When Click button advice in transport table "CONTAINER" 237ms

And Set advice window in schedule in the past 3s 464ms

And Fill advice form 20s 028ms

And Click advice save button to check error message 197ms

Then Check if possible advice alert is displayed 071ms

Hooks

After Hooks.deleteTransportAfterTest() 685ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to advice transport in the past when advice is created from transports table.

Steps

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 076ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 041ms

And Check is transport "DELIVERY" created in transport table and set transport id 1s 399ms

When Click button advice in transport table "DELIVERY" 257ms

And Set advice window in schedule in the past 3s 459ms

And Fill advice form 10s 491ms

And Click advice save button to check error message 204ms

Then Check if possible advice alert is displayed 073ms

Hooks

After Hooks.deleteTransportAfterTest() 752ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to advice transport in the past when advice is created from transports table.

Steps

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

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 2s 028ms

And Get inputs from database "ADVICE_LOAD" "super-admin-piast" 025ms

And Check is transport "LOAD" created in transport table and set transport id 1s 383ms

When Click button advice in transport table "LOAD" 248ms

And Set advice window in schedule in the past 3s 383ms

And Fill advice form 10s 867ms

And Click advice save button to check error message 215ms

Then Check if possible advice alert is displayed 074ms

Hooks

After Hooks.deleteTransportAfterTest() 800ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to advice transport in the past when advice is created from transports table.

Steps

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 990ms

And Get inputs from database "ADVICE_LOAD" "super-admin-keeeper" 019ms

And Check is transport "LOAD" created in transport table and set transport id 1s 319ms

When Click button advice in transport table "LOAD" 214ms

And Set advice window in schedule in the past 3s 181ms

And Fill advice form 16s 199ms

And Click advice save button to check error message 203ms

Then Check if possible advice alert is displayed 072ms

Hooks

After Hooks.deleteTransportAfterTest() 739ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to advice transport in the past when advice is created from transports table.

Steps

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

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 983ms

And Get inputs from database "ADVICE_CONTAINER" "super-admin-keeeper" 022ms

And Check is transport "CONTAINER" created in transport table and set transport id 1s 347ms

When Click button advice in transport table "CONTAINER" 191ms

And Set advice window in schedule in the past 3s 119ms

And Fill advice form 16s 446ms

And Click advice save button to check error message 187ms

Then Check if possible advice alert is displayed 072ms

Hooks

After Hooks.deleteTransportAfterTest() 730ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to edit advice in transport details.

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 503ms

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

And Show all transport types 1s 171ms

And Create advice "CREATE_ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 57s 273ms

And Go to "TRANSPORT_TABLE" 451ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 025ms

When Go to transport details "CONTAINER" 2s 871ms

And Fill transport form 5s 136ms

And Get inputs from database "EDIT_ADVICE_CONTAINER" "super-admin-adama" 024ms

And Expand advice panel 282ms

And Edit advice in transport details 15s 415ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 524ms

And Go to transport details "CONTAINER" 2s 901ms

And Expand advice panel 252ms

Then Check are advice values equals after edition 698ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 011ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to edit advice in transport details.

Steps

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 043ms

And Show all transport types 1s 135ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 33s

And Go to "TRANSPORT_TABLE" 495ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-piast" 025ms

When Go to transport details "DELIVERY" 2s 879ms

And Fill transport form 1m 8s 531ms

And Get inputs from database "EDIT_ADVICE_DELIVERY" "super-admin-piast" 022ms

And Expand advice panel 233ms

And Edit advice in transport details 8s 210ms

And Click "save-transport-and-close" save button and wait for form to disappear 18s 693ms

And Go to transport details "DELIVERY" 2s 932ms

And Expand advice panel 392ms

Then Check are advice values equals after edition 328ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 201ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to edit advice in transport details.

Steps

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

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 2s 013ms

And Show all transport types 1s 167ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-piast" 47s 692ms

And Go to "TRANSPORT_TABLE" 462ms

And Get inputs from database "EDIT_LOAD" "super-admin-piast" 025ms

When Go to transport details "LOAD" 3s 015ms

And Fill transport form 1m 3s 426ms

And Get inputs from database "EDIT_ADVICE_DELIVERY" "super-admin-piast" 023ms

And Expand advice panel 260ms

And Edit advice in transport details 8s 206ms

And Click "save-transport-and-close" save button and wait for form to disappear 18s 663ms

And Go to transport details "LOAD" 2s 954ms

And Expand advice panel 538ms

Then Check are advice values equals after edition 319ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 269ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to edit advice in transport details.

Steps

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 2s 005ms

And Show all transport types 1s 177ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 53s 183ms

And Go to "TRANSPORT_TABLE" 461ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 022ms

When Go to transport details "LOAD" 2s 872ms

And Fill transport form 28s 938ms

And Get inputs from database "EDIT_ADVICE_LOAD" "super-admin-keeeper" 025ms

And Expand advice panel 269ms

And Edit advice in transport details 21s 550ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 485ms

And Go to transport details "LOAD" 2s 880ms

And Expand advice panel 273ms

Then Check are advice values equals after edition 6s 970ms

Hooks

After Hooks.deleteTransportAfterTest() 982ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to edit advice in transport details.

Steps

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

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 2s 012ms

And Show all transport types 1s 167ms

And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-keeeper" 53s 264ms

And Go to "TRANSPORT_TABLE" 453ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 023ms

When Go to transport details "CONTAINER" 2s 817ms

And Fill transport form 28s 901ms

And Get inputs from database "EDIT_ADVICE_CONTAINER" "super-admin-keeeper" 018ms

And Expand advice panel 239ms

And Edit advice in transport details 21s 469ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 499ms

And Go to transport details "CONTAINER" 2s 850ms

And Expand advice panel 278ms

Then Check are advice values equals after edition 6s 952ms

Hooks

After Hooks.deleteTransportAfterTest() 986ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 588ms

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

And Get inputs from database "EDIT_ADVICE_CONTAINER" "super-admin-adama" 026ms

When Show all transport types 1s 167ms

And Click button advice in transport table "CONTAINER" 243ms

And Set advice window in schedule 3s 045ms

And Fill advice form 15s 903ms

And Click advice save button and wait for advice form to disappear 33s 298ms

And Go to "TRANSPORT_TABLE" 462ms

And Go to transport details "CONTAINER" 2s 841ms

Then Check are advice values equals 871ms

Hooks

After Hooks.deleteTransportAfterTest() 940ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table

Steps

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

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 897ms

And Get inputs from database "ADVICE_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 021ms

When Show all transport types 1s 168ms

And Click button advice in transport table "TRANSFER_BETWEEN_WAREHOUSES" 225ms

And Set advice window in schedule 7s 372ms

And Fill advice form 14s 809ms

And Click advice save button and wait for advice form to disappear 33s 822ms

And Go to "TRANSPORT_TABLE" 462ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 909ms

Then Check are advice values equals 2s 885ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 013ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table

Steps

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 016ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 029ms

When Show all transport types 1s 154ms

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

And Set advice window in schedule 3s 335ms

And Fill advice form 10s 689ms

And Click advice save button and wait for advice form to disappear 33s 336ms

And Go to "TRANSPORT_TABLE" 401ms

And Go to transport details "DELIVERY" 2s 810ms

Then Check are advice values equals 713ms

Hooks

After Hooks.deleteTransportAfterTest() 931ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table

Steps

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

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 2s

And Get inputs from database "ADVICE_LOAD" "super-admin-piast" 024ms

When Show all transport types 1s 163ms

And Click button advice in transport table "LOAD" 285ms

And Set advice window in schedule 3s 325ms

And Fill advice form 10s 707ms

And Click advice save button and wait for advice form to disappear 33s 440ms

And Go to "TRANSPORT_TABLE" 449ms

And Go to transport details "LOAD" 2s 911ms

Then Check are advice values equals 795ms

Hooks

After Hooks.deleteTransportAfterTest() 932ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table

Steps

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 882ms

And Get inputs from database "ADVICE_LOAD" "super-admin-keeeper" 024ms

When Show all transport types 1s 165ms

And Click button advice in transport table "LOAD" 305ms

And Set advice window in schedule 3s 300ms

And Fill advice form 16s 443ms

And Click advice save button and wait for advice form to disappear 33s 867ms

And Go to "TRANSPORT_TABLE" 437ms

And Go to transport details "LOAD" 2s 743ms

Then Check are advice values equals 2s 855ms

Hooks

After Hooks.deleteTransportAfterTest() 862ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table

Steps

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

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 2s 004ms

And Get inputs from database "ADVICE_CONTAINER" "super-admin-keeeper" 023ms

When Show all transport types 1s 170ms

And Click button advice in transport table "CONTAINER" 261ms

And Set advice window in schedule 3s 226ms

And Fill advice form 16s 392ms

And Click advice save button and wait for advice form to disappear 33s 302ms

And Go to "TRANSPORT_TABLE" 461ms

And Go to transport details "CONTAINER" 2s 868ms

Then Check are advice values equals 2s 835ms

Error message

java.lang.AssertionError: Wartości w formularzu w polu driver-language są niepoprawne, wartość na stronie:  wartość poprawna: PL
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Transport.Transport.checkAreValuesEquals(Transport.java:136)
	at CucumberTests.Transport.Transport.checkValueInTransportDetails(Transport.java:258)
	at CucumberTests.Transport.AdviceTransport.checkAdviceValues(AdviceTransport.java:141)
	at ✽.Check are advice values equals(file:Features/Atom/Advice/AdviceTransport.feature:60)

Hooks

After Hooks.deleteTransportAfterTest() 970ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table after passing it on to the carrier

Steps

Given Set token of apiUsername "super-admin-adama" 242ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 142ms

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

And Set token of apiUsername "paa1-carrier@qa.qa-test" 212ms

And Accept transferred transport by Api 867ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 613ms

And Get inputs from database "ADVICE_TRANSPORT" "super-admin-adama" 028ms

When Show all transport types 1s 245ms

And Click button advice in transport table "TRANSPORT" 263ms

And Set advice window in schedule 3s 169ms

And Fill advice form 14s 904ms

And Click advice save button and wait for advice form to disappear 33s 881ms

And Go to "TRANSPORT_TABLE" 470ms

And Go to transport details "TRANSPORT" 2s 907ms

Then Check are advice values equals 2s 932ms

Hooks

After Hooks.deleteTransportAfterTest() 917ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table after passing it on to the carrier

Steps

Given Set token of apiUsername "super-admin-skz" 210ms

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

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

And Set token of apiUsername "pskza1-carrier@qa.qa-test" 211ms

And Accept transferred transport by Api 838ms

And Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 774ms

And Get inputs from database "ADVICE_SMALLS" "super-admin-skz" 019ms

When Show all transport types 1s 212ms

And Click button advice in transport table "SMALLS_IMPORT" 1s 251ms

And Set advice window in schedule 3s 294ms

And Fill advice form 18s 166ms

And Click advice save button and wait for advice form to disappear 33s 851ms

And Go to "TRANSPORT_TABLE" 455ms

And Go to transport details "SMALLS_IMPORT" 2s 883ms

Then Check are advice values equals 2s 942ms

Hooks

After Hooks.deleteTransportAfterTest() 953ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table after passing it on to the carrier

Steps

Given Set token of apiUsername "super-admin-skz" 233ms

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

And Set token of apiUsername "pskza1-carrier@qa.qa-test" 236ms

And Accept transferred transport by Api 811ms

And Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 740ms

And Get inputs from database "ADVICE_SMALLS" "super-admin-skz" 028ms

When Show all transport types 1s 215ms

And Click button advice in transport table "SMALLS_EXPORT" 1s 103ms

And Set advice window in schedule 3s 390ms

And Fill advice form 17s 848ms

And Click advice save button and wait for advice form to disappear 33s 802ms

And Go to "TRANSPORT_TABLE" 446ms

And Go to transport details "SMALLS_EXPORT" 2s 870ms

Then Check are advice values equals 2s 992ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 039ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if the advice restriction blockade windows are visible during advice

Steps

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 106ms

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

And Accept transferred transport by Api 810ms

And Login as "paa1-carrier@qa.qa-test" 2s 455ms

When Show all transport types 1s 242ms

And Click button advice in transport table "TRANSPORT" 249ms

And Set week view 1s 875ms

And Show yesterday 1s 155ms

Then Check if advice restriction blockade windows are visible 061ms

Hooks

After Hooks.deleteTransportAfterTest() 683ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if the advice restriction blockade windows are visible during advice

Steps

Given Set token of apiUsername "super-admin-skz" 238ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 16s 019ms

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

And Accept transferred transport by Api 769ms

And Login as "pskza1-carrier@qa.qa-test" 2s 520ms

When Show all transport types 1s 153ms

And Click button advice in transport table "SMALLS_IMPORT" 1s 348ms

And Set week view 2s 265ms

And Show yesterday 1s 272ms

Then Check if advice restriction blockade windows are visible 060ms

Hooks

After Hooks.deleteTransportAfterTest() 750ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if the advice restriction blockade windows are visible during advice

Steps

Given Set token of apiUsername "super-admin-skz" 227ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 16s 026ms

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

And Accept transferred transport by Api 781ms

And Login as "pskza1-carrier@qa.qa-test" 2s 489ms

When Show all transport types 1s 186ms

And Click button advice in transport table "SMALLS_EXPORT" 1s 240ms

And Set week view 2s 266ms

And Show yesterday 1s 316ms

Then Check if advice restriction blockade windows are visible 057ms

Hooks

After Hooks.deleteTransportAfterTest() 656ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to move advice window in schedule

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 411ms

And Show all transport "false" 099ms

And Click on time window date 1s 690ms

And Select view "DAYS_4" 2s 131ms

And Move advice window "3" 1s 486ms

Then Check if advice window is in new location 068ms

Hooks

After Hooks.deleteTransportAfterTest() 4s 218ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to move advice window in schedule

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 5s 995ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 17s 706ms

And Show all transport "false" 084ms

And Click on time window date 16s 090ms

And Select view "DAYS_4" 2s 177ms

And Move advice window "3" 1s 752ms

Then Check if advice window is in new location 098ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 552ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to move advice window in schedule

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 2s 479ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 16s 629ms

And Show all transport "false" 086ms

And Click on time window date 15s 891ms

And Select view "DAYS_4" 2s 163ms

And Move advice window "3" 1s 673ms

Then Check if advice window is in new location 071ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 903ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to move advice window in schedule

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 904ms

And Show all transport "false" 089ms

And Click on time window date 1s 955ms

And Select view "DAYS_4" 2s 174ms

And Move advice window "3" 1s 581ms

Then Check if advice window is in new location 072ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 827ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to move advice window in schedule

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 991ms

And Show all transport "false" 087ms

And Click on time window date 1s 737ms

And Select view "DAYS_4" 2s 134ms

And Move advice window "3" 1s 458ms

Then Check if advice window is in new location 071ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 840ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to move advice window in schedule

Steps

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

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

And Show all transport "true" 261ms

And Click on time window date 1s 764ms

And Select view "DAYS_4" 2s 176ms

And Move advice window "3" 1s 526ms

Then Check if advice window is in new location 069ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 340ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add advice and move advice window in schedule

Steps

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 024ms

And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 012ms

When Show all transport types 1s 158ms

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

And Set advice window in schedule 3s 311ms

And Fill advice form 10s 638ms

And Click advice save button and wait for advice form to disappear 33s 294ms

And Go to "TRANSPORT_TABLE" 444ms

And Click on time window date 1s 791ms

And Select view "DAYS_4" 2s 166ms

And Move advice window "3" 1s 624ms

Then Check if advice window is in new location 068ms

Hooks

After Hooks.deleteTransportAfterTest() 4s 857ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if late advice is red

Steps

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

And Create transport "CREATE_LATE_DELIVERY" by JSON file as "super-admin-hochland" in "0" days 3s 106ms

Then Check if transport row is "red" 3s 241ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 040ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to resize advice window in schedule

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 208ms

And Go to "TRANSPORT_TABLE" 413ms

And Show all transport types 1s 141ms

And Click on time window date 1s 723ms

And Scroll to time window "adviceWindow" 159ms

And Set time window height "2" "adviceWindow" 5s 614ms

Then Check height of the time window after expanding by "2" in "adviceWindow" 073ms

Hooks

After Hooks.deleteTransportAfterTest() 974ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to resize advice window in schedule

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 815ms

And Go to "TRANSPORT_TABLE" 376ms

And Show all transport types 1s 129ms

And Click on time window date 1s 806ms

And Scroll to time window "adviceWindow" 128ms

And Set time window height "4" "adviceWindow" 5s 622ms

Then Check height of the time window after expanding by "4" in "adviceWindow" 064ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 050ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to resize advice window in schedule

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 3s 106ms

And Go to "TRANSPORT_TABLE" 460ms

And Show all transport types 1s 148ms

And Click on time window date 1s 689ms

And Scroll to time window "adviceWindow" 129ms

And Set time window height "3" "adviceWindow" 5s 628ms

Then Check height of the time window after expanding by "3" in "adviceWindow" 071ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 023ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to resize advice window in schedule

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 2s 373ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 17s 152ms

And Go to "TRANSPORT_TABLE" 558ms

And Show all transport types 15s 034ms

And Click on time window date 16s 144ms

And Scroll to time window "adviceWindow" 240ms

And Set time window height "1" "adviceWindow" 5s 661ms

Then Check height of the time window after expanding by "1" in "adviceWindow" 067ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 340ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to resize advice window in schedule after add advice by advice button in transport table

Steps

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 046ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 022ms

When Show all transport types 1s 158ms

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

And Set advice window in schedule 3s 315ms

And Fill advice form 10s 598ms

And Click advice save button and wait for advice form to disappear 33s 280ms

And Go to "TRANSPORT_TABLE" 477ms

And Click on time window date 1s 826ms

And Set time window height "2" "adviceWindow" 5s 634ms

Then Check height of the time window after expanding by "2" in "adviceWindow" 064ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 801ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice after clicking back button in browser

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-hochland" 021ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 964ms

And Go to "WAREHOUSE_TAB" 1s 154ms

And Select warehouse "Twarożkarnia wyrób gotowy" 2s 179ms

When Go to new transport "DELIVERY" 680ms

And Fill transport form 44s 993ms

And Click "save-transport" save button and wait for form to disappear 1s 033ms

And Click previous page button in browser 059ms

Then Check if advice window can't be created 2s 928ms

Hooks

After Hooks.deleteTransportAfterTest() 001ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice after modifing warehouse id in browser url

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-hochland" 023ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 948ms

And Go to "WAREHOUSE_TAB" 1s 143ms

And Select warehouse "Twarożkarnia wyrób gotowy" 2s 207ms

When Go to new transport "DELIVERY" 697ms

And Fill transport form 44s 784ms

And Click "save-transport" save button and wait for form to disappear 882ms

And Replace warehouse id in browser url with "Twarożkarnia wyrób gotowy" id 197ms

Then Check if advice window can't be created 2s 597ms

Hooks

After Hooks.deleteTransportAfterTest() 001ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if transport without warehouse after carrier add advice has checkpoint steps

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 722ms

And Create transport "CREATE_TRANSPORT_WITHOUT_WAREHOUSES" by JSON file as "super-admin-adama" 2s 382ms

And Transfer transport to carrier by JSON file "super-admin-adama" "false" confirmation 1s 053ms

And Get inputs from database "ADVICE_TRANSPORT" "super-admin-adama" 016ms

When Show all transport types 1s 157ms

And Click button advice in transport table "TRANSPORT" 231ms

And Fill advice form 13s 916ms

And Click advice save button and wait for advice form to disappear 33s 215ms

When Find transport in table with status "no-advice-undefined" 3s 623ms

And Open statuses popup 192ms

And Wait "2" seconds 2s

Then Check if transport has checkpoints from list "Zgłoszenie się kierowcy,Zakończenie załadunku,Dostarczenie do klienta" in "1" 173ms

Hooks

After Hooks.deleteTransportAfterTest() 636ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if time window details preview displays correctly

Steps

Given Set token of apiUsername "super-admin-farmacol" 217ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 2s 050ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 4s 003ms

And Login as "farmacol-admin" 2s 286ms

And Go to "WAREHOUSE_TAB" 1s 083ms

And Select warehouse "Katowice Przyjęcia" 1s 408ms

And Set week view 2s 704ms

And Move cursor over time window element 484ms

Then Check if "Zaawizowany" "31415" "06:00" "GDA12345" are visible on time window popup details 259ms

Hooks

After Hooks.deleteTransportAfterTest() 780ms

View Feature Advice transport

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline Check if it is possible to advice transport after splitting advice data from advice window

- order: advice data => advice window [A-7478]

Steps

Given Login as "pba1-carrier" and set token of apiUsername "super-admin-bausch" 4s 949ms

And Create default accepted mode of transportation by API with "pba1-carrier" 1s 857ms

And Create transport "CREATE_EXW_DELIVERY" by JSON file as "super-admin-bausch" 2s 237ms

And Set "advice" inputs from JSON file "ADVICE_EXW_DELIVERY" "super-admin-bausch" 005ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "true" confirmation 930ms

When Go to "TRANSPORT_TABLE" 403ms

And Show all transport types 1s 162ms

And Click button advice in transport table "EXW_DELIVERY" 607ms

And Fill advice form 10s 563ms

And Click advice save button and wait for advice form to disappear 33s 272ms

And Click button advice in transport table "EXW_DELIVERY" 254ms

And Set advice window in schedule 3s 247ms

And Change filled value in transport details "rodo-acceptance" "checkbox" "true" "0" 2s 502ms

And Click advice save button and wait for advice form to disappear 33s 904ms

And Go to "TRANSPORT_TABLE" 466ms

And Show all transport types 1s 161ms

And Go to transport details "EXW_DELIVERY" 2s 958ms

Then Check are advice values equals 2s 655ms

Hooks

After Hooks.deleteTransportAfterTest() 940ms

After Hooks.deleteModeOfTransportationAfterTest() 351ms

View Feature Company Resources

@deleteTransportAfterTest

Scenario Outline Check if it possible to save resource to company from transport form

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY_CONTRACTOR" "super-admin-neuca" 002ms

And Login as "pna1-carrier" and set token of apiUsername "super-admin-neuca" 2s 365ms

And Go to new transport "DELIVERY" 15s 604ms

And Fill transport form 38s 380ms

And Select "save-as-resource" checkbox 385ms

When Click "save-transport" save button and wait for form to disappear 15s 777ms

And Set advice window in schedule 2s 405ms

And Check is transport created in schedule and set transport id 3s 955ms

Then Go to "OWN_COMPANY_TAB" 717ms

And Check if advice values are visible in company resources 402ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 070ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

When Go to "TRANSPORT_TABLE" 370ms

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

And Show all transport types 1s 193ms

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

Hooks

After Hooks.deleteTransportAfterTest() 708ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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" 2s 667ms

When Go to "TRANSPORT_TABLE" 446ms

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

And Show all transport types 1s 205ms

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

Hooks

After Hooks.deleteTransportAfterTest() 779ms

View Feature Filters

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

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

When Go to "TRANSPORT_TABLE" 396ms

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

And Show all transport types 1s 181ms

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

Hooks

After Hooks.deleteTransportAfterTest() 735ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 411ms

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

And Show all transport types 1s 199ms

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

Hooks

After Hooks.deleteTransportAfterTest() 783ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 788ms

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

When Go to "ARCHIVE_TAB" 489ms

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

And Show "SMALLS_IMPORT" 179ms

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

Hooks

After Hooks.deleteTransportAfterTest() 920ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 725ms

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

When Go to "ARCHIVE_TAB" 488ms

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

And Show "SMALLS_IMPORT" 148ms

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

Hooks

After Hooks.deleteTransportAfterTest() 815ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 685ms

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

When Go to "ARCHIVE_TAB" 487ms

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

And Show "SMALLS_IMPORT" 168ms

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 107ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if transport in archive 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" 16s 145ms

And Delete created transport by API 683ms

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

When Go to "ARCHIVE_TAB" 484ms

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

And Show "SMALLS_IMPORT" 171ms

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

Hooks

After Hooks.deleteTransportAfterTest() 917ms

View Feature Filters

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

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

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

And Go to "TRANSPORT_TABLE" 423ms

And Show all transport "true" 252ms

And Select transportType "TRANSPORT_ORDER" 1s 297ms

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

Hooks

After Hooks.deleteTransportAfterTest() 723ms

View Feature Filters

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

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

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

And Accept transferred transport by Api 758ms

And Create advice "ADVICE_SMALLS" "SMALLS_IMPORT" "super-admin-skz" 57s 265ms

And Delete created transport by API 1s 075ms

When Go to "ARCHIVE_TAB" 525ms

And Show "SMALLS_IMPORT" 180ms

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 096ms

View Feature Filters

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

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

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

And Accept transferred transport by Api 766ms

And Create advice "ADVICE_SMALLS" "SMALLS_EXPORT" "super-admin-skz" 57s 853ms

And Delete created transport by API 1s 038ms

When Go to "ARCHIVE_TAB" 529ms

And Show "SMALLS_EXPORT" 190ms

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

Hooks

After Hooks.deleteTransportAfterTest() 990ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

And Login as "neuca-admin" 2s 194ms

And Go to "TRANSPORT_TABLE" 476ms

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

And Toggle transport table days limit filter 190ms

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 028ms

View Feature Grouping of carriers

@deleteTransportAfterTest @removeContractorsGroup

Scenario Outline Check if company is selected in inquiry after adding company to contractors group and selecting contractors group

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 747ms

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

And Add carrier "Przewoźnik SKZ Automat 1" to carriers group "Kraj" by Api as "super-admin-skz" 566ms

When Go to "TRANSPORT_TABLE" 460ms

And Go to auction form 1s 607ms

And Select contractors group "Kraj" 249ms

Then Verify that carrier "PSKZA1" is selected 074ms

Hooks

After Hooks.deleteTransportAfterTest() 729ms

After Hooks.removeContractorsGroup() 302ms

View Feature Grouping of carriers

@deleteTransportAfterTest

Scenario Outline Check if all contractors group are selected in inquiry after click in all contractors group checkbox

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 562ms

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

When Go to "TRANSPORT_TABLE" 480ms

And Go to auction form 1s 536ms

And Select contractors group "Wybierz grupę firm transportowych" 246ms

Then Verify that all companies are selected after choose "data-group-name" 339ms

Hooks

After Hooks.deleteTransportAfterTest() 743ms

View Feature Grouping of carriers

@deleteTransportAfterTest

Scenario Outline Check if all companies are selected in inquiry after selecting all companies

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 571ms

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

When Go to "TRANSPORT_TABLE" 470ms

And Go to auction form 1s 514ms

And Select contractors group "Wybierz uczestników zapytania" 252ms

Then Verify that all companies are selected after choose "data-carrier-name" 182ms

Hooks

After Hooks.deleteTransportAfterTest() 726ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if it possible to add new index to transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 928ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 120ms

And Show all transport "false" 079ms

And Get inputs from database "ADD_INDEX" "super-admin-adama" 017ms

And Create product if needed "false" by api for principal "adama" 202ms

When Go to transport details "TRANSPORT" 2s 909ms

And Expand index panel 274ms

And Click add index button 317ms

And Fill index form 11s 655ms

And Click ok button in index form 15s 291ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 951ms

And Go to transport details "TRANSPORT" 2s 899ms

And Expand index panel 271ms

Then Check are transport values equals 304ms

Hooks

After Hooks.deleteTransportAfterTest() 661ms

After Hooks.deleteProductAfterTest() 194ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if it possible to add new index to transport

Steps

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

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

And Show all transport "true" 233ms

And Get inputs from database "ADD_INDEX" "super-admin-alrec" 024ms

And Create product if needed "true" by api for principal "alrec" 000ms

When Go to transport details "TRANSPORT_ORDER" 2s 827ms

And Expand index panel 334ms

And Click add index button 392ms

And Fill index form 8s 601ms

And Click ok button in index form 15s 241ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 913ms

And Go to transport details "TRANSPORT_ORDER" 2s 899ms

And Expand index panel 286ms

Then Check are transport values equals 2s 395ms

Hooks

After Hooks.deleteTransportAfterTest() 628ms

After Hooks.deleteProductAfterTest() 000ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if it possible to delete index in transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 474ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 125ms

And Show all transport "false" 076ms

And Get inputs from database "ADD_INDEX" "super-admin-adama" 017ms

And Create product if needed "false" by api for principal "adama" 120ms

When Go to transport details "TRANSPORT" 2s 834ms

And Add index to transport 27s 651ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 913ms

When Go to transport details "TRANSPORT" 2s 868ms

And Expand index panel 264ms

And Click delete index button 181ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 869ms

And Go to transport details "TRANSPORT" 2s 742ms

And Expand index panel 290ms

Then Verify that transport has no indexes 15s 036ms

Hooks

After Hooks.deleteTransportAfterTest() 691ms

After Hooks.deleteProductAfterTest() 144ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if it possible to delete index in transport

Steps

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

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

And Show all transport "true" 250ms

And Get inputs from database "ADD_INDEX" "super-admin-alrec" 025ms

And Create product if needed "true" by api for principal "alrec" 000ms

When Go to transport details "TRANSPORT_ORDER" 2s 862ms

And Add index to transport 24s 606ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 944ms

When Go to transport details "TRANSPORT_ORDER" 2s 794ms

And Expand index panel 223ms

And Click delete index button 144ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 836ms

And Go to transport details "TRANSPORT_ORDER" 2s 750ms

And Expand index panel 270ms

Then Verify that transport has no indexes 15s 073ms

Hooks

After Hooks.deleteTransportAfterTest() 641ms

After Hooks.deleteProductAfterTest() 000ms

View Feature Index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if indexes displayed after click indexes datails icon on time window

Steps

Given Login as "dayco-admin" and set token of apiUsername "super-admin-dayco" 5s 097ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 113ms

And Get inputs from database "ADD_INDEX" "super-admin-dayco" 024ms

And Create product if needed "false" by api for principal "dayco" 109ms

And Go to transport details "OWN_COLLECTION" 2s 910ms

And Add index to transport 25s 850ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 962ms

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 45s 994ms

When Click on index details icon 214ms

Then Verify that indexes display in window "product-index;quantity-of-Planned quantity;quantity-of-Quantity sent" 001ms

Hooks

After Hooks.deleteTransportAfterTest() 902ms

After Hooks.deleteProductAfterTest() 137ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after creating advice

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 405ms

And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 082ms

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

And Get inputs from database "ADVICE_CONTAINER" "super-admin-adama" 024ms

And Show all transport types 1s 162ms

And Click button advice in transport table "CONTAINER" 251ms

And Set advice window in schedule 3s 170ms

And Fill advice form 14s 634ms

And Click advice save button and wait for advice form to disappear 33s 804ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zapisano awizację! | Advice has been saved!" 8s 081ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 925ms

After Hooks.cleanUserDetailsAfterTest() 1s 306ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after creating advice

Steps

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

And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 948ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 056ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 025ms

And Show all transport types 1s 199ms

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

And Set advice window in schedule 3s 377ms

And Fill advice form 10s 661ms

And Click advice save button and wait for advice form to disappear 33s 291ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zapisano awizację! | Advice has been saved!" 7s 592ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 966ms

After Hooks.cleanUserDetailsAfterTest() 1s 046ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after creating advice

Steps

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

And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 782ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 937ms

And Get inputs from database "ADVICE_LOAD" "super-admin-keeeper" 021ms

And Show all transport types 1s 162ms

And Click button advice in transport table "LOAD" 252ms

And Set advice window in schedule 3s 258ms

And Fill advice form 16s 417ms

And Click advice save button and wait for advice form to disappear 33s 255ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zapisano awizację! | Time window has been saved!" 7s 673ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 955ms

After Hooks.cleanUserDetailsAfterTest() 1s 458ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after editing advice

Steps

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

And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 389ms

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

And Show all transport types 1s 173ms

And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 51s 289ms

And Go to "TRANSPORT_TABLE" 453ms

And Go to transport details "CONTAINER" 2s 835ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 020ms

When Go to transport details "CONTAINER" 3s 574ms

And Fill transport form 5s 174ms

And Get inputs from database "EDIT_ADVICE_CONTAINER" "super-admin-adama" 025ms

And Expand advice panel 247ms

And Edit advice in transport details 15s 027ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 474ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zmiana w awizacji numer" 1m 10s 772ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 857ms

After Hooks.cleanUserDetailsAfterTest() 1s 337ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after editing advice

Steps

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

And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 178ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 992ms

And Show all transport types 1s 167ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 47s 175ms

And Go to "TRANSPORT_TABLE" 473ms

And Go to transport details "DELIVERY" 2s 870ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-piast" 030ms

When Go to transport details "DELIVERY" 3s 752ms

And Fill transport form 1m 8s 829ms

And Get inputs from database "EDIT_ADVICE_DELIVERY" "super-admin-piast" 018ms

And Expand advice panel 270ms

And Edit advice in transport details 8s 046ms

And Click "save-transport-and-close" save button and wait for form to disappear 18s 553ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zmiana w awizacji numer" 7s 857ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 046ms

After Hooks.cleanUserDetailsAfterTest() 1s 079ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after editing advice

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 6s 108ms

And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 671ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 962ms

And Show all transport types 1s 173ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 53s 149ms

And Go to "TRANSPORT_TABLE" 396ms

And Go to transport details "LOAD" 2s 790ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 021ms

When Go to transport details "LOAD" 3s 599ms

And Fill transport form 28s 635ms

And Get inputs from database "EDIT_ADVICE_LOAD" "super-admin-keeeper" 023ms

And Expand advice panel 263ms

And Edit advice in transport details 21s 495ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 454ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zmiana w awizacji numer" 57s 785ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 037ms

After Hooks.cleanUserDetailsAfterTest() 1s 579ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after status confirmation

Steps

Given Set token of apiUsername "super-admin-skd" 237ms

And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 869ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 2s 700ms

And Confirm status "ARRIVAL" by Public API "v1" 1s 071ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Potwierdzono status Wjazd na teren zakładu" 7s 494ms

Then Check if user got a mail 000ms

And Confirm status "DEPARTURE" by Public API "v1" 1s 286ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Potwierdzono status Wyjazd" 57s 014ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 931ms

After Hooks.cleanUserDetailsAfterTest() 914ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackVerificationEmailSettingAfterTest

Scenario Outline Check if verification mail was sent to transport creator

Steps

Given Set token of apiUsername "super-admin-hochland" 239ms

And Prepare company "Dostawca Hochland Automat 1" verification email setting "48h" 038ms

And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 861ms

And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "dha1-supplier-2@qa.qa-test" 8s 315ms

And Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2@qa.qa-test" 16s 971ms

And Wait "120" seconds 2m

When Get mail "apolloautomattest@gmail.com" message from mail account with "Weryfikacja danych awizacji" 7s 608ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 881ms

After Hooks.cleanUserDetailsAfterTest() 1s 432ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 040ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating a new auction

Steps

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

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 135ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 098ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 3s 224ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Nowa aukcja" 26s 271ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 815ms

After Hooks.cleanUserDetailsAfterTest() 1s 970ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing auction

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 369ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 274ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 121ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 958ms

And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 162ms

And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 2s 102ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Nie otrzymano zlecenia" 7s 144ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 699ms

After Hooks.cleanUserDetailsAfterTest() 2s 032ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after bid has been added to auction

Steps

Given Login as "swisskrono-producer" and set token of apiUsername "super-admin-skz" 12s 405ms

And Prepare user "swisskrono-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 983ms

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

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 854ms

And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 955ms

And Wait till auction end 1m 57s 019ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Dodano nową ofertę" 8s 404ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 757ms

After Hooks.cleanUserDetailsAfterTest() 1s 768ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after auction without bids

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 501ms

And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 520ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 069ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 3s 022ms

And Wait till auction end 1m 57s 017ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Aukcja zakończona bez ofert" 45s 172ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 683ms

After Hooks.cleanUserDetailsAfterTest() 1s 296ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing first place in auction

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 837ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 295ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 076ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 959ms

And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 015ms

And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 1s 898ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Oferta przelicytowana" 13s 901ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 713ms

After Hooks.cleanUserDetailsAfterTest() 1s 963ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after winning an auction

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 446ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 343ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 062ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 997ms

And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 991ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Otrzymano zlecenie" 2m 17s 763ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 795ms

After Hooks.cleanUserDetailsAfterTest() 2s 022ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after accepting minimal price

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 309ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 330ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 153ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 967ms

And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 764ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Otrzymano zlecenie" 13s 420ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 678ms

After Hooks.cleanUserDetailsAfterTest() 1s 953ms

View Feature Discrepancy Report Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after discrepancy report generation

Steps

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

And Prepare user "hochland-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 3s 994ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 181ms

And Go to "TRANSPORT_TABLE" 394ms

And Go to transport details "DELIVERY" 2s 868ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 017ms

And Fill transport form 40s 537ms

And Open section: "discrepancy-report-panel" 1s 170ms

And Fill discrepancy report section 40s 914ms

And Go to transport details "DELIVERY" 2s 890ms

And Change filled value in transport details "rodo-acceptance" "checkbox" "true" "0" 1s 551ms

And Generate discrepancy report 23s 989ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Utworzono protokół niezgodności" 3m 21s 162ms

Then Check if user got a mail 000ms

Error message

java.lang.AssertionError: Użytkownik nie otrzymał maila. Actual: 
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failEquals(Assert.java:185)
	at org.junit.Assert.assertNotEquals(Assert.java:161)
	at CucumberTests.Mail.MailTest.checkIfUseGotMail(MailTest.java:39)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/DiscrepancyReportMail.feature:18)

Hooks

After Hooks.deleteTransportAfterTest() 996ms

After Hooks.cleanUserDetailsAfterTest() 3s 702ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after transport creation

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 9s 873ms

And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 350ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Drobnica import" 55s 712ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 685ms

After Hooks.cleanUserDetailsAfterTest() 2s 150ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after transport creation

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 309ms

And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 187ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Drobnica eksport" 1m 3s 818ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 720ms

After Hooks.cleanUserDetailsAfterTest() 2s 306ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @FLAKY-A-7913

Scenario Outline Check if mail was sent to carrier after transport transfer

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 674ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 446ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 066ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 15s 167ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='PASS'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=91.0.4472.101 (af52a90bf87030dd1523486a1cd3ae25c5d76c9b-refs/branch-heads/4472@{#1462}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.F2003R}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=91.0.4472.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 714ed1bdab8f41cbbbe0aae0f0ccfe67
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:215)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:285)
	at CucumberTests.Transport.TransferTransportTest.transferTransportToCarrier(TransferTransportTest.java:37)
	at ✽.Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true"(file:Features/Atom/Mail/TransportTransferMail.feature:8)

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zlecenie czeka na akceptację" 000ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 722ms

After Hooks.cleanUserDetailsAfterTest() 1s 996ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @FLAKY-A-7913

Scenario Outline Check if mail was sent to carrier after transport transfer with no confirmation

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 427ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 291ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 107ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 15s 219ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='PASS'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=91.0.4472.101 (af52a90bf87030dd1523486a1cd3ae25c5d76c9b-refs/branch-heads/4472@{#1462}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.F2003R}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=91.0.4472.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 714ed1bdab8f41cbbbe0aae0f0ccfe67
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:215)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:285)
	at CucumberTests.Transport.TransferTransportTest.transferTransportToCarrier(TransferTransportTest.java:37)
	at ✽.Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false"(file:Features/Atom/Mail/TransportTransferMail.feature:20)

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zostało przekazane nowe zlecenie" 000ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 634ms

After Hooks.cleanUserDetailsAfterTest() 1s 870ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating new inquiry

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 326ms

And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 150ms

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

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 3s 015ms

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nowe zapytanie ofertowe" 31s 357ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 758ms

After Hooks.cleanUserDetailsAfterTest() 1s 716ms

View Feature Pallet limit

@deleteTransportAfterTest

Scenario Outline Verify that the error is visible after exceeding the pallet limit during create transport

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-neuca" 002ms

And Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 2s 477ms

When Go to new transport "DELIVERY" 15s 522ms

And Fill transport form 46s 127ms

And Change filled value in transport details "number-of-pallets-step-0" "number" "1000000" "0" 1s 658ms

And Click "save-transport" save button and wait for form to disappear 15s 756ms

And Set advice window in schedule 2s 398ms

Then Verify that the error is visible after exceeding the pallet limit 670ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

View Feature Pallet limit

@deleteTransportAfterTest

Scenario Outline Verify that the error is visible after exceeding the pallet limit during edit transport

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 2s 508ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 16s 988ms

And Go to "TRANSPORT_TABLE" 570ms

And Show all transport "false" 079ms

And Go to transport details "DELIVERY" 30s 727ms

And Change filled value in transport details "number-of-pallets-step-0" "number" "1000000" "0" 1s 699ms

And Click "save-transport" save button 1s 475ms

Then Verify that the error is visible after exceeding the pallet limit 072ms

Hooks

After Hooks.deleteTransportAfterTest() 878ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

Scenario Outline Check that the appropriate means of transport are not visible during the advice [A-6256]

Steps

Given Set token of apiUsername "super-admin-bausch" 237ms

And Create default mode of transportation by API with "pba1-carrier" 575ms

And Set status of MOT to "AWAITING_VERIFICATION" 255ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 16s 189ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 737ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 386ms

When Login as "super-admin-bausch" 5s 998ms

And Go to "TRANSPORT_TABLE" 437ms

And Click button advice in transport table "LOAD_EXPORT" 200ms

And Set advice window in schedule 3s 265ms

Then Check if "AAAA0000" MOT is NOT visible in advice form 16s 483ms

Hooks

After Hooks.deleteTransportAfterTest() 774ms

After Hooks.deleteModeOfTransportationAfterTest() 303ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

Scenario Outline Check that the appropriate means of transport are not visible during the advice [A-6256]

Steps

Given Set token of apiUsername "super-admin-bausch" 217ms

And Create default mode of transportation by API with "pba1-carrier" 462ms

And Set status of MOT to "DISABLED" 288ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 16s 153ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 736ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 390ms

When Login as "super-admin-bausch" 2s 441ms

And Go to "TRANSPORT_TABLE" 468ms

And Click button advice in transport table "LOAD_EXPORT" 260ms

And Set advice window in schedule 3s 277ms

Then Check if "AAAA0000" MOT is NOT visible in advice form 16s 503ms

Hooks

After Hooks.deleteTransportAfterTest() 766ms

After Hooks.deleteModeOfTransportationAfterTest() 253ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

Scenario Outline Check that the appropriate means of transport are visible during the advice [A-6256]

Steps

Given Set token of apiUsername "super-admin-bausch" 221ms

And Create default mode of transportation by API with "pba1-carrier" 442ms

And Set status of MOT to "ACCEPTED" 285ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 16s 104ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 721ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 384ms

When Login as "super-admin-bausch" 2s 549ms

And Go to "TRANSPORT_TABLE" 470ms

And Click button advice in transport table "LOAD_EXPORT" 269ms

And Set advice window in schedule 3s 307ms

Then Check if "AAAA0000" MOT can be selected in advice form 1s 585ms

Hooks

After Hooks.deleteTransportAfterTest() 654ms

After Hooks.deleteModeOfTransportationAfterTest() 333ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

Scenario Outline Check that the appropriate means of transport are visible during the advice [A-6256]

Steps

Given Set token of apiUsername "super-admin-bausch" 224ms

And Create default mode of transportation by API with "pba1-carrier" 472ms

And Set status of MOT to "UPDATED" 312ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 16s 174ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 850ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 432ms

When Login as "super-admin-bausch" 2s 447ms

And Go to "TRANSPORT_TABLE" 403ms

And Click button advice in transport table "LOAD_EXPORT" 298ms

And Set advice window in schedule 3s 175ms

Then Check if "AAAA0000" MOT can be selected in advice form 1s 545ms

Hooks

After Hooks.deleteTransportAfterTest() 710ms

After Hooks.deleteModeOfTransportationAfterTest() 280ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

Scenario Outline Check that the appropriate means of transport are visible but not available during the advice [A-6256]

Steps

Given Set token of apiUsername "super-admin-bausch" 236ms

And Create default mode of transportation by API with "pba1-carrier" 471ms

And Set status of MOT to "REJECTED" 303ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 16s 114ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 718ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 394ms

When Login as "super-admin-bausch" 2s 496ms

And Go to "TRANSPORT_TABLE" 378ms

And Click button advice in transport table "LOAD_EXPORT" 322ms

And Set advice window in schedule 3s 318ms

Then Check if "AAAA0000" MOT is visible in advice form 1s 495ms

And Check if "AAAA0000" MOT cannot be selected in advice form 15s 481ms

Hooks

After Hooks.deleteTransportAfterTest() 678ms

After Hooks.deleteModeOfTransportationAfterTest() 308ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

Scenario Outline Check that the appropriate means of transport are visible but not available during the advice [A-6256]

Steps

Given Set token of apiUsername "super-admin-bausch" 222ms

And Create default mode of transportation by API with "pba1-carrier" 457ms

And Set status of MOT to "BLOCKED" 269ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 16s 117ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 645ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 368ms

When Login as "super-admin-bausch" 2s 433ms

And Go to "TRANSPORT_TABLE" 355ms

And Click button advice in transport table "LOAD_EXPORT" 327ms

And Set advice window in schedule 3s 238ms

Then Check if "AAAA0000" MOT is visible in advice form 1s 509ms

And Check if "AAAA0000" MOT cannot be selected in advice form 15s 470ms

Hooks

After Hooks.deleteTransportAfterTest() 698ms

After Hooks.deleteModeOfTransportationAfterTest() 297ms

View Feature SK Api - Statuses confirmation

@deleteTransportAfterTest

Scenario Outline Check if it is possible to confirm statuses by SkApi

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 574ms

When Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 021ms

And Add transport by SKApi in "MGW" 1s 862ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 37s 500ms

And Click button advice in transport table "TRANSPORT_ORDER" 234ms

And Set advice window in schedule 3s 366ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 016ms

And Fill advice form 18s 108ms

And Click advice save button and wait for advice form to disappear 33s 847ms

And Find transport in table with status "planned" 3s 804ms

And Confirm statuses until reach "left-the-factory" through SKAPI 5m 8s 228ms

Then Check if transport has "left-the-factory" 079ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 102ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi

Steps

Given Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 024ms

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

When Add transport by SKApi in "MGW" 020ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 48s 764ms

And Go to "TRANSPORT_TABLE" 402ms

And Go to transport details "TRANSPORT_ORDER" 2s 837ms

Then Check are transport values equals 1s 287ms

Hooks

After Hooks.deleteTransportAfterTest() 700ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi

Steps

Given Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 018ms

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

When Add transport by SKApi in "MGW" 022ms

Then Check is transport "CONTAINER" created in transport table and set transport id 52s 023ms

And Go to "TRANSPORT_TABLE" 387ms

And Go to transport details "CONTAINER" 2s 863ms

Then Check are transport values equals 1s 313ms

Hooks

After Hooks.deleteTransportAfterTest() 717ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi

Steps

Given Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 021ms

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

When Add transport by SKApi in "MGW" 020ms

Then Check is transport "OWN_COLLECTION" created in transport table and set transport id 52s 192ms

And Go to "TRANSPORT_TABLE" 389ms

And Go to transport details "OWN_COLLECTION" 2s 868ms

Then Check are transport values equals 1s 331ms

Hooks

After Hooks.deleteTransportAfterTest() 708ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi

Steps

Given Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 018ms

And Login as "swisskrono-admin-10" and set token of apiUsername "super-admin-skz" 9s 680ms

When Add transport by SKApi in "HRL" 021ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 43s 600ms

And Go to "TRANSPORT_TABLE" 412ms

And Go to transport details "TRANSPORT_ORDER" 2s 829ms

Then Check are transport values equals 1s 331ms

Hooks

After Hooks.deleteTransportAfterTest() 748ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi

Steps

Given Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 024ms

And Login as "swisskrono-admin-10" and set token of apiUsername "super-admin-skz" 2s 672ms

When Add transport by SKApi in "HRL" 020ms

Then Check is transport "CONTAINER" created in transport table and set transport id 52s 010ms

And Go to "TRANSPORT_TABLE" 406ms

And Go to transport details "CONTAINER" 2s 853ms

Then Check are transport values equals 1s 347ms

Hooks

After Hooks.deleteTransportAfterTest() 696ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi

Steps

Given Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 020ms

And Login as "swisskrono-admin-10" and set token of apiUsername "super-admin-skz" 2s 693ms

When Add transport by SKApi in "HRL" 021ms

Then Check is transport "OWN_COLLECTION" created in transport table and set transport id 52s 224ms

And Go to "TRANSPORT_TABLE" 397ms

And Go to transport details "OWN_COLLECTION" 2s 838ms

Then Check are transport values equals 1s 308ms

Hooks

After Hooks.deleteTransportAfterTest() 803ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi with specific client name

Steps

Given Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 024ms

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

And Set another client name "Pepsi" 000ms

When Add transport by SKApi in "MGW" 020ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 51s 763ms

And Check client name in database "Pepsi" "TRANSPORT_ORDER" 108ms

Hooks

After Hooks.deleteTransportAfterTest() 723ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it transport created by SKApi without `warehouse_alias` field is in default warehouse

Steps

Given Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 018ms

And Login as "swisskrono-admin-10" and set token of apiUsername "super-admin-skz" 2s 603ms

When Add transport by SKApi in "" 020ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 55s 492ms

And Go to "TRANSPORT_TABLE" 402ms

And Go to transport details "TRANSPORT_ORDER" 2s 842ms

Then Check if transport has warehouse "MGW" in step section "0" 157ms

Hooks

After Hooks.deleteTransportAfterTest() 774ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to advice transport when transport is created by sk API

The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 758ms

And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 021ms

And Add transport by SKApi in "MGW" 022ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 016ms

And Check is transport "CONTAINER" created in transport table and set transport id 55s 016ms

When Click button advice in transport table "CONTAINER" 227ms

And Set advice window in schedule 3s 373ms

And Fill advice form 17s 941ms

And Click advice save button and wait for advice form to disappear 33s 883ms

And Go to "TRANSPORT_TABLE" 445ms

And Go to transport details "CONTAINER" 2s 914ms

Then Check are advice values equals 2s 931ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 070ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to advice transport when transport is created by sk API

The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 670ms

And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 022ms

And Add transport by SKApi in "MGW" 020ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 017ms

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 55s 210ms

When Click button advice in transport table "OWN_COLLECTION" 223ms

And Set advice window in schedule 3s 373ms

And Fill advice form 17s 942ms

And Click advice save button and wait for advice form to disappear 33s 850ms

And Go to "TRANSPORT_TABLE" 480ms

And Go to transport details "OWN_COLLECTION" 2s 910ms

Then Check are advice values equals 2s 936ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 104ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to advice transport when transport is created by sk API

The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 734ms

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms

And Add transport by SKApi in "MGW" 025ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 019ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 51s 713ms

When Click button advice in transport table "TRANSPORT_ORDER" 201ms

And Set advice window in schedule 3s 338ms

And Fill advice form 18s 057ms

And Click advice save button and wait for advice form to disappear 33s 892ms

And Go to "TRANSPORT_TABLE" 483ms

And Go to transport details "TRANSPORT_ORDER" 2s 903ms

Then Check are advice values equals 2s 903ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 029ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Verify that advice data are saved properly

The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 639ms

And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 023ms

And Add transport by SKApi in "MGW" 021ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 018ms

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 55s 228ms

When Click button advice in transport table "OWN_COLLECTION" 228ms

And Set advice window in schedule 3s 379ms

And Fill advice form 18s 071ms

And Click advice save button and wait for advice form to disappear 33s 826ms

And Go to "TRANSPORT_TABLE" 457ms

Then Check advice data in SK API database "OWN_COLLECTION" 410ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 110ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Verify that advice data are saved properly

The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 687ms

And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 021ms

And Add transport by SKApi in "MGW" 020ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 016ms

And Check is transport "CONTAINER" created in transport table and set transport id 1m 1s 020ms

When Click button advice in transport table "CONTAINER" 235ms

And Set advice window in schedule 3s 433ms

And Fill advice form 17s 835ms

And Click advice save button and wait for advice form to disappear 33s 837ms

And Go to "TRANSPORT_TABLE" 460ms

Then Check advice data in SK API database "CONTAINER" 201ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 026ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Verify that advice data are saved properly

The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 624ms

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 022ms

And Add transport by SKApi in "MGW" 020ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 017ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 58s 535ms

When Click button advice in transport table "TRANSPORT_ORDER" 240ms

And Set advice window in schedule 3s 376ms

And Fill advice form 18s 088ms

And Click advice save button and wait for advice form to disappear 33s 911ms

And Go to "TRANSPORT_TABLE" 485ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 094ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 087ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Check if not possible to advice transport in the past when advice is created from transports table and transport is created by sk API

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 706ms

And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 023ms

And Add transport by SKApi in "MGW" 019ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 018ms

And Check is transport "CONTAINER" created in transport table and set transport id 1m 1s 031ms

When Click button advice in transport table "CONTAINER" 241ms

And Set advice window in schedule in the past 3s 332ms

And Fill advice form 17s 872ms

And Click advice save button to check error message 162ms

Then Check if possible advice alert is displayed 073ms

Hooks

After Hooks.deleteTransportAfterTest() 667ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Check if advice data saved in SK API database after edition

The scenario checks if you can correctly edit an advice. After that the correctness of the data that has been sent to the SK API microservice database is also verified.

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 621ms

And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 024ms

And Add transport by SKApi in "MGW" 022ms

And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 017ms

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 34s 278ms

And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 55s 329ms

And Go to "TRANSPORT_TABLE" 456ms

When Go to transport details "OWN_COLLECTION" 2s 912ms

And Expand advice panel 305ms

And Edit advice in transport details 16s 670ms

And Fill arrival date field 2s 546ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 483ms

Then Check advice data in database after edition "OWN_COLLECTION" 102ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 036ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Check if advice data saved in SK API database after edition

The scenario checks if you can correctly edit an advice. After that the correctness of the data that has been sent to the SK API microservice database is also verified.

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 752ms

And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 020ms

And Add transport by SKApi in "MGW" 021ms

And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 016ms

And Check is transport "CONTAINER" created in transport table and set transport id 21s 981ms

And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 55s 415ms

And Go to "TRANSPORT_TABLE" 459ms

When Go to transport details "CONTAINER" 2s 924ms

And Expand advice panel 304ms

And Edit advice in transport details 16s 624ms

And Fill arrival date field 2s 546ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 451ms

Then Check advice data in database after edition "CONTAINER" 102ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 086ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Check if advice data saved in SK API database after edition

The scenario checks if you can correctly edit an advice. After that the correctness of the data that has been sent to the SK API microservice database is also verified.

Steps

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

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 020ms

And Add transport by SKApi in "MGW" 022ms

And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 016ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 18s 690ms

And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 55s 353ms

And Go to "TRANSPORT_TABLE" 505ms

When Go to transport details "TRANSPORT_ORDER" 2s 869ms

And Expand advice panel 316ms

And Edit advice in transport details 16s 701ms

And Fill arrival date field 2s 549ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 476ms

Then Check advice data in database after edition "TRANSPORT_ORDER" 090ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 048ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

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

And Create "CREATE_GRAY_WINDOW_TWG" window by JSON file for test as "super-admin-hochland" 214ms

And Create "CREATE_GRAY_WINDOW_OST" window by JSON file for test as "super-admin-hochland" 202ms

When Go to "WAREHOUSE_TAB" 1s 257ms

And Select warehouse "Twarożkarnia wyrób gotowy" 2s 117ms

And Select view "DAYS_2" 2s 163ms

Then Check if gray window is in the schedule 2s 049ms

And Select warehouse "Opakowania, surowce twarożkarnia" 1s 425ms

And Select view "DAYS_2" 2s 129ms

And Check if gray window is in the schedule 2s 039ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 584ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

Given Login as "hochland-producer" and set token of apiUsername "super-admin-hochland" 11s 040ms

And Create "CREATE_GRAY_WINDOW_TWG" window by JSON file for test as "super-admin-hochland" 222ms

And Create "CREATE_GRAY_WINDOW_OST" window by JSON file for test as "super-admin-hochland" 236ms

When Go to "WAREHOUSE_TAB" 1s 158ms

And Select warehouse "Twarożkarnia wyrób gotowy" 2s 153ms

And Select view "DAYS_2" 2s 189ms

Then Check if gray window is in the schedule 2s 039ms

And Select warehouse "Opakowania, surowce twarożkarnia" 1s 399ms

And Select view "DAYS_2" 2s 111ms

And Check if gray window is in the schedule 2s 043ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 684ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

Given Login as "pha1-carrier@qa.qa-test" and set token of apiUsername "super-admin-hochland" 9s 479ms

And Create "CREATE_GRAY_WINDOW_TWG" window by JSON file for test as "super-admin-hochland" 329ms

And Create "CREATE_GRAY_WINDOW_OST" window by JSON file for test as "super-admin-hochland" 318ms

When Go to "WAREHOUSE_TAB" 1s 305ms

And Select warehouse "Twarożkarnia wyrób gotowy" 2s 135ms

And Select view "DAYS_2" 2s 166ms

Then Check if gray window is in the schedule 2s 050ms

And Select warehouse "Opakowania, surowce twarożkarnia" 1s 438ms

And Select view "DAYS_2" 2s 140ms

And Check if gray window is in the schedule 2s 039ms

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 551ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 523ms

And Create "CREATE_GRAY_WINDOW_MGW" window by JSON file for test as "super-admin-skz" 203ms

And Create "CREATE_GRAY_WINDOW_HRL" window by JSON file for test as "super-admin-skz" 194ms

When Go to "WAREHOUSE_TAB" 858ms

And Select warehouse "MGW" 1s 380ms

And Select view "DAYS_2" 2s 166ms

Then Check if gray window is in the schedule 2s 051ms

And Select warehouse "HRL" 1s 539ms

And Select view "DAYS_2" 2s 138ms

And Check if gray window is in the schedule 2s 038ms

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 529ms

View Feature Schedule

@deleteTransportAfterTest @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if used pallet limit in schedule changing properly with given pallet settings [A-7575]

Steps

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

And Set "transport" inputs from JSON file "CREATE_DELIVERY_PALLETS_IN_WAREHOUSE_STEP_ONLY" "super-admin-neuca" 001ms

And Get package type settings for transportType "DELIVERY" from "neuca" 265ms

And Set package type "PALLETS" settings with values: "visibleInContractorStep;visibleInWarehouseStep", "true;false" 334ms

When Login as "neuca-admin" 8s 791ms

And Go to new transport "DELIVERY" 15s 519ms

And Fill transport form 37s 360ms

And Get sum of pallets of "load" in transport form 088ms

And Click "save-transport" save button and wait for form to disappear 15s 789ms

And Set advice window in schedule 2s 347ms

And Check is transport created in schedule and set transport id 3s 101ms

Then Verify if used pallet limit in schedule changed properly in "I" on "RT1" 188ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 094ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 127ms

View Feature Schedule

@deleteTransportAfterTest @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if used pallet limit in schedule changing properly with given pallet settings [A-7575]

Steps

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

And Set "transport" inputs from JSON file "CREATE_DELIVERY_PALLETS_IN_COMPANY_STEP_ONLY" "super-admin-neuca" 001ms

And Get package type settings for transportType "DELIVERY" from "neuca" 117ms

And Set package type "PALLETS" settings with values: "visibleInContractorStep;visibleInWarehouseStep", "false;true" 224ms

When Login as "neuca-admin" 2s 277ms

And Go to new transport "DELIVERY" 15s 495ms

And Fill transport form 37s 361ms

And Get sum of pallets of "unload" in transport form 073ms

And Click "save-transport" save button and wait for form to disappear 15s 737ms

And Set advice window in schedule 2s 360ms

And Check is transport created in schedule and set transport id 3s 384ms

Then Verify if used pallet limit in schedule changed properly in "I" on "RT1" 259ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 098ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 136ms

View Feature Schedule

@deleteTransportAfterTest @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if used pallet limit in schedule changing properly with given pallet settings [A-7575]

Steps

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

And Set "transport" inputs from JSON file "CREATE_DELIVERY_PALLETS_IN_WAREHOUSE_AND_COMPANY_STEPS" "super-admin-neuca" 002ms

And Get package type settings for transportType "DELIVERY" from "neuca" 123ms

And Set package type "PALLETS" settings with values: "visibleInContractorStep;visibleInWarehouseStep", "true;true" 220ms

When Login as "neuca-admin" 2s 489ms

And Go to new transport "DELIVERY" 15s 529ms

And Fill transport form 40s 384ms

And Get sum of pallets of "unload" in transport form 092ms

And Click "save-transport" save button and wait for form to disappear 15s 780ms

And Set advice window in schedule 2s 417ms

And Check is transport created in schedule and set transport id 3s 322ms

Then Verify if used pallet limit in schedule changed properly in "I" on "RT1" 250ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 041ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 153ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Steps

Given Set token of apiUsername "super-admin-hochland" 227ms

And Get custom field settings for "DELIVERY" transport type and "hochland" company 192ms

And Mark custom fields as not obligatory 006ms

And Login as "hochland-admin" 2s 745ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 209ms

When Find transport in table with status "advice-added" 3s 690ms

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

Then Check if transport has "process-ended" 077ms

Hooks

After Hooks.deleteTransportAfterTest() 968ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 986ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Steps

Given Set token of apiUsername "super-admin-pgf" 243ms

And Get custom field settings for "UNLOAD" transport type and "pgf" company 117ms

And Mark custom fields as not obligatory 006ms

And Login as "pgf-admin" 5s 028ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 17s 675ms

When Find transport in table with status "planned" 17s 610ms

And Confirm statuses until reach "process-ended" 12s 588ms

Then Check if transport has "process-ended" 070ms

Hooks

After Hooks.deleteTransportAfterTest() 885ms

After Hooks.rollbackAllCustomFieldsSettings() 384ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Steps

Given Set token of apiUsername "super-admin-adama" 238ms

And Get custom field settings for "DELIVERY" transport type and "adama" company 111ms

And Mark custom fields as not obligatory 005ms

And Login as "adama-admin" 5s 089ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 768ms

When Find transport in table with status "planned" 3s 694ms

And Confirm statuses until reach "process-ended" 11s 399ms

Then Check if transport has "process-ended" 069ms

Hooks

After Hooks.deleteTransportAfterTest() 764ms

After Hooks.rollbackAllCustomFieldsSettings() 397ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Steps

Given Set token of apiUsername "super-admin-lantmannen" 236ms

And Get custom field settings for "DELIVERY" transport type and "lantmannen" company 097ms

And Mark custom fields as not obligatory 005ms

And Login as "lantmannen-admin" 4s 594ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 993ms

When Find transport in table with status "potwierdzony" 3s 698ms

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

Then Check if transport has "process-ended" 075ms

Hooks

After Hooks.deleteTransportAfterTest() 907ms

After Hooks.rollbackAllCustomFieldsSettings() 004ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Steps

Given Set token of apiUsername "super-admin-lantmannen" 251ms

And Get custom field settings for "LOAD" transport type and "lantmannen" company 099ms

And Mark custom fields as not obligatory 004ms

And Login as "lantmannen-admin" 2s 175ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 3s 036ms

When Find transport in table with status "created" 3s 735ms

And Confirm statuses until reach "process-ended" 26s

Then Check if transport has "process-ended" 074ms

Hooks

After Hooks.deleteTransportAfterTest() 859ms

After Hooks.rollbackAllCustomFieldsSettings() 004ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Steps

Given Set token of apiUsername "super-admin-keeeper" 236ms

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 115ms

And Mark custom fields as not obligatory 006ms

And Login as "keeeper-admin" 5s 803ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 916ms

When Find transport in table with status "planned" 3s 652ms

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

Then Check if transport has "process-ended" 054ms

Hooks

After Hooks.deleteTransportAfterTest() 832ms

After Hooks.rollbackAllCustomFieldsSettings() 470ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Steps

Given Set token of apiUsername "super-admin-keeeper" 210ms

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 106ms

And Mark custom fields as not obligatory 006ms

And Login as "keeeper-admin" 5s 217ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 993ms

When Find transport in table with status "planned" 3s 687ms

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

Then Check if transport has "process-ended" 074ms

Hooks

After Hooks.deleteTransportAfterTest() 950ms

After Hooks.rollbackAllCustomFieldsSettings() 592ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if transport has ended status after adding advice by user

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 7s 454ms

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

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

When Accept or reject "accept" transferred transport 19s 554ms

And Get inputs from database "ADVICE_SMALLS" "super-admin-skz" 020ms

And Click button advice in transport table "SMALLS_IMPORT" 255ms

And Set advice window in schedule 3s 381ms

And Fill advice form 17s 991ms

And Click advice save button and wait for advice form to disappear 33s 800ms

And Check if window is "silver" 4s 071ms

And Go to "TRANSPORT_TABLE" 421ms

Then Check if transport has "process-ended" 684ms

Hooks

After Hooks.deleteTransportAfterTest() 992ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if transport has ended status after adding advice by user

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 708ms

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

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

When Accept or reject "accept" transferred transport 19s 732ms

And Get inputs from database "ADVICE_SMALLS" "super-admin-skz" 020ms

And Click button advice in transport table "SMALLS_EXPORT" 228ms

And Set advice window in schedule 3s 351ms

And Fill advice form 17s 935ms

And Click advice save button and wait for advice form to disappear 33s 845ms

And Check if window is "silver" 4s 081ms

And Go to "TRANSPORT_TABLE" 401ms

Then Check if transport has "process-ended" 845ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 051ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to edit advice after reach specific status

Steps

Given Set token of apiUsername "super-admin-hochland" 239ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_ADVICE" "CHECKPOINT_BASED" "ARRIVAL" 469ms

And Get custom field settings for "DELIVERY" transport type and "hochland" company 195ms

And Mark custom fields as not obligatory 017ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 258ms

When Login as "hochland-admin" 9s 999ms

And Find transport in table with status "advice-added" 3s 774ms

And Confirm statuses until reach "arrived" 6s 271ms

And Go to transport details "DELIVERY" 2s 901ms

Then Check if it is not possible to edit advice 1s 085ms

Hooks

After Hooks.deleteTransportAfterTest() 782ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 929ms

After Hooks.rollbackAddedActionAuthorities() 272ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check is transport color changed after confirm status

Steps

Given Set token of apiUsername "super-admin-hochland" 242ms

And Get custom field settings for "DELIVERY" transport type and "hochland" company 199ms

And Mark custom fields as not obligatory 009ms

And Login as "hochland-admin" 9s 526ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 132ms

When Find transport in table with status "advice-added" 3s 694ms

And Check if transport row is "blue" 3s 227ms

And Confirm statuses until reach "arrived" 6s 293ms

And Check if transport row is "green" 3s 211ms

And Confirm statuses until reach "during-unload" 6s 219ms

Then Check if transport row is "orange" 3s 218ms

And Confirm statuses until reach "unloaded" 6s 226ms

Then Check if transport row is "darkgoldenrod" 3s 224ms

And Confirm statuses until reach "process-ended" 6s 206ms

Then Check if transport row is "silver" 3s 178ms

Hooks

After Hooks.deleteTransportAfterTest() 796ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 804ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses before add file to transport

Steps

Given Set token of apiUsername "super-admin-piast" 229ms

And Get custom field settings for "DELIVERY" transport type and "piast" company 248ms

And Mark custom fields as not obligatory 007ms

And Login as "piast-admin" 5s 779ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 980ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 020ms

And Show all transport types 1s 152ms

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

And Set advice window in schedule 3s 580ms

And Fill advice form 10s 568ms

And Click advice save button and wait for advice form to disappear 33s 214ms

And Go to "TRANSPORT_TABLE" 413ms

And Find transport in table with status "advice-added" 3s 658ms

And Confirm statuses until reach "left-the-area" 32s 323ms

Then Check if next status is not possible to confirm 348ms

Hooks

After Hooks.deleteTransportAfterTest() 987ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 835ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses before add file to transport

Steps

Given Set token of apiUsername "super-admin-piast" 233ms

And Get custom field settings for "LOAD" transport type and "piast" company 263ms

And Mark custom fields as not obligatory 013ms

And Login as "piast-admin" 6s 062ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 2s 103ms

And Get inputs from database "ADVICE_LOAD" "super-admin-piast" 024ms

And Show all transport types 1s 148ms

And Click button advice in transport table "LOAD" 247ms

And Set advice window in schedule 3s 301ms

And Fill advice form 10s 387ms

And Click advice save button and wait for advice form to disappear 33s 373ms

And Go to "TRANSPORT_TABLE" 442ms

And Find transport in table with status "advice-added" 3s 670ms

And Confirm statuses until reach "left-the-area" 32s 285ms

Then Check if next status is not possible to confirm 303ms

Hooks

After Hooks.deleteTransportAfterTest() 956ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 412ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses after add file to transport

Steps

Given Set token of apiUsername "super-admin-piast" 245ms

And Get custom field settings for "DELIVERY" transport type and "piast" company 222ms

And Mark custom fields as not obligatory 006ms

And Login as "piast-admin" 5s 890ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 934ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 020ms

And Show all transport types 1s 156ms

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

And Set advice window in schedule 3s 305ms

And Fill advice form 10s 567ms

And Click advice save button and wait for advice form to disappear 33s 332ms

And Go to "TRANSPORT_TABLE" 454ms

And Find transport in table with status "advice-added" 3s 676ms

When Add file to transport by API 2s 805ms

And Confirm statuses until reach "process-ended" 37s 605ms

Then Check if transport has "process-ended" 080ms

Hooks

After Hooks.deleteTransportAfterTest() 885ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 792ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses after add file to transport

Steps

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

And Get custom field settings for "LOAD" transport type and "piast" company 260ms

And Mark custom fields as not obligatory 010ms

And Login as "piast-admin" 5s 990ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 948ms

And Get inputs from database "ADVICE_LOAD" "super-admin-piast" 022ms

And Show all transport types 1s 156ms

And Click button advice in transport table "LOAD" 238ms

And Set advice window in schedule 3s 327ms

And Fill advice form 10s 522ms

And Click advice save button and wait for advice form to disappear 33s 402ms

And Go to "TRANSPORT_TABLE" 446ms

And Find transport in table with status "advice-added" 3s 722ms

When Add file to transport by API 2s 134ms

And Confirm statuses until reach "process-ended" 33s 228ms

Error message

java.lang.AssertionError: Wartość advice-added-magazyn-hala-a atrybutu data-status-name nie zmieniła się w webelemencie [[ChromeDriver: chrome on LINUX (714ed1bdab8f41cbbbe0aae0f0ccfe67)] -> xpath: //td[contains(@data-status-name, 'advice-added')]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.StatusUtil.waitUntilAttributeOfWebElementChangeValue(StatusUtil.java:43)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:303)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:290)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:84)
	at ✽.Confirm statuses until reach "process-ended"(file:Features/Atom/Statuses/ConfirmStatuses.feature:117)

Then Check if transport has "process-ended" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 950ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 446ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - with advice step

Steps

Given Set token of apiUsername "super-admin-hochland" 229ms

And Get custom field settings for "TRANSFER_BETWEEN_WAREHOUSES" transport type and "hochland" company 231ms

And Mark custom fields as not obligatory 009ms

And Set custom field "Magazynier (R)" with "EDIT_TRANSFER_BETWEEN_WAREHOUSES_WAREHOUSEMAN_U_CFD" in "TRANSFER_BETWEEN_WAREHOUSES" - "hochland" by "super-admin-hochland" 468ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 901ms

And Set "advice" inputs from JSON file "ADVICE_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 002ms

And Login as "hochland-admin" 9s 779ms

And Show all transport types 1s 158ms

And Click button advice in transport table "TRANSFER_BETWEEN_WAREHOUSES" 1s 119ms

And Set advice window in schedule 7s 525ms

And Fill advice form 16s 534ms

And Click advice save button and wait for advice form to disappear 33s 820ms

And Go to "TRANSPORT_TABLE" 455ms

And Find transport in table with status "advice-added" 3s 651ms

And Confirm statuses until reach "during-load" 11s 483ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 606ms

And Check if next status is not possible to confirm in status confirmation modal 292ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 035ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 139ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - with advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 235ms

And Get custom field settings for "LOAD" transport type and "keeeper" company 126ms

And Mark custom fields as not obligatory 005ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_LOAD_SANITARY_CONDITIONS_CFD" in "LOAD" - "keeeper" by "super-admin-keeeper" 235ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 931ms

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper" 002ms

And Login as "keeeper-admin" 5s 948ms

And Show all transport types 1s 165ms

And Click button advice in transport table "LOAD" 263ms

And Set advice window in schedule 3s 200ms

And Fill advice form 16s 554ms

And Click advice save button and wait for advice form to disappear 33s 183ms

And Go to "TRANSPORT_TABLE" 466ms

And Find transport in table with status "advice-added" 3s 634ms

And Confirm statuses until reach "arrived" 6s 270ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 581ms

And Check if next status is not possible to confirm in status confirmation modal 257ms

Hooks

After Hooks.deleteTransportAfterTest() 839ms

After Hooks.rollbackAllCustomFieldsSettings() 751ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - with advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 229ms

And Get custom field settings for "CONTAINER" transport type and "keeeper" company 127ms

And Mark custom fields as not obligatory 005ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_CONTAINER_SANITARY_CONDITIONS_CFD" in "CONTAINER" - "keeeper" by "super-admin-keeeper" 226ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 901ms

And Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-keeeper" 001ms

And Login as "keeeper-admin" 5s 765ms

And Show all transport types 1s 175ms

And Click button advice in transport table "CONTAINER" 276ms

And Set advice window in schedule 3s 226ms

And Fill advice form 16s 297ms

And Click advice save button and wait for advice form to disappear 33s 313ms

And Go to "TRANSPORT_TABLE" 426ms

And Find transport in table with status "advice-added" 3s 683ms

And Confirm statuses until reach "arrived" 6s 294ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 583ms

And Check if next status is not possible to confirm in status confirmation modal 239ms

Hooks

After Hooks.deleteTransportAfterTest() 774ms

After Hooks.rollbackAllCustomFieldsSettings() 681ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - without advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 217ms

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 130ms

And Mark custom fields as not obligatory 005ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 239ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 747ms

And Login as "keeeper-admin" 5s 715ms

And Go to "TRANSPORT_TABLE" 427ms

And Find transport in table with status "planned" 3s 693ms

And Confirm statuses until reach "arrived" 6s 273ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 617ms

And Check if next status is not possible to confirm in status confirmation modal 274ms

Hooks

After Hooks.deleteTransportAfterTest() 953ms

After Hooks.rollbackAllCustomFieldsSettings() 473ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - without advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 234ms

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 118ms

And Mark custom fields as not obligatory 006ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_TANKER_GRANULATE_DELIVERY_SANITARY_CONDITIONS_CFD" in "TANKER_GRANULATE_DELIVERY" - "keeeper" by "super-admin-keeeper" 231ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 3s 009ms

And Login as "keeeper-admin" 5s 683ms

And Go to "TRANSPORT_TABLE" 431ms

And Find transport in table with status "planned" 3s 684ms

And Confirm statuses until reach "arrived" 6s 247ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 652ms

And Check if next status is not possible to confirm in status confirmation modal 241ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 044ms

After Hooks.rollbackAllCustomFieldsSettings() 623ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - without advice step

Steps

Given Set token of apiUsername "super-admin-hochland" 225ms

And Get custom field settings for "DELIVERY" transport type and "hochland" company 214ms

And Mark custom fields as not obligatory 007ms

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 1s 222ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 217ms

And Login as "hochland-admin" 9s 943ms

And Go to "TRANSPORT_TABLE" 435ms

And Find transport in table with status "advice-added" 3s 536ms

And Confirm statuses until reach "during-unload" 11s 503ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 654ms

And Check if next status is not possible to confirm in status confirmation modal 246ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 188ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 866ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Steps

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

And Get custom field settings for "LOAD" transport type and "keeeper" company 130ms

And Mark custom fields as not obligatory 005ms

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper" 002ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_LOAD_SANITARY_CONDITIONS_CFD" in "LOAD" - "keeeper" by "super-admin-keeeper" 211ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 908ms

And Login as "keeeper-admin" 5s 744ms

And Show all transport types 1s 265ms

And Click button advice in transport table "LOAD" 285ms

And Set advice window in schedule 3s 250ms

And Fill advice form 16s 502ms

And Click advice save button and wait for advice form to disappear 33s 324ms

And Go to "TRANSPORT_TABLE" 470ms

And Find transport in table with status "advice-added" 3s 686ms

When Confirm statuses until reach "arrived" 6s 276ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 533ms

And Check if next status is not possible to confirm in status confirmation modal 246ms

And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper" 001ms

And Click cancel in status confirmation modal 15s 316ms

And Go to transport details "LOAD" 2s 841ms

And Open section: "advice-panel" 1s 153ms

And Fill transport form 28s 644ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 530ms

And Go to transport details "LOAD" 2s 892ms

And Open section: "advice-panel" 1s 168ms

And Fill "meeting-sanitary-and-technical-conditions" in transport form 17s 382ms

And Confirm statuses until reach "process-ended" 16s 587ms

Then Check if transport has "process-ended" 077ms

Hooks

After Hooks.deleteTransportAfterTest() 966ms

After Hooks.rollbackAllCustomFieldsSettings() 699ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 230ms

And Get custom field settings for "CONTAINER" transport type and "keeeper" company 121ms

And Mark custom fields as not obligatory 005ms

And Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-keeeper" 001ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_CONTAINER_SANITARY_CONDITIONS_CFD" in "CONTAINER" - "keeeper" by "super-admin-keeeper" 225ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 909ms

And Login as "keeeper-admin" 6s 083ms

And Show all transport types 1s 170ms

And Click button advice in transport table "CONTAINER" 256ms

And Set advice window in schedule 3s 248ms

And Fill advice form 16s 397ms

And Click advice save button and wait for advice form to disappear 33s 313ms

And Go to "TRANSPORT_TABLE" 465ms

And Find transport in table with status "advice-added" 3s 702ms

When Confirm statuses until reach "arrived" 6s 293ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 501ms

And Check if next status is not possible to confirm in status confirmation modal 234ms

And Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-keeeper" 001ms

And Click cancel in status confirmation modal 15s 360ms

And Go to transport details "CONTAINER" 2s 852ms

And Open section: "advice-panel" 1s 170ms

And Fill transport form 28s 564ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 513ms

And Go to transport details "CONTAINER" 2s 846ms

And Open section: "advice-panel" 1s 174ms

And Fill "meeting-sanitary-and-technical-conditions" in transport form 17s 371ms

And Confirm statuses until reach "process-ended" 16s 507ms

Then Check if transport has "process-ended" 067ms

Hooks

After Hooks.deleteTransportAfterTest() 965ms

After Hooks.rollbackAllCustomFieldsSettings() 769ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Steps

Given Set token of apiUsername "super-admin-hochland" 233ms

And Get custom field settings for "TRANSFER_BETWEEN_WAREHOUSES" transport type and "hochland" company 207ms

And Mark custom fields as not obligatory 007ms

And Set "advice" inputs from JSON file "ADVICE_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 001ms

And Set custom field "Magazynier (R)" with "EDIT_TRANSFER_BETWEEN_WAREHOUSES_WAREHOUSEMAN_U_CFD" in "TRANSFER_BETWEEN_WAREHOUSES" - "hochland" by "super-admin-hochland" 459ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 898ms

And Login as "hochland-admin" 10s 201ms

And Show all transport types 1s 163ms

And Click button advice in transport table "TRANSFER_BETWEEN_WAREHOUSES" 1s 045ms

And Set advice window in schedule 7s 494ms

And Fill advice form 16s 547ms

And Click advice save button and wait for advice form to disappear 33s 858ms

And Go to "TRANSPORT_TABLE" 457ms

And Find transport in table with status "advice-added" 3s 654ms

When Confirm statuses until reach "during-load" 11s 599ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 577ms

And Check if next status is not possible to confirm in status confirmation modal 319ms

And Set "transport" inputs from JSON file "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 001ms

And Click cancel in status confirmation modal 15s 412ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 941ms

And Open section: "advice-panel" 1s 155ms

And Fill transport form 39s 881ms

And Click "save-transport-and-close" save button and wait for form to disappear 18s 093ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 769ms

And Open section: "advice-panel" 1s 286ms

And Fill "warehouseman-(u)" in transport form 17s 893ms

And Confirm statuses until reach "process-ended" 32s 321ms

Then Check if transport has "process-ended" 056ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 235ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 847ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 208ms

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 105ms

And Mark custom fields as not obligatory 005ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-keeeper" 001ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 217ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 949ms

And Login as "keeeper-admin" 6s 101ms

And Go to "TRANSPORT_TABLE" 430ms

And Find transport in table with status "planned" 3s 641ms

When Confirm statuses until reach "arrived" 6s 232ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 612ms

And Check if next status is not possible to confirm in status confirmation modal 263ms

And Click cancel in status confirmation modal 15s 385ms

And Go to transport details "UNLOAD" 2s 869ms

And Fill transport form 40s 893ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 505ms

And Confirm statuses until reach "process-ended" 16s 663ms

Then Check if transport has "process-ended" 053ms

Hooks

After Hooks.deleteTransportAfterTest() 786ms

After Hooks.rollbackAllCustomFieldsSettings() 485ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 229ms

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 109ms

And Mark custom fields as not obligatory 006ms

And Set "transport" inputs from JSON file "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 001ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_TANKER_GRANULATE_DELIVERY_SANITARY_CONDITIONS_CFD" in "TANKER_GRANULATE_DELIVERY" - "keeeper" by "super-admin-keeeper" 230ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 904ms

And Login as "keeeper-admin" 5s 627ms

And Go to "TRANSPORT_TABLE" 442ms

And Find transport in table with status "planned" 3s 696ms

When Confirm statuses until reach "arrived" 6s 255ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 641ms

And Check if next status is not possible to confirm in status confirmation modal 263ms

And Click cancel in status confirmation modal 15s 412ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 889ms

And Fill transport form 40s 702ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 476ms

And Confirm statuses until reach "process-ended" 16s 702ms

Then Check if transport has "process-ended" 070ms

Hooks

After Hooks.deleteTransportAfterTest() 877ms

After Hooks.rollbackAllCustomFieldsSettings() 629ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Steps

Given Set token of apiUsername "super-admin-hochland" 231ms

And Get custom field settings for "DELIVERY" transport type and "hochland" company 188ms

And Mark custom fields as not obligatory 006ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 703ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 144ms

And Login as "hochland-admin" 9s 592ms

And Go to "TRANSPORT_TABLE" 458ms

And Find transport in table with status "advice-added" 3s 692ms

When Confirm statuses until reach "during-unload" 11s 465ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 669ms

And Check if next status is not possible to confirm in status confirmation modal 225ms

And Click cancel in status confirmation modal 15s 555ms

And Go to transport details "DELIVERY" 2s 978ms

And Fill transport form 40s 534ms

And Click "save-transport-and-close" save button and wait for form to disappear 18s 083ms

And Confirm statuses until reach "process-ended" 11s 513ms

Then Check if transport has "process-ended" 077ms

Hooks

After Hooks.deleteTransportAfterTest() 967ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 905ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if it is possible to confirm status by guard without confirming earlier statuses

Steps

Given Set token of apiUsername "super-admin-skd" 231ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 2s 554ms

And Confirm status "REPORTING" by Public API "v1" 424ms

And Confirm status "ARRIVAL" by Public API "v1" 647ms

And Login as "swiss-krono-delivery-guard" 4s 805ms

And Go to "TRANSPORT_TABLE" 457ms

When Confirm "Departure" status in transport row 227ms

Then Verify that "Departure" has been confirmed 1s 333ms

Hooks

After Hooks.deleteTransportAfterTest() 892ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm next status in transport details on transport details reopen after filling blockade customfields and not saving changes - without advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 236ms

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 110ms

And Mark custom fields as not obligatory 005ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-keeeper" 001ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 253ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 16s 835ms

When Login as "keeeper-admin" 5s 882ms

And Find transport in table with status "planned" 3s 654ms

And Confirm statuses until reach "arrived" 6s 292ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 594ms

And Check if next status is not possible to confirm in status confirmation modal 273ms

And Click cancel in status confirmation modal 15s 368ms

And Go to transport details "UNLOAD" 2s 796ms

And Fill transport form 40s 951ms

Then Check if confirm status modal appeared on confirming next status in transport "details" 307ms

And Check if next status is not possible to confirm in status confirmation modal 238ms

Hooks

After Hooks.deleteTransportAfterTest() 935ms

After Hooks.rollbackAllCustomFieldsSettings() 511ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm next status in transport details on transport details reopen after filling blockade customfields and not saving changes - without advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 230ms

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 128ms

And Mark custom fields as not obligatory 005ms

And Set "transport" inputs from JSON file "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 001ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_TANKER_GRANULATE_DELIVERY_SANITARY_CONDITIONS_CFD" in "TANKER_GRANULATE_DELIVERY" - "keeeper" by "super-admin-keeeper" 244ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 3s 108ms

When Login as "keeeper-admin" 5s 754ms

And Find transport in table with status "planned" 3s 728ms

And Confirm statuses until reach "arrived" 6s 237ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 546ms

And Check if next status is not possible to confirm in status confirmation modal 257ms

And Click cancel in status confirmation modal 15s 323ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 907ms

And Fill transport form 40s 931ms

Then Check if confirm status modal appeared on confirming next status in transport "details" 268ms

And Check if next status is not possible to confirm in status confirmation modal 197ms

Hooks

After Hooks.deleteTransportAfterTest() 780ms

After Hooks.rollbackAllCustomFieldsSettings() 27s 242ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm next status in transport details on transport details reopen after filling blockade customfields and not saving changes - without advice step

Steps

Given Set token of apiUsername "super-admin-hochland" 243ms

And Get custom field settings for "DELIVERY" transport type and "hochland" company 178ms

And Mark custom fields as not obligatory 005ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 705ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 225ms

When Login as "hochland-admin" 10s 016ms

And Find transport in table with status "advice-added" 3s 787ms

And Confirm statuses until reach "during-unload" 11s 532ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 666ms

And Check if next status is not possible to confirm in status confirmation modal 409ms

And Click cancel in status confirmation modal 15s 549ms

And Go to transport details "DELIVERY" 2s 971ms

And Fill transport form 40s 736ms

Then Check if confirm status modal appeared on confirming next status in transport "details" 313ms

And Check if next status is not possible to confirm in status confirmation modal 264ms

Hooks

After Hooks.deleteTransportAfterTest() 847ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 879ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm status with given confirmation date [A-7159]

Steps

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

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 165ms

And Mark custom fields as not obligatory 007ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 776ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 263ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 727ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 415ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" 4s 798ms

And Login as "bausch-admin" 5s 870ms

And Go to "TRANSPORT_TABLE" 511ms

And Find transport in table with status "advice-added" 3s 697ms

And Confirm statuses until reach "on-the-way" 15s 641ms

When Open statuses popup 133ms

And Toggle status date confirmation checkbox 382ms

And Confirm statuses until reach "process-ended" 6s 151ms

Then Check if transport has "process-ended" 081ms

Hooks

After Hooks.deleteTransportAfterTest() 983ms

After Hooks.rollbackAllCustomFieldsSettings() 1s 866ms

After Hooks.deleteModeOfTransportationAfterTest() 334ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm status with invalid confirmation date [A-7159]

Steps

Given Set token of apiUsername "super-admin-bausch" 238ms

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 172ms

And Mark custom fields as not obligatory 006ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 714ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 219ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 742ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 362ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" 4s 434ms

And Login as "bausch-admin" 5s 878ms

And Go to "TRANSPORT_TABLE" 513ms

And Find transport in table with status "advice-added" 3s 691ms

And Confirm statuses until reach "on-the-way" 16s 754ms

And Open statuses popup 147ms

And Toggle status date confirmation checkbox 392ms

And Change status execution date to "1" days from today 2s 463ms

Then Verify that status cannot be confirmed 1s 216ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 023ms

After Hooks.rollbackAllCustomFieldsSettings() 1s 873ms

After Hooks.deleteModeOfTransportationAfterTest() 340ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm status with invalid confirmation date [A-7159]

Steps

Given Set token of apiUsername "super-admin-bausch" 232ms

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 164ms

And Mark custom fields as not obligatory 006ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 688ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 194ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 751ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 391ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" 4s 670ms

And Login as "bausch-admin" 5s 973ms

And Go to "TRANSPORT_TABLE" 511ms

And Find transport in table with status "advice-added" 3s 700ms

And Confirm statuses until reach "on-the-way" 16s 692ms

And Open statuses popup 158ms

And Toggle status date confirmation checkbox 403ms

And Change status execution date to "-1" days from today 2s 505ms

Then Verify that status cannot be confirmed 1s 212ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 068ms

After Hooks.rollbackAllCustomFieldsSettings() 1s 870ms

After Hooks.deleteModeOfTransportationAfterTest() 328ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackTaskChanges @rollbackAllCustomFieldsSettings

Scenario Outline Confirmed statuses of existing orders should not be deleted - even after editing the order [A-6874]

Steps

Given Set token of apiUsername "super-admin-farmacol" 328ms

And Get custom field settings for "EXTERNAL_DELIVERY" transport type and "farmacol" company 090ms

And Mark custom fields as not obligatory 004ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 891ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 3s 659ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 120ms

When Login as "farmacol-admin" 7s 501ms

And Go to "TRANSPORT_TABLE" 497ms

And Confirm statuses until reach "during-unload" 16s 894ms

And Set actual confirmed transport status list 2s 003ms

And Disable task by API 297ms

And Go to transport details "EXTERNAL_DELIVERY" 2s 946ms

And Edit transport hours and recalculate statuses 19s 087ms

Then Verify that all confirmed statuses are still on transport status list 455ms

Hooks

After Hooks.deleteTransportAfterTest() 866ms

After Hooks.rollbackAllCustomFieldsSettings() 316ms

After Hooks.rollbackTaskChanges() 181ms

View Feature Status rejection

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it is possible to reject status by guard in transport table

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 4s 583ms

And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 273ms

And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 4s 652ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 974ms

And Check if reject date is not visible 15s 052ms

When Reject status: Book of disinfection 15s 059ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//button[@data-button-name='reject-checkpoint']"}
  (Session info: headless chrome=91.0.4472.114)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=91.0.4472.101 (af52a90bf87030dd1523486a1cd3ae25c5d76c9b-refs/branch-heads/4472@{#1462}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.F2003R}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=91.0.4472.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 714ed1bdab8f41cbbbe0aae0f0ccfe67
*** Element info: {Using=xpath, value=//button[@data-button-name='reject-checkpoint']}
	at sun.reflect.GeneratedConstructorAccessor214.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at CucumberTests.StatusTests.RejectStatuses.rejectStatusBookOfDisinfection(RejectStatuses.java:41)
	at ✽.Reject status: Book of disinfection(file:Features/Atom/Statuses/RejectStatuses.feature:10)

And Check if reject date is visible 000ms

Then If user is login then logout 000ms

And Login as "lantmannen-admin" 000ms

And Check if note was added to transport after status rejection 000ms

And Check if history note was added to transport after status rejection - "LOAD" 000ms

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nieaktualna księga mycia i dezynfekcji" 000ms

And Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 839ms

After Hooks.cleanUserDetailsAfterTest() 964ms

View Feature Status rejection

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject status twice and reject date is changing

Steps

Given Login as "lantmannen-guard-3" and set token of apiUsername "super-admin-lantmannen" 5s 044ms

And Create transport "CREATE_LOAD_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 2s 950ms

And Check if reject date is not visible 15s 076ms

When Reject status: Book of disinfection 190ms

And Check if reject date is visible 664ms

And Get rejection date 095ms

And Wait "60" seconds 1m

And Reject status: Book of disinfection 180ms

Then Check if reject date has changed 1s 222ms

Hooks

After Hooks.deleteTransportAfterTest() 853ms

View Feature Status rejection

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject status by admin in transport form

Steps

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 911ms

And Go to transport details "LOAD" 2s 754ms

And Check if reject date is not visible 15s 049ms

When Reject status: Book of disinfection 188ms

Then Check if reject date is visible 575ms

Hooks

After Hooks.deleteTransportAfterTest() 908ms

View Feature Status rejection

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject status by admin in statuses popup

Steps

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 915ms

And Open statuses popup 203ms

And Check if reject date is not visible 15s 069ms

When Reject status: Book of disinfection 211ms

Then Open statuses popup 161ms

And Check if reject date is visible 438ms

Hooks

After Hooks.deleteTransportAfterTest() 985ms

View Feature Status revocation

@deleteTransportAfterTest

Scenario Outline Check if it is possible to revoke statuses by user

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 094ms

And Confirm to the last status by API 1s 292ms

When Find statuses for transport in table 3s 249ms

And Revoke statuses until reach "advice-added" 7s 994ms

Then Check if transport has "advice-added" 064ms

Hooks

After Hooks.deleteTransportAfterTest() 817ms

View Feature Status revocation

@deleteTransportAfterTest

Scenario Outline Check if it is possible to revoke statuses by user

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 5s 778ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 3s 061ms

And Confirm to the last status by API 1s 369ms

When Find statuses for transport in table 2s 608ms

And Revoke statuses until reach "planned" 8s 073ms

Then Check if transport has "planned" 055ms

Hooks

After Hooks.deleteTransportAfterTest() 962ms

View Feature Status

@deleteTransportAfterTest

Scenario Outline Check if after created transport without advice, transport has checkpoints only from "preparation" section

Steps

Given Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 6s 978ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 994ms

When Find transport in table with status "new" 3s 680ms

And Open statuses popup 150ms

Then Check if transport has checkpoints from list "Utworzenie zlecenia,Dodanie awizacji,Potwierdzenie okna czasowego" in "0" 151ms

Hooks

After Hooks.deleteTransportAfterTest() 579ms

View Feature Status

@deleteTransportAfterTest

Scenario Outline Check if after added advice, checkpoints are generated from "steps" section

Steps

Given Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 2s 194ms

And Get inputs from database "ADVICE_EXTERNAL_DELIVERY" "super-admin-farmacol" 018ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 993ms

And Click button advice in transport table "EXTERNAL_DELIVERY" 204ms

And Set advice window in schedule 3s 493ms

And Fill advice form 14s 831ms

And Click advice save button and wait for advice form to disappear 33s 855ms

And Go to "TRANSPORT_TABLE" 504ms

When Find transport in table with status "advice-added" 3s 629ms

And Open statuses popup 151ms

Then Check if transport has checkpoints from list "Zgłoszenie kierowcy,Rozpoczęcie rozładunku,Zakończenie rozładunku" in "1" 147ms

Hooks

After Hooks.deleteTransportAfterTest() 808ms

View Feature Status

@deleteTransportAfterTest @rollbackTaskChanges @rollbackAllCustomFieldsSettings

Scenario Outline Check if deleted task is not in new transports' workflow @A-6875

Steps

Given Set token of apiUsername "super-admin-farmacol" 221ms

And Get custom field settings for "EXTERNAL_DELIVERY" transport type and "farmacol" company 111ms

And Mark custom fields as not obligatory 004ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 923ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 3s 683ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 122ms

When Login as "farmacol-admin" 2s 412ms

And Go to "TRANSPORT_TABLE" 477ms

And Confirm statuses until reach "registered-katowice-przyjęcia" 11s 572ms

And Disable task by API 200ms

And Find transport pencil button in transports table 1s 821ms

And Click pencil and move transport to next day in schedule 22s 860ms

And Go to "TRANSPORT_TABLE" 495ms

Then Verify that "START_OF_UNLOADING" is not visible 383ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 024ms

After Hooks.rollbackAllCustomFieldsSettings() 346ms

After Hooks.rollbackTaskChanges() 184ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 225ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 239ms

When Go to "WAREHOUSE_TAB" 1s 180ms

And Select warehouse "Serownia" 1s 648ms

And Set week view 1s 245ms

And Show yesterday 1s 153ms

And Move window into the past 423ms

Then Check if window is "red" 4s 064ms

Hooks

After Hooks.deleteTransportAfterTest() 900ms

After Hooks.rollbackAddedAuthorities() 158ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past

Steps

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 973ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "lantmannen-admin" 192ms

When Go to "WAREHOUSE_TAB" 1s 291ms

And Select warehouse "Magazyn - Nowa Sól" 2s 653ms

And Set week view 1s 300ms

And Show yesterday 1s 181ms

And Move window into the past 699ms

Then Check if window is "red" 4s 074ms

Hooks

After Hooks.deleteTransportAfterTest() 906ms

After Hooks.rollbackAddedAuthorities() 128ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past after add advice by advice button in transport table

Steps

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 012ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "piast-admin" 201ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 021ms

When Show all transport types 1s 154ms

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

And Set advice window in schedule 3s 377ms

And Fill advice form 10s 489ms

And Click advice save button and wait for advice form to disappear 33s 341ms

And Select warehouse "Magazyn Hala A" 1s 384ms

And Set week view 2s 274ms

And Show yesterday 1s 257ms

And Move window into the past 850ms

Then Check if window is "red" 4s 083ms

Error message

java.lang.AssertionError
	at org.junit.Assert.fail(Assert.java:86)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.junit.Assert.assertTrue(Assert.java:52)
	at CucumberTests.Schedule.ScheduleTest.checkIfWindowIs(ScheduleTest.java:57)
	at ✽.Check if window is "red"(file:Features/Atom/TimeWindow/TransportWindow.feature:35)

Hooks

After Hooks.deleteTransportAfterTest() 941ms

After Hooks.rollbackAddedAuthorities() 136ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if time window resize with restriction to algorithm settings

Steps

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

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 020ms

And Set algorithm setting for "super-admin-hochland" in "Magazyn Zimny Kaźmierz" on "Magazyn Zimny" 1s 188ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 3s 204ms

When Go to "WAREHOUSE_TAB" 1s 207ms

And Select warehouse "Magazyn Zimny Kaźmierz" 2s 021ms

And Set week view 1s 284ms

And Check if time window length is correct after "CREATE" 083ms

And Change number of pallets in transport 58s 813ms

And Click "save-transport-and-close" save button and wait for form to disappear 5s 055ms

And Check if time window length is correct after "EDIT" 076ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 105ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if time window has valid length with restriction to algorithm settings when quantity is set in transport form

Steps

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

And Get package type settings for transportType "UNLOAD" from "keeeper" 125ms

And Set package type "PALLETS" settings with values: "defaultValue;required", "4;true" 234ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 675ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 3s 001ms

When Go to "WAREHOUSE_TAB" 737ms

And Select warehouse "Magazyn Surowców" 1s 368ms

And Set week view 1s 184ms

Then Check if time window has proper "60" 051ms

Hooks

After Hooks.deleteTransportAfterTest() 992ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 132ms

After Hooks.clearAlgorithmSettings() 578ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if time window has valid length with restriction to algorithm settings when quantity is set from default quantity value and quantity field is not visible in transport form

Steps

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

And Get package type settings for transportType "UNLOAD" from "keeeper" 108ms

And Set package type "PALLETS" settings with values: "defaultValue;required", "4;false" 196ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 572ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 855ms

When Go to "WAREHOUSE_TAB" 705ms

And Select warehouse "Magazyn Surowców" 1s 338ms

And Set week view 1s 245ms

Then Check if time window has proper "60" 067ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 023ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 134ms

After Hooks.clearAlgorithmSettings() 556ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if time window has valid length after advice is added with restriction to algorithm settings when quantity is set from default quantity value and quantity field is not visible in transport form

Steps

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

And Get package type settings for transportType "LOAD" from "keeeper" 132ms

And Set package type "PALLETS" settings with values: "defaultValue;required", "4;false" 223ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 629ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 932ms

And Get inputs from database "ADVICE_LOAD" "super-admin-keeeper" 018ms

And Show all transport types 1s 171ms

And Click button advice in transport table "LOAD" 253ms

And Set advice window in schedule 3s 265ms

And Fill advice form 16s 363ms

And Click advice save button and wait for advice form to disappear 33s 296ms

Then Check if time window has proper "30" 084ms

Hooks

After Hooks.deleteTransportAfterTest() 916ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 148ms

After Hooks.clearAlgorithmSettings() 540ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if time window has valid length after advice is added with restriction to algorithm settings when quantity is set from default quantity value and quantity field is not visible in transport form

Steps

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

And Get package type settings for transportType "CONTAINER" from "keeeper" 126ms

And Set package type "PALLETS" settings with values: "defaultValue;required", "20;false" 222ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 606ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 904ms

And Get inputs from database "ADVICE_CONTAINER" "super-admin-keeeper" 022ms

And Show all transport types 1s 154ms

And Click button advice in transport table "CONTAINER" 251ms

And Set advice window in schedule 3s 244ms

And Fill advice form 16s 339ms

And Click advice save button and wait for advice form to disappear 33s 304ms

Then Check if time window has proper "60" 079ms

Hooks

After Hooks.deleteTransportAfterTest() 897ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 128ms

After Hooks.clearAlgorithmSettings() 553ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings

Scenario Outline Check if supplier can change time window size by change number of pallets

Steps

Given Set token of apiUsername "super-admin-hochland" 235ms

And Set algorithm setting for "super-admin-hochland" in "Serownia" on "Magazyn Sera" 857ms

And Set token of apiUsername "dha1-supplier-2@qa.qa-test" 212ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 16s 934ms

And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "super-admin-hochland" 7s 669ms

When Go to transport details "DELIVERY" 30s 755ms

And Change filled value in transport details "number-of-pallets-step-0" "number" "25" "0" 1s 545ms

And Click "save-transport-and-close" save button and wait for form to disappear 19s 206ms

And Go to "WAREHOUSE_TAB" 1s 184ms

And Select warehouse "Serownia" 1s 622ms

And Set week view 1s 259ms

Then Check if time window has proper "60" 087ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 024ms

After Hooks.clearAlgorithmSettings() 987ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if window counter value in schedule changes

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 3s 041ms

And Set basic authorities "ROLE_ACCESS_TO_NUMBER_OF_WINDOWS" to user "keeeper-admin" 131ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 906ms

When Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 52s 877ms

And Check if time window counter value equals "1" 229ms

And Select view "DAYS_2" 2s 189ms

And Move advice window "2" 1s 511ms

And Select view "DAY" 2s 151ms

Then Check if time window counter value equals "0" 195ms

And Delete created transport by API 960ms

And Check if time window counter value equals "0" 161ms

And Click in free spot in schedule page to create gray window 463ms

And Check if time window counter value equals "0" 262ms

And Click in free spot in schedule page to create dedicated window 2s 155ms

And Check if time window counter value equals "0" 180ms

Hooks

After Hooks.deleteTransportAfterTest() 821ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-adama" 018ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 328ms

When Go to new transport "DELIVERY" 721ms

And Fill transport form 13s 091ms

And Click "save-transport" save button and wait for form to disappear 15s 726ms

And Set advice window in schedule 2s 403ms

And Check is transport created in schedule and set transport id 2s 520ms

And Go to "TRANSPORT_TABLE" 519ms

When Click on time window date 1s 673ms

And Open transport form when in schedule 1s 307ms

Then Check are transport values equals 390ms

Hooks

After Hooks.deleteTransportAfterTest() 815ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-hochland" 020ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 999ms

When Go to new transport "DELIVERY" 675ms

And Fill transport form 43s 922ms

And Click "save-transport" save button and wait for form to disappear 15s 769ms

And Set advice window in schedule 2s 368ms

And Check is transport created in schedule and set transport id 2s 979ms

And Go to "TRANSPORT_TABLE" 530ms

When Click on time window date 1s 648ms

And Open transport form when in schedule 1s 401ms

Then Check are transport values equals 20s 036ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 047ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_CISTERN_DELIVERY" "super-admin-hochland" 018ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 026ms

When Go to new transport "CISTERN_DELIVERY" 742ms

And Fill transport form 46s 362ms

And Click "save-transport" save button and wait for form to disappear 15s 754ms

And Set advice window in schedule 2s 426ms

And Check is transport created in schedule and set transport id 2s 551ms

And Go to "TRANSPORT_TABLE" 512ms

When Click on time window date 2s 918ms

And Open transport form when in schedule 1s 376ms

Then Check are transport values equals 7s 260ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 121ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_CISTERN_COLLECTION" "super-admin-hochland" 020ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 082ms

When Go to new transport "CISTERN_COLLECTION" 625ms

And Fill transport form 32s 057ms

And Click "save-transport" save button and wait for form to disappear 15s 725ms

And Set advice window in schedule 2s 437ms

And Check is transport created in schedule and set transport id 2s 463ms

And Go to "TRANSPORT_TABLE" 473ms

When Click on time window date 3s 055ms

And Open transport form when in schedule 1s 363ms

Then Check are transport values equals 22s 023ms

Hooks

After Hooks.deleteTransportAfterTest() 923ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-lantmannen" 019ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 4s 925ms

When Go to new transport "DELIVERY" 611ms

And Fill transport form 42s 825ms

And Click "save-transport" save button and wait for form to disappear 15s 743ms

And Set advice window in schedule 2s 318ms

And Check is transport created in schedule and set transport id 2s 476ms

And Go to "TRANSPORT_TABLE" 407ms

When Click on time window date 1s 675ms

And Open transport form when in schedule 1s 289ms

Then Check are transport values equals 20s 015ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 192ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-lantmannen" 020ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 717ms

When Go to new transport "LOAD" 669ms

And Fill transport form 42s 585ms

And Click "save-transport" save button and wait for form to disappear 15s 764ms

And Set advice window in schedule 2s 379ms

And Check is transport created in schedule and set transport id 2s 709ms

And Go to "TRANSPORT_TABLE" 501ms

When Click on time window date 1s 752ms

And Open transport form when in schedule 1s 301ms

Then Check are transport values equals 19s 898ms

Hooks

After Hooks.deleteTransportAfterTest() 906ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackTransportTypeSettings

Scenario Outline Check if it is possible to add new warehouse step with new time window to existing transport

Steps

Given Set token of apiUsername "super-admin-farmacol" 242ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 334ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 298ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 265ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 808ms

And Login as "farmacol-admin" 6s 797ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 52s 971ms

And Go to "TRANSPORT_TABLE" 544ms

When Go to transport details "EXTERNAL_DELIVERY" 2s 883ms

And Add step "unload" 209ms

And Change filled value in transport details "warehouse-select-step-2" "select" "Mory Przyjęcia" "0" 3s 828ms

And Change filled value in transport details "weight-step-2" "number" "23" "0" 1s 580ms

And Change filled value in transport details "number-of-pallets-step-2" "number" "23" "0" 1s 561ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 835ms

Then Click "save-transport" save button 326ms

And Set advice window in schedule in "2" days 5s 592ms

And Click advice save button and wait for advice form to disappear 35s 532ms

And Go to "TRANSPORT_TABLE" 434ms

And Check if transport has "2" time windows 037ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 212ms

After Hooks.rollbackTransportTypeSettings() 320ms

After Hooks.rollbackAddedActionAuthorities() 289ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest

Scenario Outline Check if window changes color properly in transport table

Steps

Given Set token of apiUsername "super-admin-farmacol" 225ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 169ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 254ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 2s 036ms

And Set double window advice 000ms

And Login as "farmacol-admin" 6s 749ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 58s

And Go to "TRANSPORT_TABLE" 544ms

And Get checkpoint colors for transport 034ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "true" 38s 778ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 171ms

After Hooks.rollbackTransportTypeSettings() 253ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest

Scenario Outline Check if window changes color properly in transport table

Steps

Given Set token of apiUsername "super-admin-farmacol" 220ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 138ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 263ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 2s 010ms

And Set double window advice 000ms

And Login as "farmacol-admin" 2s 652ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 58s 011ms

And Go to "TRANSPORT_TABLE" 551ms

And Get checkpoint colors for transport 019ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "false" 39s 319ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 163ms

After Hooks.rollbackTransportTypeSettings() 461ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest

Scenario Outline Check if window changes color properly in schedule

Steps

Given Set token of apiUsername "super-admin-farmacol" 221ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 154ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 258ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 2s 081ms

And Set double window advice 000ms

And Login as "farmacol-admin" 2s 534ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 57s 653ms

And Get checkpoint colors for transport 024ms

And Go to "TRANSPORT_TABLE" 577ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true" 9s 507ms

Error message

java.lang.AssertionError
	at org.junit.Assert.fail(Assert.java:86)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.junit.Assert.assertTrue(Assert.java:52)
	at CucumberTests.TimeWindow.TimeWindowTest.verifyThatTransportColorsOfWindowsChangeProperlyInScheduleWhenWindowColorDependsOnWarehouseIs(TimeWindowTest.java:118)
	at ✽.Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true"(file:Features/Atom/TimeWindow/TransportWindow.feature:247)

Hooks

After Hooks.deleteTransportAfterTest() 1s 116ms

After Hooks.rollbackTransportTypeSettings() 265ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest

Scenario Outline Check if window changes color properly in schedule

Steps

Given Set token of apiUsername "super-admin-farmacol" 230ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 132ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 252ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 15s 880ms

And Set double window advice 000ms

And Login as "farmacol-admin" 2s 706ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 57s 808ms

And Get checkpoint colors for transport 018ms

And Go to "TRANSPORT_TABLE" 573ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "false" 30s 054ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 220ms

After Hooks.rollbackTransportTypeSettings() 333ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if window is active after using "create similar" on that window [A-7009]

Steps

Given Set token of apiUsername "super-admin-farmacol" 220ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 998ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 3s 864ms

And Login as "super-admin-farmacol" 8s 005ms

And Show all transport types 1s 159ms

And Click on time window date 2s 027ms

Then Open transport form when in schedule 1s 418ms

And Click create similar button 15s 263ms

And Click cancel button in transport form 211ms

And Open transport form when in schedule 1s 356ms

Then Check if transport form modal is visible 095ms

Hooks

After Hooks.deleteTransportAfterTest() 853ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if min and max advice date changed after moving advice window [A-7503]

Steps

Given Set token of apiUsername "super-admin-farmacol" 235ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 923ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 3s 933ms

And Get min and max advice date of created transport as "super-admin-farmacol" 462ms

And Login as "farmacol-admin" 2s 573ms

And Show all transport types 1s 166ms

And Click on time window date 2s 039ms

And Set week view 2s 598ms

And Move advice window "3" 1s 820ms

Then Check if min and max advice date changed after moving advice window as "super-admin-farmacol" 627ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 334ms

View Feature Move transport to archive

@rollbackSettings @deleteTransportAfterTest

Scenario Outline Check if delayed transport is moved to archived and can be restored

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 8s 034ms

And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 017ms

And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 144ms

And Set proper delay time to move order to archive after task timeout 127ms

When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 958ms

And Go to "WAREHOUSE_TAB" 1s 048ms

And Change warehouse in schedule to: "Katowice" 1s 560ms

And Wait "60" seconds 1m

And Verify that transport window is grey 084ms

And Verify that transport is in archive 10s 799ms

Then Restore transport from archive 2s 607ms

And Verify that transport has been successfully restored 15s 685ms

Hooks

After Hooks.deleteTransportAfterTest() 1s

After Hooks.rollbackSettings() 120ms

View Feature Move transport to archive

@deleteTransportAfterTest

Scenario Outline Check if removing a transport from the table moves it to the archive

Steps

Given Login as "dayco-admin" and set token of apiUsername "super-admin-dayco" 6s 931ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 233ms

When Go to "TRANSPORT_TABLE" 417ms

And Delete transport 19s 526ms

When Go to "ARCHIVE_TAB" 559ms

And Show "OWN_COLLECTION" 197ms

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

Hooks

After Hooks.deleteTransportAfterTest() 841ms

View Feature Move transport to archive

@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings @FLAKY

Scenario Outline Check if confirming transport status removed it to the archive

Steps

Given Set token of apiUsername "super-admin-dayco" 243ms

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 117ms

And Mark custom fields as not obligatory 007ms

And Login as "dayco-admin" 2s 101ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 112ms

And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 141ms

And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 030ms

When Go to "TRANSPORT_TABLE" 392ms

And Click button advice in transport table "OWN_COLLECTION" 1s 420ms

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 45s 835ms

And Go to "TRANSPORT_TABLE" 462ms

And Find transport in table with status "planned-magazyn-tychy" 3s 727ms

And Confirm statuses until reach "process-ended" 16s 649ms

And Wait "12" seconds 12s

Then Go to "ARCHIVE_TAB" 525ms

And Show "OWN_COLLECTION" 163ms

And Verify that created transport is "true" in transport table 1m 32s 358ms

Error message

java.lang.AssertionError: expected: but was:
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:834)
	at org.junit.Assert.assertEquals(Assert.java:118)
	at org.junit.Assert.assertEquals(Assert.java:144)
	at CucumberTests._PerformanceTests.TransportTableTest.verifyThatCreatedTransportIsInTransportTable(TransportTableTest.java:120)
	at ✽.Verify that created transport is "true" in transport table(file:Features/Atom/Transport/Archive.feature:54)

Hooks

After Hooks.deleteTransportAfterTest() 992ms

After Hooks.rollbackAllCustomFieldsSettings() 464ms

After Hooks.rollbackSettings() 140ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to create new auction in transport

Steps

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 097ms

When Fill auction form 16s 117ms

Then Verify that the auction has been added to transport 166ms

Hooks

After Hooks.deleteTransportAfterTest() 799ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to create new auction in transport

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 916ms

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

When Fill auction form 16s 127ms

Then Verify that the auction has been added to transport 164ms

Hooks

After Hooks.deleteTransportAfterTest() 696ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept auction offer with minimum rate

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 565ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 177ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 831ms

When If user is login then logout 276ms

And Login as "paa1-carrier@qa.qa-test" 5s 037ms

And Go to auction offer 1s 646ms

And Accept transport with minimum rate 16s 978ms

Then Check if carrier is assigned to transport 071ms

Hooks

After Hooks.deleteTransportAfterTest() 664ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject auction offer

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 519ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 102ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 794ms

When If user is login then logout 236ms

And Login as "paa1-carrier@qa.qa-test" 2s 539ms

And Go to auction offer 1s 609ms

And Reject auction offer 15s 782ms

Then Verify that offer has been removed from transport 15s 125ms

Hooks

After Hooks.deleteTransportAfterTest() 852ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject auction offer

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 692ms

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 774ms

When If user is login then logout 453ms

And Login as "pskza1-carrier@qa.qa-test" 6s 310ms

And Go to auction offer 2s 358ms

And Reject auction offer 15s 820ms

Then Verify that offer has been removed from transport 15s 083ms

Hooks

After Hooks.deleteTransportAfterTest() 764ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add offer above maximum rate

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 527ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 144ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 873ms

When If user is login then logout 281ms

And Login as "paa1-carrier@qa.qa-test" 2s 343ms

And Go to auction offer 1s 590ms

And Offer prize above maximum - "20000" 386ms

Then Verify that is not possible to add offer 852ms

Hooks

After Hooks.deleteTransportAfterTest() 711ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add offer above maximum rate

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 521ms

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 729ms

When If user is login then logout 240ms

And Login as "pskza1-carrier@qa.qa-test" 2s 216ms

And Go to auction offer 2s 423ms

And Offer prize above maximum - "20000" 387ms

Then Verify that is not possible to add offer 1s 012ms

Hooks

After Hooks.deleteTransportAfterTest() 744ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add auction again after previous auction end

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 372ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 099ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 811ms

And Wait till auction end 1m 58s 016ms

Then Verify that is possible to add auction 154ms

Hooks

After Hooks.deleteTransportAfterTest() 809ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add auction again after previous auction end

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 624ms

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 819ms

And Wait till auction end 1m 58s 015ms

Then Verify that is possible to add auction 157ms

Hooks

After Hooks.deleteTransportAfterTest() 806ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add valid offer

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 721ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 317ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 898ms

And Go to auction offer 1s 535ms

When Offer "1000" 359ms

Then Verify that offer with "1000" has been added to auction 3s 086ms

Hooks

After Hooks.deleteTransportAfterTest() 761ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add valid offer

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 515ms

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 823ms

And Go to auction offer 1s 537ms

When Offer "1000" 354ms

Then Verify that offer with "1000" has been added to auction 3s 085ms

Hooks

After Hooks.deleteTransportAfterTest() 712ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to revoke an offer

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 484ms

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 824ms

And Go to auction offer 1s 475ms

When Offer "1000" 305ms

And Verify that offer with "1000" has been added to auction 3s 061ms

Then Go to auction offer 1s 461ms

And Revoke current offer 710ms

And Verify that offer has been revoked 33s 040ms

Hooks

After Hooks.deleteTransportAfterTest() 723ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to offer more than last price

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 711ms

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 800ms

And Go to auction offer 1s 564ms

When Offer "1000" 366ms

And Verify that offer with "1000" has been added to auction 3s 087ms

Then Go to auction offer 1s 505ms

And Offer "1500" 351ms

And Verify that offer with "1500" has been added to auction 3s 078ms

Hooks

After Hooks.deleteTransportAfterTest() 770ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to finish active auction

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 409ms

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 802ms

And Go to auction offer 1s 531ms

When Offer "1000" 362ms

And Verify that offer with "1000" has been added to auction 3s 084ms

Then Login as "swisskrono-admin" 2s 301ms

And Go to auction details 2s 162ms

And Finish active auction 146ms

And Verify that the transport has no active auction 721ms

Hooks

After Hooks.deleteTransportAfterTest() 698ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if carrier can see current place in auction depending on the "canSeeCurrentPlaceInAuction" role

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 430ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 228ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 811ms

And Go to auction offer 1s 555ms

When Offer "1000" 371ms

Then Verify that carrier can see current place in auction depending on the "true" role 846ms

Hooks

After Hooks.deleteTransportAfterTest() 752ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if carrier can see current place in auction depending on the "canSeeCurrentPlaceInAuction" role

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 516ms

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 816ms

And Go to auction offer 1s 551ms

When Offer "1000" 371ms

Then Verify that carrier can see current place in auction depending on the "false" role 15s 065ms

Hooks

After Hooks.deleteTransportAfterTest() 872ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to add offer below min price

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 780ms

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 773ms

And Go to auction offer 1s 500ms

When Offer "300" 304ms

And Verify that carrier can't add offer to auction 073ms

Hooks

After Hooks.deleteTransportAfterTest() 686ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check carrier selection in create auction form

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 171ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 102ms

And Show all transport "false" 077ms

When Go to auction form 1s 633ms

Then Verify carrier selection value "false" 144ms

Hooks

After Hooks.deleteTransportAfterTest() 653ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check carrier selection in create auction form

Steps

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

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

And Show all transport "true" 241ms

When Go to auction form 1s 551ms

Then Verify carrier selection value "true" 147ms

Hooks

After Hooks.deleteTransportAfterTest() 623ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if auction is available to correct participants

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 196ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 075ms

When Open transport auction form 425ms

And Select all companies checkbox in transport auction form 178ms

And Unselect company "PAA2" in transport auction form 179ms

And Put transport on auction 15s 461ms

And Open transport auction history 213ms

And Open participants section in transport auction history 153ms

Then Check if unselected "PAA2" is in transport auction history as participant 15s 089ms

Hooks

After Hooks.deleteTransportAfterTest() 692ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if auction is available to correct participants

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 683ms

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

When Open transport auction form 474ms

And Select all companies checkbox in transport auction form 134ms

And Unselect company "PSKZA2" in transport auction form 126ms

And Put transport on auction 15s 423ms

And Open transport auction history 198ms

And Open participants section in transport auction history 153ms

Then Check if unselected "PSKZA2" is in transport auction history as participant 15s 089ms

Hooks

After Hooks.deleteTransportAfterTest() 831ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if "reason" field has validation error when passing to second carrier in auction [A-7573]

Steps

Given Set token of apiUsername "super-admin-varrocrychvald" 219ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-varrocrychvald" 2s 320ms

And Set transport on auction with "1000" and "1500" by JSON file as "super-admin-varrocrychvald" 2s 734ms

And Add a bid "1500" to an auction by JSON file as "pvra1-carrier" for "super-admin-varrocrychvald" 917ms

And Add a bid "1000" to an auction by JSON file as "pvra2-carrier-2" for "super-admin-varrocrychvald" 986ms

When Login as "varrocrychvald-admin" and set token of apiUsername "super-admin-varrocrychvald" 4s 994ms

And Show all transport "true" 259ms

And Open transport auction history 1s 123ms

And Pass transport to "2" carrier in auction history 1s 192ms

Then Verify if "REASON" is visible in pass transport modal 090ms

And Confirm pass transport to carrier in pass transport modal 164ms

And Verify that "REASON" in pass transport modal has validation error 1s 084ms

Hooks

After Hooks.deleteTransportAfterTest() 745ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_UNLOAD" "super-admin-pgf" 020ms

And Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 5s 019ms

When Go to new transport "UNLOAD" 15s 517ms

And Fill transport form 28s 192ms

And Click "save-transport" save button and wait for form to disappear 15s 723ms

And Set advice window in schedule 2s 422ms

And Check is transport created in schedule and set transport id 2s 725ms

And Go to "TRANSPORT_TABLE" 519ms

And Go to transport details "UNLOAD" 30s 651ms

Then Check are transport values equals 21s 940ms

Hooks

After Hooks.deleteTransportAfterTest() 848ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-adama" 019ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 491ms

When Go to new transport "DELIVERY" 644ms

And Fill transport form 13s 194ms

And Click "save-transport" save button and wait for form to disappear 15s 723ms

And Set advice window in schedule 2s 407ms

And Check is transport created in schedule and set transport id 2s 537ms

And Go to "TRANSPORT_TABLE" 471ms

And Go to transport details "DELIVERY" 2s 781ms

Then Check are transport values equals 447ms

Hooks

After Hooks.deleteTransportAfterTest() 841ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-adama" 020ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 430ms

When Go to new transport "OWN_COLLECTION" 625ms

And Fill transport form 20s 655ms

And Click "save-transport" save button and wait for form to disappear 15s 790ms

And Set advice window in schedule 2s 399ms

And Check is transport created in schedule and set transport id 2s 514ms

And Go to "TRANSPORT_TABLE" 456ms

And Go to transport details "OWN_COLLECTION" 2s 735ms

Then Check are transport values equals 516ms

Hooks

After Hooks.deleteTransportAfterTest() 881ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-hochland" 018ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 10s 098ms

When Go to new transport "DELIVERY" 698ms

And Fill transport form 43s 900ms

And Click "save-transport" save button and wait for form to disappear 15s 741ms

And Set advice window in schedule 2s 334ms

And Check is transport created in schedule and set transport id 2s 970ms

And Go to "TRANSPORT_TABLE" 525ms

And Go to transport details "DELIVERY" 2s 883ms

Then Check are transport values equals 20s 206ms

Hooks

After Hooks.deleteTransportAfterTest() 962ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_CISTERN_DELIVERY" "super-admin-hochland" 019ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 903ms

When Go to new transport "CISTERN_DELIVERY" 693ms

And Fill transport form 46s 205ms

And Click "save-transport" save button and wait for form to disappear 15s 792ms

And Set advice window in schedule 2s 461ms

And Check is transport created in schedule and set transport id 2s 523ms

And Go to "TRANSPORT_TABLE" 510ms

And Go to transport details "CISTERN_DELIVERY" 2s 863ms

Then Check are transport values equals 7s 071ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 087ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_CISTERN_COLLECTION" "super-admin-hochland" 019ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 931ms

When Go to new transport "CISTERN_COLLECTION" 657ms

And Fill transport form 32s 139ms

And Click "save-transport" save button and wait for form to disappear 15s 701ms

And Set advice window in schedule 2s 427ms

And Check is transport created in schedule and set transport id 2s 446ms

And Go to "TRANSPORT_TABLE" 461ms

And Go to transport details "CISTERN_COLLECTION" 2s 962ms

Then Check are transport values equals 22s 025ms

Hooks

After Hooks.deleteTransportAfterTest() 868ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-hochland" 019ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 976ms

When Go to new transport "OWN_COLLECTION" 680ms

And Fill transport form 37s 053ms

And Click "save-transport" save button and wait for form to disappear 15s 759ms

And Set advice window in schedule 2s 397ms

And Check is transport created in schedule and set transport id 2s 863ms

And Go to "TRANSPORT_TABLE" 486ms

And Go to transport details "OWN_COLLECTION" 2s 813ms

Then Check are transport values equals 20s 101ms

Hooks

After Hooks.deleteTransportAfterTest() 998ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 018ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 946ms

When Go to new transport "OWN_COLLECTION_POWDER_FACTORY" 675ms

And Fill transport form 37s 135ms

And Click "save-transport" save button and wait for form to disappear 15s 752ms

And Set advice window in schedule 2s 403ms

And Check is transport created in schedule and set transport id 2s 744ms

And Go to "TRANSPORT_TABLE" 460ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 3s 492ms

Then Check are transport values equals 4s 976ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 108ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_EXPORT" "super-admin-hochland" 021ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 884ms

When Go to new transport "EXPORT" 748ms

And Fill transport form 45s 264ms

And Click "save-transport" save button and wait for form to disappear 15s 770ms

And Set advice window in schedule 2s 367ms

And Check is transport created in schedule and set transport id 2s 998ms

And Go to "TRANSPORT_TABLE" 488ms

And Go to transport details "EXPORT" 2s 955ms

Then Check are transport values equals 309ms

Error message

org.junit.ComparisonFailure: Wartości w formularzu w polu free-pallet-places są niepoprawne, wartość na stronie:  wartość poprawna: 2 expected:<[2]> but was:<[]>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at CucumberTests.Transport.Transport.checkAreValuesEquals(Transport.java:122)
	at CucumberTests.Transport.Transport.checkValueInTransportDetails(Transport.java:258)
	at CucumberTests.Transport.CreateTransport.checkTransportValues(CreateTransport.java:238)
	at ✽.Check are transport values equals(file:Features/Atom/Transport/CrudTransport.feature:14)

Hooks

After Hooks.deleteTransportAfterTest() 1s 395ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-skd" 030ms

And Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 5s 273ms

When Go to new transport "DELIVERY" 15s 419ms

And Fill transport form 32s 019ms

And Click "save-transport" save button and wait for form to disappear 15s 726ms

And Set advice window in schedule 2s 406ms

And Check is transport created in schedule and set transport id 2s 532ms

And Go to "TRANSPORT_TABLE" 492ms

And Go to transport details "DELIVERY" 30s 584ms

Then Check are transport values equals 36s 844ms

Hooks

After Hooks.deleteTransportAfterTest() 792ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-lantmannen" 024ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 5s 074ms

When Go to new transport "DELIVERY" 696ms

And Fill transport form 42s 962ms

And Click "save-transport" save button and wait for form to disappear 15s 798ms

And Set advice window in schedule 2s 373ms

And Check is transport created in schedule and set transport id 2s 582ms

And Go to "TRANSPORT_TABLE" 464ms

And Go to transport details "DELIVERY" 2s 736ms

Then Check are transport values equals 19s 891ms

Hooks

After Hooks.deleteTransportAfterTest() 938ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-lantmannen" 019ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 509ms

When Go to new transport "LOAD" 659ms

And Fill transport form 42s 709ms

And Click "save-transport" save button and wait for form to disappear 15s 784ms

And Set advice window in schedule 2s 384ms

And Check is transport created in schedule and set transport id 2s 703ms

And Go to "TRANSPORT_TABLE" 489ms

And Go to transport details "LOAD" 2s 755ms

Then Check are transport values equals 19s 861ms

Hooks

After Hooks.deleteTransportAfterTest() 981ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-keeeper" 020ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 6s 163ms

When Go to new transport "UNLOAD" 642ms

And Fill transport form 42s 592ms

And Click "save-transport" save button and wait for form to disappear 15s 790ms

And Set advice window in schedule 2s 374ms

And Check is transport created in schedule and set transport id 2s 826ms

And Go to "TRANSPORT_TABLE" 448ms

And Go to transport details "UNLOAD" 2s 798ms

Then Check are transport values equals 22s 253ms

Hooks

After Hooks.deleteTransportAfterTest() 936ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 018ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 506ms

When Go to new transport "TANKER_GRANULATE_DELIVERY" 680ms

And Fill transport form 42s 242ms

And Click "save-transport" save button and wait for form to disappear 806ms

And Set advice window in schedule 2s 615ms

And Check is transport created in schedule and set transport id 2s 660ms

And Go to "TRANSPORT_TABLE" 470ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 826ms

Then Check are transport values equals 22s 118ms

Hooks

After Hooks.deleteTransportAfterTest() 946ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-alrec" 019ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 433ms

When Go to new transport "DELIVERY" 598ms

And Fill transport form 26s 366ms

And Click "save-transport" save button and wait for form to disappear 15s 774ms

And Set advice window in schedule 2s 381ms

And Check is transport created in schedule and set transport id 2s 527ms

And Go to "TRANSPORT_TABLE" 487ms

And Go to transport details "DELIVERY" 2s 764ms

Then Check are transport values equals 17s 818ms

Hooks

After Hooks.deleteTransportAfterTest() 919ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_WEIGHING" "super-admin-hochland" 018ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 965ms

When Go to new transport "WEIGHING" 637ms

And Fill transport form 15s 656ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 840ms

And Show all transport "false" 076ms

And Go to "TRANSPORT_TABLE" 435ms

And Go to transport details "WEIGHING" 3s 234ms

And Check are transport values equals 2s 511ms

Hooks

After Hooks.deleteTransportAfterTest() 764ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_TRANSPORT" "super-admin-adama" 020ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 458ms

When Go to new transport "TRANSPORT" 645ms

And Fill transport form 29s 020ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 380ms

And Show all transport "false" 075ms

And Go to "TRANSPORT_TABLE" 430ms

And Go to transport details "TRANSPORT" 2s 903ms

And Check are transport values equals 6s 683ms

Hooks

After Hooks.deleteTransportAfterTest() 814ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_CONTAINER" "super-admin-adama" 019ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 570ms

When Go to new transport "CONTAINER" 585ms

And Fill transport form 12s 057ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 361ms

And Show all transport "false" 083ms

And Go to "TRANSPORT_TABLE" 418ms

And Go to transport details "CONTAINER" 2s 820ms

And Check are transport values equals 212ms

Hooks

After Hooks.deleteTransportAfterTest() 594ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 021ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 896ms

When Go to new transport "TRANSFER_BETWEEN_WAREHOUSES" 693ms

And Fill transport form 14s 369ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 321ms

And Show all transport "false" 075ms

And Go to "TRANSPORT_TABLE" 410ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 916ms

And Check are transport values equals 4s 706ms

Hooks

After Hooks.deleteTransportAfterTest() 639ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-piast" 021ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 213ms

When Go to new transport "DELIVERY" 660ms

And Fill transport form 24s 825ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 391ms

And Show all transport "false" 066ms

And Go to "TRANSPORT_TABLE" 338ms

And Go to transport details "DELIVERY" 2s 790ms

And Check are transport values equals 17s 637ms

Hooks

After Hooks.deleteTransportAfterTest() 732ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-piast" 021ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 534ms

When Go to new transport "LOAD" 694ms

And Fill transport form 28s 679ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 334ms

And Show all transport "false" 073ms

And Go to "TRANSPORT_TABLE" 435ms

And Go to transport details "LOAD" 2s 940ms

And Check are transport values equals 2s 690ms

Hooks

After Hooks.deleteTransportAfterTest() 756ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-keeeper" 021ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 492ms

When Go to new transport "LOAD" 608ms

And Fill transport form 27s 207ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 344ms

And Show all transport "false" 074ms

And Go to "TRANSPORT_TABLE" 414ms

And Go to transport details "LOAD" 2s 775ms

And Check are transport values equals 19s 644ms

Hooks

After Hooks.deleteTransportAfterTest() 588ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_CONTAINER" "super-admin-keeeper" 019ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 552ms

When Go to new transport "CONTAINER" 584ms

And Fill transport form 27s 206ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 264ms

And Show all transport "false" 074ms

And Go to "TRANSPORT_TABLE" 399ms

And Go to transport details "CONTAINER" 2s 801ms

And Check are transport values equals 19s 660ms

Hooks

After Hooks.deleteTransportAfterTest() 675ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_SMALLS_IMPORT" "super-admin-skz" 020ms

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

When Go to new transport "SMALLS_IMPORT" 737ms

And Fill transport form 39s 967ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 938ms

And Show all transport "false" 074ms

And Go to "TRANSPORT_TABLE" 440ms

And Go to transport details "SMALLS_IMPORT" 2s 816ms

And Check are transport values equals 11s 123ms

Hooks

After Hooks.deleteTransportAfterTest() 825ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_SMALLS_EXPORT" "super-admin-skz" 019ms

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

When Go to new transport "SMALLS_EXPORT" 739ms

And Fill transport form 40s 059ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 970ms

And Show all transport "false" 077ms

And Go to "TRANSPORT_TABLE" 433ms

And Go to transport details "SMALLS_EXPORT" 2s 827ms

And Check are transport values equals 11s 136ms

Hooks

After Hooks.deleteTransportAfterTest() 807ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-alrec" 020ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 512ms

When Go to new transport "TRANSPORT_ORDER" 726ms

And Fill transport form 33s 375ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 947ms

And Show all transport "true" 256ms

And Go to "TRANSPORT_TABLE" 416ms

And Go to transport details "TRANSPORT_ORDER" 2s 824ms

And Check are transport values equals 20s 007ms

Hooks

After Hooks.deleteTransportAfterTest() 688ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_TRANSPORT_ORDER_WITHOUT_WAREHOUSES" "super-admin-adama" 020ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 553ms

When Go to new transport "TRANSPORT" 684ms

And Fill transport form 40s 856ms

And Click "save-transport-and-close" save button and wait for form to disappear 1s 460ms

And Show all transport "false" 072ms

And Go to "TRANSPORT_TABLE" 421ms

And Go to transport details "TRANSPORT" 2s 881ms

And Check are transport values equals 4s 668ms

Hooks

After Hooks.deleteTransportAfterTest() 670ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_INBOUND_WITHOUT_WAREHOUSES" "super-admin-alrec" 021ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 485ms

When Go to new transport "INBOUND" 727ms

And Fill transport form 43s 420ms

And Click "save-transport-and-close" save button and wait for form to disappear 1s 440ms

And Show all transport "true" 323ms

And Go to "TRANSPORT_TABLE" 419ms

And Go to transport details "INBOUND" 2s 885ms

And Check are transport values equals 2s 784ms

Hooks

After Hooks.deleteTransportAfterTest() 634ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" "super-admin-farmacol" 022ms

And Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 7s 339ms

When Go to new transport "EXTERNAL_DELIVERY" 687ms

And Fill transport form 59s 615ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 346ms

And Show all transport "false" 078ms

And Go to "TRANSPORT_TABLE" 430ms

And Go to transport details "EXTERNAL_DELIVERY" 2s 869ms

And Check are transport values equals 5s 460ms

Hooks

After Hooks.deleteTransportAfterTest() 642ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" "dfa1-supplier" 021ms

And Login as "dfa1-supplier" and set token of apiUsername "dfa1-supplier" 6s 799ms

When Go to new transport "EXTERNAL_DELIVERY" 15s 573ms

And Fill transport form 52s 692ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 316ms

And Show all transport "false" 075ms

And Go to "TRANSPORT_TABLE" 430ms

And Go to transport details "EXTERNAL_DELIVERY" 2s 908ms

And Check are transport values equals 5s 351ms

Hooks

After Hooks.deleteTransportAfterTest() 833ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 2s 468ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 021ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 17s 760ms

And Show all transport "false" 082ms

When Go to transport details "UNLOAD" 30s 792ms

And Fill transport form 33s 932ms

And Click "save-transport-and-close" save button and wait for form to disappear 19s 156ms

And Go to transport details "UNLOAD" 30s 696ms

Then Check are transport values equals 4s 877ms

Hooks

After Hooks.deleteTransportAfterTest() 924ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 583ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 020ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 123ms

And Show all transport "false" 064ms

When Go to transport details "TRANSPORT" 2s 902ms

And Fill transport form 11s 107ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 906ms

And Go to transport details "TRANSPORT" 2s 876ms

Then Check are transport values equals 4s 362ms

Hooks

After Hooks.deleteTransportAfterTest() 690ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 489ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 022ms

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

And Show all transport "false" 081ms

When Go to transport details "CONTAINER" 2s 838ms

And Fill transport form 5s 181ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 929ms

And Go to transport details "CONTAINER" 2s 776ms

Then Check are transport values equals 167ms

Hooks

After Hooks.deleteTransportAfterTest() 615ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 473ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 021ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 819ms

And Show all transport "false" 078ms

When Go to transport details "DELIVERY" 2s 820ms

And Fill transport form 13s 631ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 409ms

And Go to transport details "DELIVERY" 2s 788ms

Then Check are transport values equals 471ms

Hooks

After Hooks.deleteTransportAfterTest() 840ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 499ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-adama" 021ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-adama" 2s 812ms

And Show all transport "false" 065ms

When Go to transport details "OWN_COLLECTION" 2s 760ms

And Fill transport form 24s 457ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 458ms

And Go to transport details "OWN_COLLECTION" 2s 774ms

Then Check are transport values equals 2s 658ms

Hooks

After Hooks.deleteTransportAfterTest() 922ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 023ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 172ms

And Show all transport "false" 078ms

When Go to transport details "DELIVERY" 2s 875ms

And Fill transport form 40s 765ms

And Click "save-transport-and-close" save button and wait for form to disappear 18s 081ms

And Go to transport details "DELIVERY" 2s 813ms

Then Check are transport values equals 11s 546ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 031ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 4s 583ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-hochland" 020ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 3s

And Show all transport "false" 077ms

When Go to transport details "OWN_COLLECTION" 2s 897ms

And Fill transport form 40s 900ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 502ms

And Go to transport details "OWN_COLLECTION" 2s 877ms

Then Check are transport values equals 7s 131ms

Hooks

After Hooks.deleteTransportAfterTest() 965ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 020ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 3s 130ms

And Show all transport "false" 079ms

When Go to transport details "EXPORT" 3s 023ms

And Fill transport form 53s 885ms

And Click "save-transport-and-close" save button and wait for form to disappear 2s 597ms

And Go to transport details "EXPORT" 2s 911ms

Then Check are transport values equals 9s 177ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 070ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 021ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 957ms

And Show all transport "false" 080ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 888ms

And Fill transport form 39s 586ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 509ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 759ms

Then Check are transport values equals 13s 330ms

Hooks

After Hooks.deleteTransportAfterTest() 804ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_CISTERN_DELIVERY" "super-admin-hochland" 021ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 2s 714ms

And Show all transport "false" 075ms

When Go to transport details "CISTERN_DELIVERY" 2s 885ms

And Fill transport form 30s 672ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 488ms

And Go to transport details "CISTERN_DELIVERY" 2s 855ms

Then Check are transport values equals 6s 847ms

Hooks

After Hooks.deleteTransportAfterTest() 862ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_CISTERN_COLLECTION" "super-admin-hochland" 021ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 2s 678ms

And Show all transport "false" 078ms

When Go to transport details "CISTERN_COLLECTION" 2s 840ms

And Fill transport form 28s 986ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 397ms

And Go to transport details "CISTERN_COLLECTION" 2s 801ms

Then Check are transport values equals 6s 844ms

Hooks

After Hooks.deleteTransportAfterTest() 891ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 022ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 2s 196ms

And Show all transport "false" 085ms

When Go to transport details "WEIGHING" 2s 892ms

And Fill transport form 14s 215ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 880ms

And Go to transport details "WEIGHING" 2s 803ms

Then Check are transport values equals 2s 149ms

Error message

java.lang.AssertionError: Wartości w formularzu w polu assortment są niepoprawne, wartość na stronie: Antybiotyk wartość poprawna: Makulatura
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Transport.Transport.checkAreValuesEquals(Transport.java:136)
	at CucumberTests.Transport.Transport.checkValueInTransportDetails(Transport.java:258)
	at CucumberTests.Transport.CreateTransport.checkTransportValues(CreateTransport.java:238)
	at ✽.Check are transport values equals(file:Features/Atom/Transport/CrudTransport.feature:76)

Hooks

After Hooks.deleteTransportAfterTest() 603ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 020ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 2s 782ms

And Show all transport "false" 075ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 2s 942ms

And Fill transport form 39s 417ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 428ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 2s 832ms

Then Check are transport values equals 7s 016ms

Hooks

After Hooks.deleteTransportAfterTest() 968ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 2s 654ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 16s 572ms

And Show all transport "false" 073ms

When Go to transport details "DELIVERY" 30s 638ms

And Fill transport form 28s 639ms

And Click "save-transport-and-close" save button and wait for form to disappear 1s 987ms

And Go to transport details "DELIVERY" 30s 644ms

Then Check are transport values equals 2s 626ms

Hooks

After Hooks.deleteTransportAfterTest() 816ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_LOAD" "super-admin-piast" 021ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 956ms

And Show all transport "false" 074ms

When Go to transport details "LOAD" 2s 923ms

And Fill transport form 1m 3s 016ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 559ms

And Go to transport details "LOAD" 2s 950ms

Then Check are transport values equals 26s 296ms

Hooks

After Hooks.deleteTransportAfterTest() 824ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 022ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 910ms

And Show all transport "false" 077ms

When Go to transport details "DELIVERY" 2s 875ms

And Fill transport form 18s 060ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 895ms

And Go to transport details "DELIVERY" 2s 771ms

Then Check are transport values equals 241ms

Hooks

After Hooks.deleteTransportAfterTest() 917ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 020ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 943ms

And Show all transport "false" 076ms

When Go to transport details "LOAD" 2s 855ms

And Fill transport form 31s 839ms

And Click "save-transport-and-close" save button and wait for form to disappear 19s 184ms

And Go to transport details "LOAD" 2s 793ms

Then Check are transport values equals 2s 747ms

Hooks

After Hooks.deleteTransportAfterTest() 921ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 019ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 894ms

And Show all transport "false" 075ms

When Go to transport details "UNLOAD" 2s 919ms

And Fill transport form 42s 543ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 482ms

And Go to transport details "UNLOAD" 2s 826ms

Then Check are transport values equals 7s 195ms

Hooks

After Hooks.deleteTransportAfterTest() 950ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 024ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 935ms

And Show all transport "false" 079ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 918ms

And Fill transport form 40s 814ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 496ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 766ms

Then Check are transport values equals 7s 131ms

Hooks

After Hooks.deleteTransportAfterTest() 903ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 020ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 915ms

And Show all transport "false" 077ms

When Go to transport details "LOAD" 2s 773ms

And Fill transport form 28s 629ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 950ms

And Go to transport details "LOAD" 2s 784ms

Then Check are transport values equals 4s 688ms

Hooks

After Hooks.deleteTransportAfterTest() 693ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 021ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 945ms

And Show all transport "false" 075ms

When Go to transport details "CONTAINER" 2s 770ms

And Fill transport form 28s 744ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 956ms

And Go to transport details "CONTAINER" 2s 788ms

Then Check are transport values equals 4s 745ms

Hooks

After Hooks.deleteTransportAfterTest() 732ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 641ms

And Get inputs from database "EDIT_SMALLS_EXPORT" "super-admin-skz" 019ms

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

And Show all transport "false" 076ms

When Go to transport details "SMALLS_EXPORT" 2s 929ms

And Fill transport form 36s 271ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 891ms

And Go to transport details "SMALLS_EXPORT" 2s 815ms

Then Check are transport values equals 8s 927ms

Hooks

After Hooks.deleteTransportAfterTest() 685ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 020ms

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

And Show all transport "true" 240ms

When Go to transport details "DELIVERY" 2s 845ms

And Fill transport form 22s 645ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 520ms

And Go to transport details "DELIVERY" 2s 738ms

Then Check are transport values equals 452ms

Hooks

After Hooks.deleteTransportAfterTest() 818ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

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

And Get inputs from database "EDIT_TRANSPORT_ORDER" "super-admin-alrec" 019ms

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

And Show all transport "true" 220ms

When Go to transport details "TRANSPORT_ORDER" 2s 828ms

And Fill transport form 29s 617ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 928ms

And Go to transport details "TRANSPORT_ORDER" 2s 877ms

Then Check are transport values equals 2s 733ms

Hooks

After Hooks.deleteTransportAfterTest() 713ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "keeeper-warehouseman" and set token of apiUsername "super-admin-keeeper" 6s 022ms

And Get inputs from database "EDIT_CONTAINER_WAREHOUSEMAN_CUSTOMFIELDS" "super-admin-keeeper" 019ms

And Create transport "CREATE_CONTAINER_KEEEPER_WAIMEA" by JSON file as "super-admin-keeeper" 1s 778ms

And Show all transport "false" 076ms

When Go to transport details "CONTAINER" 2s 775ms

And Fill transport form 11s 278ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 938ms

And Go to transport details "CONTAINER" 2s 727ms

Then Check are transport values equals 061ms

Error message

org.junit.ComparisonFailure: Wartości w formularzu w polu seal-number są niepoprawne, wartość na stronie:  wartość poprawna: 123456789 expected:<[123456789]> but was:<[]>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at CucumberTests.Transport.Transport.checkAreValuesEquals(Transport.java:122)
	at CucumberTests.Transport.Transport.checkValueInTransportDetails(Transport.java:258)
	at CucumberTests.Transport.CreateTransport.checkTransportValues(CreateTransport.java:238)
	at ✽.Check are transport values equals(file:Features/Atom/Transport/CrudTransport.feature:76)

Hooks

After Hooks.deleteTransportAfterTest() 740ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 202ms

And Show all transport "false" 076ms

When Delete transport 21s 439ms

Then Transport not displayed in table of transports 15s 059ms

Hooks

After Hooks.deleteTransportAfterTest() 953ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 027ms

And Show all transport "false" 077ms

When Delete transport 20s 918ms

Then Transport not displayed in table of transports 15s 093ms

Hooks

After Hooks.deleteTransportAfterTest() 744ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 907ms

And Show all transport "false" 077ms

When Delete transport 20s 596ms

Then Transport not displayed in table of transports 15s 064ms

Hooks

After Hooks.deleteTransportAfterTest() 11s 772ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 966ms

And Show all transport "false" 082ms

When Delete transport 15s 752ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //td[contains(@data-column-name, 'IDENTIFIER') and contains(@data-transport-id, '222226707')]//button (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=91.0.4472.101 (af52a90bf87030dd1523486a1cd3ae25c5d76c9b-refs/branch-heads/4472@{#1462}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.F2003R}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=91.0.4472.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 714ed1bdab8f41cbbbe0aae0f0ccfe67
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:215)
	at CucumberTests.Transport.DeleteTransportTest.deleteTransport(DeleteTransportTest.java:32)
	at ✽.Delete transport(file:Features/Atom/Transport/CrudTransport.feature:114)

Then Transport not displayed in table of transports 000ms

Hooks

After Hooks.deleteTransportAfterTest() 649ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 682ms

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

And Show all transport "false" 083ms

When Delete transport 18s 471ms

Then Transport not displayed in table of transports 15s 093ms

Hooks

After Hooks.deleteTransportAfterTest() 740ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 620ms

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

And Show all transport "false" 077ms

When Delete transport 19s 136ms

Then Transport not displayed in table of transports 15s 060ms

Hooks

After Hooks.deleteTransportAfterTest() 788ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

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

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

And Show all transport "true" 238ms

When Delete transport 19s 477ms

Then Transport not displayed in table of transports 15s 082ms

Hooks

After Hooks.deleteTransportAfterTest() 814ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

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

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

And Show all transport "true" 248ms

When Delete transport 19s 595ms

Then Transport not displayed in table of transports 15s 059ms

Hooks

After Hooks.deleteTransportAfterTest() 757ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 2s 185ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 018ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 17s 667ms

And Show all transport "false" 077ms

When Go to transport details "UNLOAD" 30s 749ms

And Fill transport form 33s 870ms

And Click "save-transport" save button 4s 312ms

And Click cancel button in transport form 191ms

And Go to transport details "UNLOAD" 30s 672ms

Then Check are transport values equals 4s 698ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 023ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 521ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 020ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 095ms

And Show all transport "false" 077ms

When Go to transport details "TRANSPORT" 2s 952ms

And Fill transport form 11s 207ms

And Click "save-transport" save button 2s 052ms

And Click cancel button in transport form 178ms

And Go to transport details "TRANSPORT" 2s 819ms

Then Check are transport values equals 4s 387ms

Hooks

After Hooks.deleteTransportAfterTest() 681ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 447ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 020ms

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

And Show all transport "false" 075ms

When Go to transport details "CONTAINER" 2s 908ms

And Fill transport form 5s 191ms

And Click "save-transport" save button 2s 057ms

And Click cancel button in transport form 174ms

And Go to transport details "CONTAINER" 2s 729ms

Then Check are transport values equals 133ms

Hooks

After Hooks.deleteTransportAfterTest() 608ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 470ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 021ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 675ms

And Show all transport "false" 066ms

When Go to transport details "DELIVERY" 2s 756ms

And Fill transport form 13s 505ms

And Click "save-transport" save button 2s 635ms

And Click cancel button in transport form 180ms

And Go to transport details "DELIVERY" 2s 770ms

Then Check are transport values equals 480ms

Hooks

After Hooks.deleteTransportAfterTest() 739ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 523ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-adama" 021ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-adama" 2s 824ms

And Show all transport "false" 079ms

When Go to transport details "OWN_COLLECTION" 2s 836ms

And Fill transport form 24s 491ms

And Click "save-transport" save button 2s 615ms

And Click cancel button in transport form 146ms

And Go to transport details "OWN_COLLECTION" 2s 707ms

Then Check are transport values equals 2s 533ms

Hooks

After Hooks.deleteTransportAfterTest() 901ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 022ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 234ms

And Show all transport "false" 081ms

When Go to transport details "DELIVERY" 2s 910ms

And Fill transport form 40s 908ms

And Click "save-transport" save button 3s 186ms

And Click cancel button in transport form 193ms

And Go to transport details "DELIVERY" 2s 728ms

Then Check are transport values equals 11s 528ms

Hooks

After Hooks.deleteTransportAfterTest() 955ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-hochland" 021ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 2s 931ms

And Show all transport "false" 076ms

When Go to transport details "OWN_COLLECTION" 2s 905ms

And Fill transport form 40s 977ms

And Click "save-transport" save button 2s 694ms

And Click cancel button in transport form 233ms

And Go to transport details "OWN_COLLECTION" 2s 840ms

Then Check are transport values equals 7s 076ms

Hooks

After Hooks.deleteTransportAfterTest() 881ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 020ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 3s 148ms

And Show all transport "false" 077ms

When Go to transport details "EXPORT" 3s 020ms

And Fill transport form 53s 846ms

And Click "save-transport" save button 2s 797ms

And Click cancel button in transport form 199ms

And Go to transport details "EXPORT" 2s 875ms

Then Check are transport values equals 9s 368ms

Hooks

After Hooks.deleteTransportAfterTest() 969ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 020ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 930ms

And Show all transport "false" 077ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 899ms

And Fill transport form 39s 683ms

And Click "save-transport" save button 2s 581ms

And Click cancel button in transport form 188ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 763ms

Then Check are transport values equals 13s 198ms

Hooks

After Hooks.deleteTransportAfterTest() 682ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_CISTERN_DELIVERY" "super-admin-hochland" 019ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 2s 719ms

And Show all transport "false" 074ms

When Go to transport details "CISTERN_DELIVERY" 2s 901ms

And Fill transport form 30s 431ms

And Click "save-transport" save button 2s 565ms

And Click cancel button in transport form 201ms

And Go to transport details "CISTERN_DELIVERY" 2s 765ms

Then Check are transport values equals 6s 815ms

Hooks

After Hooks.deleteTransportAfterTest() 919ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_CISTERN_COLLECTION" "super-admin-hochland" 022ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 2s 653ms

And Show all transport "false" 074ms

When Go to transport details "CISTERN_COLLECTION" 2s 917ms

And Fill transport form 28s 811ms

And Click "save-transport" save button 2s 616ms

And Click cancel button in transport form 176ms

And Go to transport details "CISTERN_COLLECTION" 2s 751ms

Then Check are transport values equals 6s 777ms

Hooks

After Hooks.deleteTransportAfterTest() 887ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 020ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 2s 211ms

And Show all transport "false" 081ms

When Go to transport details "WEIGHING" 2s 887ms

And Fill transport form 14s 196ms

And Click "save-transport" save button 2s 043ms

And Click cancel button in transport form 178ms

And Go to transport details "WEIGHING" 2s 754ms

Then Check are transport values equals 2s 156ms

Error message

java.lang.AssertionError: Wartości w formularzu w polu assortment są niepoprawne, wartość na stronie: Antybiotyk wartość poprawna: Makulatura
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Transport.Transport.checkAreValuesEquals(Transport.java:136)
	at CucumberTests.Transport.Transport.checkValueInTransportDetails(Transport.java:258)
	at CucumberTests.Transport.CreateTransport.checkTransportValues(CreateTransport.java:238)
	at ✽.Check are transport values equals(file:Features/Atom/Transport/CrudTransport.feature:138)

Hooks

After Hooks.deleteTransportAfterTest() 665ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 019ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 2s 721ms

And Show all transport "false" 072ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 3s 097ms

And Fill transport form 39s 498ms

And Click "save-transport" save button 2s 600ms

And Click cancel button in transport form 188ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 2s 860ms

Then Check are transport values equals 7s 038ms

Hooks

After Hooks.deleteTransportAfterTest() 964ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 2s 399ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 16s 497ms

And Show all transport "false" 072ms

When Go to transport details "DELIVERY" 30s 668ms

And Fill transport form 28s 333ms

And Click "save-transport" save button 2s 015ms

And Click cancel button in transport form 171ms

And Go to transport details "DELIVERY" 30s 601ms

Then Check are transport values equals 2s 607ms

Hooks

After Hooks.deleteTransportAfterTest() 927ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_LOAD" "super-admin-piast" 021ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 964ms

And Show all transport "false" 077ms

When Go to transport details "LOAD" 2s 882ms

And Fill transport form 1m 2s 877ms

And Click "save-transport" save button 2s 657ms

And Click cancel button in transport form 182ms

And Go to transport details "LOAD" 2s 879ms

Then Check are transport values equals 26s 366ms

Hooks

After Hooks.deleteTransportAfterTest() 754ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 963ms

And Show all transport "false" 080ms

When Go to transport details "DELIVERY" 2s 869ms

And Fill transport form 17s 941ms

And Click "save-transport" save button 1s 973ms

And Click cancel button in transport form 163ms

And Go to transport details "DELIVERY" 2s 718ms

Then Check are transport values equals 226ms

Hooks

After Hooks.deleteTransportAfterTest() 953ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 020ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 3s 012ms

And Show all transport "false" 077ms

When Go to transport details "LOAD" 2s 816ms

And Fill transport form 31s 835ms

And Click "save-transport" save button 4s 342ms

And Click cancel button in transport form 182ms

And Go to transport details "LOAD" 2s 877ms

Then Check are transport values equals 2s 705ms

Hooks

After Hooks.deleteTransportAfterTest() 998ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 021ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 865ms

And Show all transport "false" 064ms

When Go to transport details "UNLOAD" 2s 852ms

And Fill transport form 42s 679ms

And Click "save-transport" save button 2s 612ms

And Click cancel button in transport form 193ms

And Go to transport details "UNLOAD" 2s 760ms

Then Check are transport values equals 7s 010ms

Hooks

After Hooks.deleteTransportAfterTest() 909ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 021ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 3s 011ms

And Show all transport "false" 078ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 912ms

And Fill transport form 40s 910ms

And Click "save-transport" save button 2s 621ms

And Click cancel button in transport form 166ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 735ms

Then Check are transport values equals 6s 857ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 013ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 019ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 946ms

And Show all transport "false" 077ms

When Go to transport details "LOAD" 2s 813ms

And Fill transport form 28s 428ms

And Click "save-transport" save button 2s 055ms

And Click cancel button in transport form 159ms

And Go to transport details "LOAD" 2s 905ms

Then Check are transport values equals 4s 707ms

Hooks

After Hooks.deleteTransportAfterTest() 711ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 021ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 898ms

And Show all transport "false" 082ms

When Go to transport details "CONTAINER" 2s 748ms

And Fill transport form 28s 496ms

And Click "save-transport" save button 2s 046ms

And Click cancel button in transport form 159ms

And Go to transport details "CONTAINER" 2s 761ms

Then Check are transport values equals 4s 657ms

Hooks

After Hooks.deleteTransportAfterTest() 728ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 730ms

And Get inputs from database "EDIT_SMALLS_IMPORT" "super-admin-skz" 020ms

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

And Show all transport "false" 077ms

When Go to transport details "SMALLS_IMPORT" 2s 910ms

And Fill transport form 36s 159ms

And Click "save-transport" save button 2s 076ms

And Click cancel button in transport form 179ms

And Go to transport details "SMALLS_IMPORT" 2s 770ms

Then Check are transport values equals 8s 980ms

Hooks

After Hooks.deleteTransportAfterTest() 678ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 649ms

And Get inputs from database "EDIT_SMALLS_EXPORT" "super-admin-skz" 020ms

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

And Show all transport "false" 083ms

When Go to transport details "SMALLS_EXPORT" 2s 840ms

And Fill transport form 36s 028ms

And Click "save-transport" save button 2s 088ms

And Click cancel button in transport form 189ms

And Go to transport details "SMALLS_EXPORT" 2s 781ms

Then Check are transport values equals 8s 983ms

Hooks

After Hooks.deleteTransportAfterTest() 782ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 020ms

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

And Show all transport "true" 251ms

When Go to transport details "DELIVERY" 2s 822ms

And Fill transport form 22s 408ms

And Click "save-transport" save button 2s 600ms

And Click cancel button in transport form 164ms

And Go to transport details "DELIVERY" 2s 742ms

Then Check are transport values equals 545ms

Hooks

After Hooks.deleteTransportAfterTest() 900ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

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

And Get inputs from database "EDIT_TRANSPORT_ORDER" "super-admin-alrec" 021ms

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

And Show all transport "true" 235ms

When Go to transport details "TRANSPORT_ORDER" 2s 874ms

And Fill transport form 29s 637ms

And Click "save-transport" save button 2s 049ms

And Click cancel button in transport form 175ms

And Go to transport details "TRANSPORT_ORDER" 2s 796ms

Then Check are transport values equals 2s 744ms

Hooks

After Hooks.deleteTransportAfterTest() 586ms

View Feature Crud Transport

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest

Scenario Outline Check if firstPossibleStart algorithm works properly when creating transport advice

Steps

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 857ms

And Create gray windows "CREATE_GRAY_WINDOW_MWG" on "PRZESYŁKI DROBNICOWE" in "Magazyn Wyrobów Gotowych" as "super-admin-keeeper" 1s 256ms

And If user is login then logout 314ms

Then Login as "dka1-supplier" 6s 149ms

And Click button advice in transport table "LOAD" 875ms

And Check if moved to first possible start date in schedule 1s 198ms

Hooks

After Hooks.deleteTransportAfterTest() 657ms

After Hooks.deleteAllGrayWindowsAfterTest() 1m 31s 653ms

View Feature Crud Transport

@deleteTransportAfterTest @deleteAddressAfterTest

Scenario Outline Check if it is possible to create transport with new address [A-7158]

Steps

Given Set token of apiUsername "super-admin-piast" 251ms

And Set "transport" inputs from JSON file "CREATE_LOAD_WITH_NEW_ADDRESS" "super-admin-piast" 001ms

When Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 626ms

Then Go to new transport "LOAD" 699ms

And Fill transport form 26s 036ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 383ms

And Go to "COMPANIES_TAB" 898ms

And Go to company "Dostawca Piast Automat 1" details 578ms

And Check if new address with "Adresat" is visible in company details 381ms

And Go to "TRANSPORT_TABLE" 455ms

And Go to transport details "LOAD" 2s 868ms

Hooks

After Hooks.deleteTransportAfterTest() 881ms

After Hooks.deleteAddressAfterTest() 114ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Steps

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 042ms

When Go to "TRANSPORT_TABLE" 401ms

And Show all transport types 1s 156ms

And Verify that transport has "0" files 090ms

Then Add file to transport by API 1s 936ms

And Verify that transport has "1" files 2s 235ms

Hooks

After Hooks.deleteTransportAfterTest() 708ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Steps

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

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 953ms

When Go to "TRANSPORT_TABLE" 407ms

And Show all transport types 1s 158ms

And Verify that transport has "0" files 101ms

Then Add file to transport by API 1s 449ms

And Verify that transport has "1" files 1s 610ms

Hooks

After Hooks.deleteTransportAfterTest() 600ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 091ms

When Go to "TRANSPORT_TABLE" 414ms

And Show all transport types 1s 161ms

And Verify that transport has "0" files 074ms

Then Add file to transport by API 1s 523ms

And Verify that transport has "1" files 352ms

Hooks

After Hooks.deleteTransportAfterTest() 989ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Steps

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

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 962ms

When Go to "TRANSPORT_TABLE" 412ms

And Show all transport types 1s 157ms

And Verify that transport has "0" files 088ms

Then Add file to transport by API 1s 500ms

And Verify that transport has "1" files 270ms

Hooks

After Hooks.deleteTransportAfterTest() 628ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Steps

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 965ms

And Delete transport 20s 916ms

When Go to "ARCHIVE_TAB" 572ms

And Show "DELIVERY" 144ms

And Verify that transport has "0" files 6s 912ms

Then Add file to transport 436ms

And Verify that transport has "1" files 2s 834ms

Hooks

After Hooks.deleteTransportAfterTest() 740ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Steps

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

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 882ms

And Delete transport 18s 447ms

When Go to "ARCHIVE_TAB" 523ms

And Show "LOAD" 205ms

And Verify that transport has "0" files 6s 112ms

Then Add file to transport 402ms

And Verify that transport has "1" files 1s 702ms

Hooks

After Hooks.deleteTransportAfterTest() 744ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 162ms

And Delete transport 21s 436ms

When Go to "ARCHIVE_TAB" 565ms

And Show "DELIVERY" 140ms

And Verify that transport has "0" files 6s 395ms

Then Add file to transport 344ms

And Verify that transport has "1" files 1s 791ms

Hooks

After Hooks.deleteTransportAfterTest() 845ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Steps

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

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 922ms

And Delete transport 18s 375ms

When Go to "ARCHIVE_TAB" 512ms

And Show "CONTAINER" 185ms

And Verify that transport has "0" files 4s 445ms

Then Add file to transport 395ms

And Verify that transport has "1" files 1s 616ms

Hooks

After Hooks.deleteTransportAfterTest() 658ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check that the file is added to the transport after carrier acceptance when the transport has been passed to the carrier

Steps

Given Set token of apiUsername "super-admin-adama" 234ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 15s 980ms

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

And Accept transferred transport by Api 750ms

And Login as "paa1-carrier@qa.qa-test" 2s 361ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 18s 425ms

Hooks

After Hooks.deleteTransportAfterTest() 613ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check that the file is automatically added to the transport after the transport has been passed to the carrier

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 569ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 392ms

And Transfer transport to carrier by JSON file "super-admin-adama" "false" confirmation 930ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 18s 519ms

Hooks

After Hooks.deleteTransportAfterTest() 654ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check that the file is added to the transport after winning the auction

Steps

Given Set token of apiUsername "super-admin-adama" 234ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 018ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 837ms

And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 662ms

And Login as "paa1-carrier@qa.qa-test" 2s 313ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 17s 459ms

Hooks

After Hooks.deleteTransportAfterTest() 671ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it CMR documents are added to transport after creation

Steps

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

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

When Go to "TRANSPORT_TABLE" 399ms

And Show all transport "true" 246ms

Then Verify that transport has "1" CMR file 1s 569ms

Error message

java.lang.AssertionError: Liczba plików CMR w transporcie się nie zgadza! expected:<1> but was:<2>
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:834)
	at org.junit.Assert.assertEquals(Assert.java:645)
	at CucumberTests.Transport.TransportFile.verifyThatTransportHasCMRFile(TransportFile.java:75)
	at ✽.Verify that transport has "1" CMR file(file:Features/Atom/Transport/File.feature:76)

Hooks

After Hooks.deleteTransportAfterTest() 642ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it CMR documents are added to transport after creation

Steps

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

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 2s 458ms

When Go to "TRANSPORT_TABLE" 397ms

And Show all transport "true" 245ms

Then Verify that transport has "2" CMR file 1s 644ms

Hooks

After Hooks.deleteTransportAfterTest() 684ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it CMR document can be downloaded

Steps

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

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 2s 410ms

When Go to "TRANSPORT_TABLE" 393ms

And Show all transport "true" 242ms

Then Verify that "CMR" document can be downloaded 19s 032ms

Hooks

After Hooks.deleteTransportAfterTest() 665ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it CMR document can be downloaded in archive

Steps

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

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 2s 440ms

And Show all transport "true" 239ms

And Delete transport 19s 117ms

When Go to "ARCHIVE_TAB" 560ms

And Show "TRANSPORT_ORDER" 171ms

Then Verify that "CMR" document can be downloaded 23s 720ms

Hooks

After Hooks.deleteTransportAfterTest() 843ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 166ms

And Show all transport "false" 080ms

When Find transport pencil button in transports table 1s 773ms

And Click pencil and move transport to next day in schedule 5s 671ms

Then Check if transport is in new location in schedule 2s 257ms

And Check if dates in transport form are correct 3s 889ms

Hooks

After Hooks.deleteTransportAfterTest() 818ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 470ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 745ms

And Show all transport "false" 067ms

When Find transport pencil button in transports table 1s 681ms

And Click pencil and move transport to next day in schedule 20s 528ms

Then Check if transport is in new location in schedule 2s 282ms

And Check if dates in transport form are correct 3s 912ms

Hooks

After Hooks.deleteTransportAfterTest() 811ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Steps

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 927ms

And Show all transport "false" 076ms

When Find transport pencil button in transports table 1s 810ms

And Click pencil and move transport to next day in schedule 21s 363ms

Then Check if transport is in new location in schedule 2s 222ms

And Check if dates in transport form are correct 3s 805ms

Hooks

After Hooks.deleteTransportAfterTest() 817ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 925ms

And Show all transport "false" 075ms

When Find transport pencil button in transports table 1s 880ms

And Click pencil and move transport to next day in schedule 20s 517ms

Then Check if transport is in new location in schedule 2s 273ms

And Check if dates in transport form are correct 3s 926ms

Hooks

After Hooks.deleteTransportAfterTest() 852ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Steps

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

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 918ms

And Show all transport "false" 077ms

When Find transport pencil button in transports table 1s 833ms

And Click pencil and move transport to next day in schedule 20s 591ms

Then Check if transport is in new location in schedule 2s 278ms

And Check if dates in transport form are correct 3s 913ms

Hooks

After Hooks.deleteTransportAfterTest() 868ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Steps

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

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-alrec" 3s 005ms

And Show all transport "true" 331ms

When Find transport pencil button in transports table 1s 777ms

And Click pencil and move transport to next day in schedule 20s 437ms

Then Check if transport is in new location in schedule 2s 250ms

And Check if dates in transport form are correct 3s 983ms

Hooks

After Hooks.deleteTransportAfterTest() 817ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to add advice by advice button in transport table and edit transport by pencil

Steps

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 981ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 017ms

When Show all transport types 1s 122ms

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

And Set advice window in schedule 3s 306ms

And Fill advice form 10s 689ms

And Click advice save button and wait for advice form to disappear 33s 340ms

And Go to "TRANSPORT_TABLE" 479ms

And Find transport pencil button in transports table 1s 787ms

And Click pencil and move transport to next day in schedule 22s 528ms

Then Check if transport is in new location in schedule 2s 266ms

And Check if dates in transport form are correct 4s 018ms

Hooks

After Hooks.deleteTransportAfterTest() 997ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 215ms

And Show all transport "false" 078ms

When Find transport pencil button in transports table 1s 759ms

And Click pencil and move transport to next day in schedule 21s 276ms

And Move advice window "3" 1s 500ms

Then Check if advice window is in new location 064ms

Hooks

After Hooks.deleteTransportAfterTest() 4s 040ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 486ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 758ms

And Show all transport "false" 071ms

When Find transport pencil button in transports table 1s 696ms

And Click pencil and move transport to next day in schedule 20s 210ms

And Move advice window "3" 1s 615ms

Then Check if advice window is in new location 064ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 457ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 952ms

And Show all transport "false" 079ms

When Find transport pencil button in transports table 1s 728ms

And Click pencil and move transport to next day in schedule 21s 449ms

And Move advice window "3" 1s 627ms

Then Check if advice window is in new location 064ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 822ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 833ms

And Show all transport "false" 069ms

When Find transport pencil button in transports table 1s 790ms

And Click pencil and move transport to next day in schedule 20s 521ms

And Move advice window "3" 1s 522ms

Then Check if advice window is in new location 061ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 756ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

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

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 3s 073ms

And Show all transport "false" 084ms

When Find transport pencil button in transports table 1s 783ms

And Click pencil and move transport to next day in schedule 20s 544ms

And Move advice window "3" 1s 468ms

Then Check if advice window is in new location 056ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 516ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

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

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

And Show all transport "true" 241ms

When Find transport pencil button in transports table 1s 840ms

And Click pencil and move transport to next day in schedule 20s 288ms

And Move advice window "3" 1s 601ms

Then Check if advice window is in new location 064ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 248ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report custom fields are visible in proper section

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 201ms

And Go to transport details "DELIVERY" 2s 935ms

When Open section: "discrepancy-report-panel" 1s 159ms

Then Verify that no discrepancies found label is visible in discrepancy report section 174ms

And Select "NIE" in the "insp.-accord.-with-ins." 2s 682ms

And Verify that discrepancy report custom fields are visible in discrepancy report section 252ms

Hooks

After Hooks.deleteTransportAfterTest() 869ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section will open with validation errors

Steps

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 021ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 134ms

And Go to transport details "DELIVERY" 2s 917ms

And Fill transport form 40s 717ms

And Click "save-transport-and-close" save button and wait for form to disappear 18s 080ms

When Go to transport details "DELIVERY" 2s 778ms

Then Select "NIE" in the "insp.-accord.-with-ins." 2s 750ms

And Click "save-transport" save button 897ms

And Wait "2" seconds 2s

And Verify that discrepancy report section is open 074ms

And Verify that discrepancy report section contains validation errors 069ms

Hooks

After Hooks.deleteTransportAfterTest() 939ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 159ms

When Go to transport details "DELIVERY" 2s 907ms

Then Verify that discrepancy report section is available 073ms

And Open section: "discrepancy-report-panel" 1s 185ms

And Verify that generate new discrepancy report button is visible 095ms

Hooks

After Hooks.deleteTransportAfterTest() 970ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Steps

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

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 2s 975ms

When Go to transport details "OWN_COLLECTION" 2s 873ms

Then Verify that discrepancy report section is available 096ms

And Open section: "discrepancy-report-panel" 1s 320ms

And Verify that generate new discrepancy report button is visible 069ms

Hooks

After Hooks.deleteTransportAfterTest() 833ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Steps

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

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 2s 808ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 3s 002ms

Then Verify that discrepancy report section is available 078ms

And Open section: "discrepancy-report-panel" 1s 163ms

And Verify that generate new discrepancy report button is visible 089ms

Hooks

After Hooks.deleteTransportAfterTest() 969ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Steps

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

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 3s 088ms

When Go to transport details "EXPORT" 3s 016ms

Then Verify that discrepancy report section is available 077ms

And Open section: "discrepancy-report-panel" 1s 130ms

And Verify that generate new discrepancy report button is visible 124ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 314ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Steps

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

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 970ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 882ms

Then Verify that discrepancy report section is available 125ms

And Open section: "discrepancy-report-panel" 1s 234ms

And Verify that generate new discrepancy report button is visible 088ms

Hooks

After Hooks.deleteTransportAfterTest() 648ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is not available

Steps

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

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 2s 773ms

When Go to transport details "CISTERN_DELIVERY" 2s 895ms

Then Verify that discrepancy report section is not available 15s 029ms

Hooks

After Hooks.deleteTransportAfterTest() 925ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is not available

Steps

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

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 2s 558ms

When Go to transport details "CISTERN_COLLECTION" 2s 868ms

Then Verify that discrepancy report section is not available 15s 098ms

Hooks

After Hooks.deleteTransportAfterTest() 921ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is not available

Steps

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

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 2s 208ms

When Go to transport details "WEIGHING" 2s 798ms

Then Verify that discrepancy report section is not available 15s 041ms

Hooks

After Hooks.deleteTransportAfterTest() 691ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report is properly generated

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 180ms

When Go to "TRANSPORT_TABLE" 433ms

And Go to transport details "DELIVERY" 2s 923ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 794ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 508ms

And Open section: "discrepancy-report-panel" 1s 135ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 015ms

And Fill transport form 40s 850ms

And Fill discrepancy report section without closing the form 22s 082ms

And Generate discrepancy report 20s 056ms

And Download discrepancy report 343ms

Then Verify that discrepancy report file has correct values 16s 212ms

Hooks

After Hooks.deleteTransportAfterTest() 952ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if edited discrepancy report is properly generated

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 311ms

When Go to "TRANSPORT_TABLE" 381ms

And Go to transport details "DELIVERY" 2s 885ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 020ms

And Fill transport form 40s 595ms

And Open section: "discrepancy-report-panel" 1s 165ms

And Fill discrepancy report section without closing the form 22s 220ms

And Generate discrepancy report 20s 420ms

And Download discrepancy report 366ms

And Verify that discrepancy report file has correct values 15s 654ms

And Fill edited discrepancy report section 18s 832ms

And Generate edited discrepancy report 2s 775ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to be clickable: By.xpath: //button[@data-button-name='generate-discrepancy-report-button'] (tried for 2 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=91.0.4472.101 (af52a90bf87030dd1523486a1cd3ae25c5d76c9b-refs/branch-heads/4472@{#1462}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.F2003R}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=91.0.4472.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 714ed1bdab8f41cbbbe0aae0f0ccfe67
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementClickable(BasePage.java:223)
	at CucumberTests.Transport.TransportFormTest.generateEditedDiscrepancyReport(TransportFormTest.java:240)
	at ✽.Generate edited discrepancy report(file:Features/Atom/Transport/TransportForm/DiscrepancyReport.feature:95)

And Download discrepancy report 000ms

Then Verify that discrepancy report file has correct values 000ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 025ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackTransportTypeSettings

Scenario Outline Check if added step is saved with transport

Steps

Given Set token of apiUsername "super-admin-piast" 237ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 325ms

And Get "LOAD" settings from "piast" 151ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "false" 297ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-piast" 1s 982ms

And Login as "piast-admin" 5s 559ms

And Go to "TRANSPORT_TABLE" 498ms

When Go to transport details "LOAD" 2s 954ms

And Add step "unload" 331ms

And Change filled value in transport details "company-step-2" "autocomplete" "DPA2" "0" 7s 096ms

And Change filled value in transport details "recipient-step-2" "autocomplete" "Testowy" "0" 7s 011ms

Then Click "save-transport-and-close" save button and wait for form to disappear 17s 503ms

And Go to transport details "LOAD" 3s 008ms

And Verify that transport has "3" steps 036ms

Hooks

After Hooks.deleteTransportAfterTest() 719ms

After Hooks.rollbackTransportTypeSettings() 188ms

After Hooks.rollbackAddedActionAuthorities() 257ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest

Scenario Outline Check if supplier can't edit time range for load and unload step

Steps

Given Login as "pskza1-carrier-2@qa.qa-test" and set token of apiUsername "super-admin-skz" 7s 533ms

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

When Go to "TRANSPORT_TABLE" 424ms

And Go to transport details "SMALLS_IMPORT" 17s 401ms

Then Verify that user can't edit time range for load and unload 15s 025ms

Hooks

After Hooks.deleteTransportAfterTest() 733ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest

Scenario Outline Check if sum of number of pallets in transport form is correct

Steps

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

And Create transport "CREATE_DELIVERY_TWO_LOADS" by JSON file as "super-admin-neuca" 3s 266ms

And Login as "neuca-admin" 2s 053ms

And Go to "TRANSPORT_TABLE" 492ms

And Show all transport types 15s 077ms

When Go to transport details "DELIVERY" 30s 820ms

Then Check if sum of number of pallets in transport form in "load" steps is correct 253ms

Hooks

After Hooks.deleteTransportAfterTest() 995ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest

Scenario Outline Check if sum of number of pallets in transport form is correct

Steps

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

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 17s 070ms

And Login as "hochland-admin" 4s 040ms

And Go to "TRANSPORT_TABLE" 404ms

And Show all transport types 1s 179ms

When Go to transport details "EXPORT" 3s 015ms

Then Check if sum of number of pallets in transport form in "unload" steps is correct 130ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 314ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackTransportTypeSettings

Scenario Outline Check if sum of number of pallets check message is displayed in transport form

Steps

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

And Get "DELIVERY" settings from "neuca" 275ms

And Set transportType settings with values: "quantitySumCheckValue", "33" 412ms

And Login as "neuca-admin" 2s 342ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 16s 879ms

When Go to "TRANSPORT_TABLE" 509ms

And Go to transport details "DELIVERY" 30s 714ms

And Set number of pallets in "load" step in transport - "32" 303ms

And Check if number of pallets check message is not visible in transport form 15s 051ms

And Set number of pallets in "load" step in transport - "34" 226ms

Then Check if number of pallets check message is visible in transport form 069ms

Hooks

After Hooks.deleteTransportAfterTest() 963ms

After Hooks.rollbackTransportTypeSettings() 402ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackTransportTypeSettings

Scenario Outline Check if time range fields are required in new warehouse step

Steps

Given Set token of apiUsername "super-admin-farmacol" 212ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 333ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 276ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 278ms

And Login as "farmacol-admin" 6s 820ms

And Go to new transport "EXTERNAL_DELIVERY" 639ms

And Add step "unload" 207ms

And Click "save-transport-and-close" save button 910ms

Then Verify that "time-range-from-date-2" has validation error 1s 087ms

Then Verify that "time-range-to-date-2" has validation error 1s 070ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 721ms

And Click "save-transport-and-close" save button 907ms

And Verify that "time-range-from-date-2" has no validation error 068ms

And Verify that "time-range-to-date-2" has no validation error 068ms

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.rollbackTransportTypeSettings() 270ms

After Hooks.rollbackAddedActionAuthorities() 295ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities

Scenario Outline Check if new step is added in proper column in transport form

Steps

Given Set token of apiUsername "super-admin-piast" 325ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_LOAD_STEP_FROM_UNLOAD" "ACTIVE" 325ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 942ms

When Login as "piast-admin" 5s 652ms

And Go to transport details "LOAD" 3s 108ms

And Get inputs from database "PIAST_LOAD_ADD_UNLOAD_STEP" "super-admin-piast" 017ms

And Add step "unload" 332ms

And Fill step data 16s 064ms

And Get inputs from database "PIAST_LOAD_ADD_LOAD_STEP" "super-admin-piast" 019ms

And Add step "load" 190ms

And Fill step data 5s 757ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 520ms

Then Go to transport details "LOAD" 3s 053ms

And Check if "unload" step is added as "3" step in transport form 101ms

And Check if "load" step is added as "4" step in transport form 095ms

Hooks

After Hooks.deleteTransportAfterTest() 659ms

After Hooks.rollbackAddedActionAuthorities() 262ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackRemovedActionAuthorities

Scenario Outline Check if step is draggable according to authority @A-6865

Steps

Given Set token of apiUsername "super-admin-skz" 233ms

And Add action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_LOAD_STEPS" "UNLIMITED" 328ms

And Remove action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_UNLOAD_STEPS" "UNLIMITED" 056ms

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

When Login as "super-admin-skz" 9s 307ms

And Go to transport details "SMALLS_EXPORT" 2s 900ms

And Check if step is draggable "LOAD" 173ms

And Check if step is not draggable "UNLOAD" 084ms

Hooks

After Hooks.deleteTransportAfterTest() 697ms

After Hooks.rollbackAddedActionAuthorities() 258ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest @ADAMA_NIE_DZIAŁA_PRZEZ_A-7134

Scenario Outline Check if transport created without advice by similar button has correct values

Steps

Given Set "transport" inputs from JSON file "CREATE_SMALLS_IMPORT" "super-admin-skz" 001ms

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

When Go to new transport "SMALLS_IMPORT" 740ms

And Fill transport form 21s 466ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 950ms

And Show all transport "false" 074ms

And Go to transport details "SMALLS_IMPORT" 2s 842ms

And Click create similar button 15s 269ms

And Fill "transport" form "CREATE_SIMILAR_SMALLS_IMPORT" by "super-admin-skz" 001ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 266ms

And Open similar transport details 509ms

Then Check are transport values equals 2s 355ms

Hooks

After Hooks.deleteTransportAfterTest() 648ms

After Hooks.deleteSimilarTransportAfterTest() 606ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest @ADAMA_NIE_DZIAŁA_PRZEZ_A-7134

Scenario Outline Check if transport created with advice by similar button has correct values

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "pna1-carrier" 001ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 8s 166ms

When Go to new transport "DELIVERY" 15s 539ms

And Fill transport form 40s 423ms

And Click "save-transport" save button and wait for form to disappear 15s 801ms

And Set advice window in schedule 2s 381ms

And Check is transport created in schedule and set transport id 3s 459ms

And Go to "TRANSPORT_TABLE" 518ms

And Go to transport details "DELIVERY" 30s 620ms

And Click create similar button 15s 292ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 11s 642ms

And Click "save-transport" save button and wait for form to disappear 15s 733ms

And Set advice window in schedule in "2" days 4s 453ms

And Go to "TRANSPORT_TABLE" 470ms

And Open similar transport details 2s 734ms

Then Check are transport values equals 24s 386ms

Hooks

After Hooks.deleteTransportAfterTest() 1s

After Hooks.deleteSimilarTransportAfterTest() 868ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

Scenario Outline Check if transport created with advice by similar button has correct carrier

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "pna1-carrier" 001ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 2s 385ms

When Go to new transport "DELIVERY" 15s 587ms

And Fill transport form 40s 437ms

And Click "save-transport" save button and wait for form to disappear 15s 756ms

And Set advice window in schedule 2s 390ms

And Check is transport created in schedule and set transport id 3s 482ms

And Go to "TRANSPORT_TABLE" 495ms

And Go to transport details "DELIVERY" 30s 557ms

And Click create similar button 15s 271ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 11s 698ms

And Click "save-transport" save button and wait for form to disappear 15s 804ms

And Set advice window in schedule in "2" days 4s 532ms

And Go to "TRANSPORT_TABLE" 447ms

And Open similar transport details 2s 746ms

Then Check is field "CARRIER" of type "autocomplete" equals "Przewoźnik Neuca Automat 1" 083ms

Hooks

After Hooks.deleteTransportAfterTest() 1s

After Hooks.deleteSimilarTransportAfterTest() 924ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is possible to show transport details print form

Steps

Given Get inputs from database "CREATE_SMALLS_IMPORT_FOR_PRINT" "super-admin-skz" 018ms

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

When Go to new transport "SMALLS_IMPORT" 684ms

And Fill transport form 36s 497ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 882ms

And Go to transport details "SMALLS_IMPORT" 2s 869ms

And Go to transport print details form 3s 563ms

Then Check are transport values equals 8s 967ms

Hooks

After Hooks.deleteTransportAfterTest() 671ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to edit transport when auction is active

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 787ms

And Get inputs from database "CREATE_SMALLS_IMPORT" "super-admin-skz" 021ms

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

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 868ms

And Go to transport details "SMALLS_IMPORT" 2s 831ms

Then Verify that the transport can be edited 2s 010ms

And Close transport details 15s 223ms

And If user is login then logout 259ms

And Login as "pskza1-carrier@qa.qa-test" 2s 300ms

And Go to transport details "SMALLS_IMPORT" 3s 697ms

And Verify that the transport cannot be edited 46s 931ms

Hooks

After Hooks.deleteTransportAfterTest() 859ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to edit transport when auction is active

Steps

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

And Get inputs from database "CREATE_SMALLS_EXPORT" "super-admin-skz" 021ms

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

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 803ms

And Go to transport details "SMALLS_EXPORT" 2s 780ms

Then Verify that the transport can be edited 2s 002ms

And Close transport details 15s 238ms

And If user is login then logout 310ms

And Login as "pskza1-carrier@qa.qa-test" 2s 732ms

And Go to transport details "SMALLS_EXPORT" 3s 663ms

And Verify that the transport cannot be edited 46s 908ms

Hooks

After Hooks.deleteTransportAfterTest() 776ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to see hidden data in transport when auction is active

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 595ms

And Get inputs from database "HIDDEN_DATA_SMALLS_IMPORT" "super-admin-skz" 017ms

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

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 842ms

And Go to transport details "SMALLS_IMPORT" 2s 927ms

Then Verify that the hidden data in transport are not visible 1s 110ms

And Close transport details 15s 219ms

And If user is login then logout 286ms

And Login as "swisskrono-admin" 2s 702ms

And Go to transport details "SMALLS_IMPORT" 2s 898ms

And Verify that the hidden data in transport are visible 1s 678ms

Hooks

After Hooks.deleteTransportAfterTest() 843ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to see hidden data in transport when auction is active

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 575ms

And Get inputs from database "HIDDEN_DATA_SMALLS_EXPORT" "super-admin-skz" 020ms

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

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 805ms

And Go to transport details "SMALLS_EXPORT" 2s 866ms

Then Verify that the hidden data in transport are not visible 1s 098ms

And Close transport details 15s 235ms

And If user is login then logout 291ms

And Login as "swisskrono-admin" 2s 542ms

And Go to transport details "SMALLS_EXPORT" 2s 953ms

And Verify that the hidden data in transport are visible 1s 691ms

Hooks

After Hooks.deleteTransportAfterTest() 745ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is possible use 'save' and 'save transport and close' buttons after editing transport and fill discrepancy report panel

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 169ms

When Go to transport details "DELIVERY" 2s 903ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 558ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 876ms

And Change filled value in transport details "insp.-accord.-with-ins." "select" "NIE" "1" 3s 843ms

And Fill discrepancy report section without closing the form 22s 113ms

And Click "save-transport" save button 3s 189ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 432ms

And Check if transport details form is disappeared 15s 060ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 057ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest @rollbackWarehousesAccess

Scenario Outline Check if user can add description to transport

Steps

Given Set token of apiUsername "super-admin-hochland" 227ms

And Add action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 332ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 3s 038ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 3s 205ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 10s 763ms

When Go to "TRANSPORT_TABLE" 470ms

And Go to transport details "DELIVERY" 2s 856ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 562ms

Then Verify that "transport-description" in transport has value "opis" 078ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 003ms

After Hooks.rollbackAddedActionAuthorities() 263ms

After Hooks.rollbackWarehousesAccess() 705ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest @rollbackWarehousesAccess

Scenario Outline Check if user can't add description to transport

Steps

Given Set token of apiUsername "super-admin-hochland" 246ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 3s 152ms

And Remove action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 337ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 672ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 8s 804ms

When Go to "TRANSPORT_TABLE" 479ms

And Go to transport details "DELIVERY" 2s 937ms

Then Verify that "transport-description" in transport form is disabled 066ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 430ms

After Hooks.rollbackRemovedActionAuthorities() 278ms

After Hooks.rollbackWarehousesAccess() 705ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can see `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-hochland" 232ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 341ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 166ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 8s 982ms

And Show all transport "false" 083ms

When Go to "TRANSPORT_TABLE" 480ms

And Go to transport details "DELIVERY" 2s 940ms

Then Verify that "CARRIER" in transport form is visible 074ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 190ms

After Hooks.rollbackAddedActionAuthorities() 260ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can see `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-adama" 234ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 330ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 069ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 026ms

And Show all transport "false" 082ms

When Go to "TRANSPORT_TABLE" 429ms

And Go to transport details "TRANSPORT" 2s 984ms

Then Verify that "CARRIER" in transport form is visible 135ms

Hooks

After Hooks.deleteTransportAfterTest() 781ms

After Hooks.rollbackAddedActionAuthorities() 275ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can see `carrierCompany` field in transport form

Steps

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

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 301ms

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

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 4s 580ms

And Show all transport "true" 235ms

When Go to "TRANSPORT_TABLE" 353ms

And Go to transport details "TRANSPORT_ORDER" 2s 879ms

Then Verify that "CARRIER" in transport form is visible 116ms

Hooks

After Hooks.deleteTransportAfterTest() 609ms

After Hooks.rollbackAddedActionAuthorities() 273ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't see `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-hochland" 237ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 337ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 119ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 8s 944ms

And Show all transport "false" 085ms

When Go to "TRANSPORT_TABLE" 484ms

And Go to transport details "DELIVERY" 2s 953ms

Then Verify that "CARRIER" in transport form is not visible 15s 093ms

Hooks

After Hooks.deleteTransportAfterTest() 886ms

After Hooks.rollbackRemovedActionAuthorities() 277ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't see `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-adama" 223ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 324ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 122ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 080ms

And Show all transport "false" 085ms

When Go to "TRANSPORT_TABLE" 426ms

And Go to transport details "TRANSPORT" 2s 950ms

Then Verify that "CARRIER" in transport form is not visible 15s 122ms

Hooks

After Hooks.deleteTransportAfterTest() 676ms

After Hooks.rollbackRemovedActionAuthorities() 277ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't see `carrierCompany` field in transport form

Steps

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

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 333ms

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

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 4s 908ms

And Show all transport "true" 274ms

When Go to "TRANSPORT_TABLE" 390ms

And Go to transport details "TRANSPORT_ORDER" 2s 910ms

Then Verify that "CARRIER" in transport form is not visible 15s 044ms

Hooks

After Hooks.deleteTransportAfterTest() 616ms

After Hooks.rollbackRemovedActionAuthorities() 260ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can edit `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-hochland" 245ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 315ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 306ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 176ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 306ms

And Show all transport "false" 081ms

When Go to "TRANSPORT_TABLE" 485ms

And Go to transport details "DELIVERY" 2s 905ms

Then Verify that "CARRIER" in transport form is not disabled 069ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 246ms

After Hooks.rollbackAddedActionAuthorities() 522ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can edit `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-adama" 245ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 334ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 316ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 073ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 756ms

And Show all transport "false" 079ms

When Go to "TRANSPORT_TABLE" 340ms

And Go to transport details "TRANSPORT" 2s 829ms

Then Verify that "CARRIER" in transport form is not disabled 076ms

Hooks

After Hooks.deleteTransportAfterTest() 717ms

After Hooks.rollbackAddedActionAuthorities() 539ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can edit `carrierCompany` field in transport form

Steps

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

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 313ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 315ms

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

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 4s 757ms

And Show all transport "true" 272ms

When Go to "TRANSPORT_TABLE" 412ms

And Go to transport details "TRANSPORT_ORDER" 2s 902ms

Then Verify that "CARRIER" in transport form is not disabled 101ms

Hooks

After Hooks.deleteTransportAfterTest() 681ms

After Hooks.rollbackAddedActionAuthorities() 550ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't edit `carrierCompany` field in transport form

Steps

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

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 317ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 325ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 148ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 348ms

And Show all transport "false" 080ms

When Go to "TRANSPORT_TABLE" 489ms

And Go to transport details "DELIVERY" 2s 921ms

Then Verify that "CARRIER" in transport form is disabled 071ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 208ms

After Hooks.rollbackAddedActionAuthorities() 255ms

After Hooks.rollbackRemovedActionAuthorities() 266ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't edit `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-adama" 239ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 340ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 059ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 072ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 910ms

And Show all transport "false" 083ms

When Go to "TRANSPORT_TABLE" 434ms

And Go to transport details "TRANSPORT" 2s 848ms

Then Verify that "CARRIER" in transport form is disabled 135ms

Hooks

After Hooks.deleteTransportAfterTest() 672ms

After Hooks.rollbackAddedActionAuthorities() 269ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't edit `carrierCompany` field in transport form

Steps

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

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 314ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 059ms

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

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 4s 644ms

And Show all transport "true" 241ms

When Go to "TRANSPORT_TABLE" 322ms

And Go to transport details "TRANSPORT_ORDER" 2s 817ms

Then Verify that "CARRIER" in transport form is disabled 135ms

Hooks

After Hooks.deleteTransportAfterTest() 681ms

After Hooks.rollbackAddedActionAuthorities() 251ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if user can add description to archived transport

Steps

Given Set token of apiUsername "super-admin-adama" 215ms

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

And Mark custom fields as not obligatory 004ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 633ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_MAIN_DATA_SECTION" "UNLIMITED" 332ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_ADVICE" "UNLIMITED" 314ms

And Add action authority with: "adama" "adama-admin" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 310ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 019ms

When Find transport in table with status "planned" 3s 947ms

And Confirm statuses until reach "process-ended" 11s 480ms

And Wait "90" seconds 1m 30s

And Go to "ARCHIVE_TAB" 547ms

And Show "DELIVERY" 172ms

And Go to transport details "DELIVERY" 30s 664ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 586ms

And Click "save-transport-and-close" save button and wait for form to disappear 1s 976ms

And Wait "7" seconds 7s

And Go to transport details "DELIVERY" 30s 640ms

Then Verify that "transport-description" in transport has value "opis" 094ms

Hooks

After Hooks.deleteTransportAfterTest() 782ms

After Hooks.rollbackAllCustomFieldsSettings() 004ms

After Hooks.rollbackAddedActionAuthorities() 270ms

After Hooks.rollbackRemovedActionAuthorities() 531ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if driver is in list in transport form.

Steps

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 019ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 168ms

When Go to transport details "DELIVERY" 2s 910ms

And Fill transport form 40s 663ms

And Change filled value in transport details "driver-name" "text" "XXX ZZZ" "0" 1s 707ms

And Click "save-transport-and-close" save button and wait for form to disappear 18s 023ms

And Go to new transport "DELIVERY" 654ms

Then Verify that driver "XXX ZZZ" is in list 943ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 056ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if 'rate' field is visible in transport form with proper value and currency after passing transport to carrier

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 836ms

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

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 20s 948ms

And If user is login then logout 298ms

And Login as "pskza1-carrier@qa.qa-test" 2s 408ms

Then Verify that the transport has been transferred 3s 252ms

And Accept or reject "accept" transferred transport 16s 529ms

And Go to transport details "SMALLS_IMPORT" 2s 911ms

And Verify that "transaction-price" in transport form is visible 127ms

And Verify that transaction price field has correct value 086ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_IMPORT" 170ms

Hooks

After Hooks.deleteTransportAfterTest() 680ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if 'rate' field is visible in transport form with proper value and currency after passing transport to carrier

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 673ms

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

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 5s 171ms

And If user is login then logout 230ms

And Login as "pskza1-carrier@qa.qa-test" 2s 566ms

Then Verify that the transport has been transferred 3s 256ms

And Accept or reject "accept" transferred transport 16s 617ms

And Go to transport details "SMALLS_EXPORT" 2s 861ms

And Verify that "transaction-price" in transport form is visible 131ms

And Verify that transaction price field has correct value 096ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_EXPORT" 195ms

Hooks

After Hooks.deleteTransportAfterTest() 607ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if similar transport can be created based on transport with confirmed statuses [A-7322]

Steps

Given Set token of apiUsername "super-admin-dayco" 230ms

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 121ms

And Mark custom fields as not obligatory 009ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 085ms

And Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 001ms

When Login as "dayco-admin" 4s 835ms

And Click button advice in transport table "OWN_COLLECTION" 848ms

And Set advice window in schedule 3s 258ms

And Fill advice form 9s 223ms

And Click advice save button and wait for advice form to disappear 33s 265ms

And Go to "TRANSPORT_TABLE" 460ms

And Find transport in table with status "planned" 3s 694ms

And Confirm statuses until reach "on-the-area" 6s 287ms

And Go to transport details "OWN_COLLECTION" 2s 838ms

And Click create similar button 15s 267ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 6s 900ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 328ms

And Open similar transport details 440ms

Then Check if transport form modal is visible 094ms

Hooks

After Hooks.deleteTransportAfterTest() 924ms

After Hooks.deleteSimilarTransportAfterTest() 655ms

After Hooks.rollbackAllCustomFieldsSettings() 488ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if similar transport can be created based on transport with confirmed statuses [A-7322]

Steps

Given Set token of apiUsername "super-admin-dayco" 229ms

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 114ms

And Mark custom fields as not obligatory 004ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 065ms

And Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 001ms

When Login as "dayco-admin" 5s 086ms

And Click button advice in transport table "OWN_COLLECTION" 845ms

And Set advice window in schedule 3s 253ms

And Fill advice form 9s 266ms

And Click advice save button and wait for advice form to disappear 33s 342ms

And Go to "TRANSPORT_TABLE" 441ms

And Find transport in table with status "planned" 3s 699ms

And Confirm statuses until reach "during-load" 11s 450ms

And Go to transport details "OWN_COLLECTION" 2s 876ms

And Click create similar button 15s 257ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 7s 009ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 395ms

And Open similar transport details 439ms

Then Check if transport form modal is visible 109ms

Hooks

After Hooks.deleteTransportAfterTest() 880ms

After Hooks.deleteSimilarTransportAfterTest() 629ms

After Hooks.rollbackAllCustomFieldsSettings() 496ms

View Feature Transport form

@deleteTransportAfterTest @deleteCustomFieldAfterTest

Scenario Outline Check if date and time custom field appeared in transport details after creating transport

Steps

Given Set token of apiUsername "super-admin-lisner" 201ms

And Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-lisner" 001ms

And Create custom field with "CREATE_DELIVERY_DATE_AND_TIME_CFD" by "super-admin-lisner" 3s 044ms

When Login as "lisner-admin" and set token of apiUsername "super-admin-lisner" 6s 251ms

And Go to new transport "DELIVERY" 657ms

And Fill transport form 31s 338ms

And Click "save-transport" save button and wait for form to disappear 15s 725ms

And Set advice window in schedule 2s 393ms

And Go to "TRANSPORT_TABLE" 458ms

And Show all transport types 1s 166ms

And Go to transport details "DELIVERY" 2s 723ms

Then Verify that "date-and-time" in transport form is visible 086ms

Hooks

After Hooks.deleteTransportAfterTest() 939ms

After Hooks.deleteCustomFieldAfterTest() 2s 662ms

View Feature Invoice

@deleteTransportAfterTest @rollbackInvoiceCurrency

Scenario Outline Check default value of currency in invoice form [A-7389]

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 8s 689ms

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

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

When Click invoice button 3s 330ms

And Set default invoice currency value 168ms

Then Check that default currency value in invoice form is "EUR" 146ms

When Change invoice default currency value in database for "USD" transport type alias "SMALLS_IMPORT" and principal alias "swisskrono" 109ms

And Clear all cache 2s 565ms

And Login as "swisskrono-admin" 11s 205ms

And Go to "TRANSPORT_TABLE" 413ms

And Show all transport types 1s 181ms

And Click invoice button 624ms

Then Check that default currency value in invoice form is "USD" 159ms

Hooks

After Hooks.deleteTransportAfterTest() 891ms

After Hooks.rollbackInvoiceCurrency() 2s 343ms

View Feature Invoice

@deleteTransportAfterTest @rollbackInvoiceCurrency

Scenario Outline Check default value of currency in invoice form [A-7389]

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 10s 721ms

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

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

When Click invoice button 3s 456ms

And Set default invoice currency value 159ms

Then Check that default currency value in invoice form is "EUR" 136ms

When Change invoice default currency value in database for "USD" transport type alias "SMALLS_EXPORT" and principal alias "swisskrono" 108ms

And Clear all cache 2s 322ms

And Login as "swisskrono-admin" 10s 751ms

And Go to "TRANSPORT_TABLE" 401ms

And Show all transport types 1s 175ms

And Click invoice button 822ms

Then Check that default currency value in invoice form is "USD" 153ms

Hooks

After Hooks.deleteTransportAfterTest() 968ms

After Hooks.rollbackInvoiceCurrency() 2s 288ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport details button is not shown

Steps

Given Login as "lantmannen-guard-3" and set token of apiUsername "super-admin-lantmannen" 6s 160ms

And Create transport "CREATE_DELIVERY_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 2s 921ms

And Show all transport types 1s 145ms

Then Check if transport number is visible "DELIVERY" 15s 134ms

And Check if transport details is not visible 15s 058ms

Hooks

After Hooks.deleteTransportAfterTest() 901ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 16s 178ms

And Show all transport "false" 082ms

And Go to "TRANSPORT_TABLE" 404ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 184ms

When Click on transport row 171ms

Then Verify if transport row is selected 091ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 020ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 6s 588ms

And Show all transport "false" 085ms

And Go to "TRANSPORT_TABLE" 443ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 797ms

When Click on transport row 171ms

Then Verify if transport row is selected 077ms

Hooks

After Hooks.deleteTransportAfterTest() 844ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 5s 976ms

And Show all transport "false" 091ms

And Go to "TRANSPORT_TABLE" 398ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 16s 640ms

When Click on transport row 177ms

Then Verify if transport row is selected 097ms

Hooks

After Hooks.deleteTransportAfterTest() 924ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

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

And Show all transport "false" 080ms

And Go to "TRANSPORT_TABLE" 533ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 894ms

When Click on transport row 140ms

Then Verify if transport row is selected 081ms

Hooks

After Hooks.deleteTransportAfterTest() 942ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

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

And Show all transport "false" 090ms

And Go to "TRANSPORT_TABLE" 402ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 940ms

When Click on transport row 169ms

Then Verify if transport row is selected 083ms

Hooks

After Hooks.deleteTransportAfterTest() 935ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 6s 052ms

And Show all transport "true" 264ms

And Go to "TRANSPORT_TABLE" 410ms

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

When Click on transport row 170ms

Then Verify if transport row is selected 079ms

Hooks

After Hooks.deleteTransportAfterTest() 881ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 5s 630ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 458ms

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

When Accept or reject "accept" transferred transport 11s 694ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@class='btn btn-sm margin-bottom accept-transaction-button'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=91.0.4472.101 (af52a90bf87030dd1523486a1cd3ae25c5d76c9b-refs/branch-heads/4472@{#1462}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.F2003R}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=91.0.4472.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 714ed1bdab8f41cbbbe0aae0f0ccfe67
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:215)
	at CucumberTests.Transport.CarrierTransportAction.acceptOrRejectTransferredTransport(CarrierTransportAction.java:55)
	at ✽.Accept or reject "accept" transferred transport(file:Features/Atom/Transport/TransportTransfer/RejectTransport.feature:18)

Then Verify that transport is accept or reject "accept" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 655ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 653ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 428ms

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

When Accept or reject "reject" transferred transport 17s 571ms

Then Verify that transport is accept or reject "reject" 15s 069ms

Hooks

After Hooks.deleteTransportAfterTest() 694ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 8s 290ms

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

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

When Accept or reject "accept" transferred transport 19s 933ms

Then Verify that transport is accept or reject "accept" 072ms

Hooks

After Hooks.deleteTransportAfterTest() 814ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 705ms

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

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

When Accept or reject "reject" transferred transport 19s 584ms

Then Verify that transport is accept or reject "reject" 15s 087ms

Hooks

After Hooks.deleteTransportAfterTest() 772ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 724ms

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

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

When Accept or reject "accept" transferred transport 20s 145ms

Then Verify that transport is accept or reject "accept" 076ms

Hooks

After Hooks.deleteTransportAfterTest() 641ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 729ms

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

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

When Accept or reject "reject" transferred transport 19s 711ms

Then Verify that transport is accept or reject "reject" 15s 073ms

Hooks

After Hooks.deleteTransportAfterTest() 699ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - with confirmation checkbox

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 671ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 140ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 5s 290ms

And If user is login then logout 262ms

And Login as "paa1-carrier@qa.qa-test" 2s 557ms

Then Verify that the transport has been transferred with "true" 1s 760ms

Hooks

After Hooks.deleteTransportAfterTest() 864ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - with confirmation checkbox

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 495ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 084ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 5s 877ms

And If user is login then logout 216ms

And Login as "paa1-carrier@qa.qa-test" 2s 386ms

Then Verify that the transport has been transferred with "false" 1s 697ms

Hooks

After Hooks.deleteTransportAfterTest() 805ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - without confirmation checkbox

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 699ms

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

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 5s 286ms

And If user is login then logout 255ms

And Login as "pskza1-carrier@qa.qa-test" 2s 516ms

Then Verify that the transport has been transferred 3s 238ms

Hooks

After Hooks.deleteTransportAfterTest() 809ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - without confirmation checkbox

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 456ms

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

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 20s 130ms

And If user is login then logout 238ms

And Login as "pskza1-carrier@qa.qa-test" 2s 572ms

Then Verify that the transport has been transferred 3s 502ms

Hooks

After Hooks.deleteTransportAfterTest() 913ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to pass transport to carrier during auction

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 677ms

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 766ms

And Go to auction offer 1s 563ms

When Offer "1000" 313ms

And Verify that offer with "1000" has been added to auction 3s 087ms

And If user is login then logout 263ms

And Login as "swisskrono-admin" 2s 636ms

Then Go to auction details 1s 795ms

And Pass transport to carrier from auction details 1s 550ms

And If user is login then logout 1s 172ms

And Login as "pskza1-carrier@qa.qa-test" 2s 246ms

And Verify that the transport has been transferred 3s 228ms

Hooks

After Hooks.deleteTransportAfterTest() 886ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to pass transport to carrier when auction is finished

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 597ms

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 710ms

And Go to auction offer 1s 533ms

When Offer "1000" 355ms

And Verify that offer with "1000" has been added to auction 3s 078ms

And Wait till auction end 1m 53s 014ms

And If user is login then logout 287ms

Then Login as "swisskrono-admin" 2s 961ms

And Go to auction details 2s 142ms

And Pass transport to carrier from auction details 1s 504ms

And If user is login then logout 6s 222ms

And Login as "pskza1-carrier@qa.qa-test" 2s 283ms

And Verify that the transport has been transferred 3s 245ms

Hooks

After Hooks.deleteTransportAfterTest() 905ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if enabled carriers are shown in transport transfer select

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 545ms

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

And Go to "TRANSPORT_TABLE" 470ms

When Open transport transfer modal 1s 654ms

Then Verify that all enabled companies from "swisskrono" are shown in select 322ms

Hooks

After Hooks.deleteTransportAfterTest() 706ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest @rollbackRejectedSections

Scenario Outline Check if blocked carriers are shown as disabled in transport transfer select

Steps

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

And Reject main section of a "Przewoźnik Adama Automat 1" in "adama" by API 762ms

And Login as "adama-admin" 2s 114ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 34s 602ms

And Go to "TRANSPORT_TABLE" 441ms

When Open transport transfer modal 1s 676ms

Then Verify that "Przewoźnik Adama Automat 1" is blocked in select 258ms

Hooks

After Hooks.deleteTransportAfterTest() 716ms

After Hooks.rollbackRejectedSections() 518ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if transport is not visible to carrier after expiring of time to accept transport [A-7037]

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 717ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 086ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" with "120" seconds to accept transport 5s 483ms

And If user is login then logout 245ms

When Login as "paa1-carrier@qa.qa-test" 5s 143ms

And Verify that the transport has been transferred with "true" 1s 792ms

And Wait "120" seconds 2m

Then Verify if transport is not visible to carrier after expiring time to accept transport 15s 030ms

Hooks

After Hooks.deleteTransportAfterTest() 802ms

View Feature Assortment Group

@deleteTransportAfterTest

Scenario Outline Check if assortment group select is disabled when transport is during edition

Steps

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

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 3s 087ms

When Go to "TRANSPORT_TABLE" 465ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 840ms

Then Check if new assortment group is disabled in transport form 071ms

Hooks

After Hooks.deleteTransportAfterTest() 989ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to advice transport after double cancellation.

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 451ms

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

And Get inputs from database "CREATE_ADVICE_CONTAINER" "super-admin-adama" 020ms

When Show all transport types 1s 172ms

And Click button advice in transport table "CONTAINER" 341ms

And Set advice window in schedule 3s 135ms

And Click button cancel in advice form 16s 053ms

And Set advice window in schedule 2s 365ms

And Click button cancel in advice form 16s 041ms

And Set advice window in schedule 2s 391ms

And Fill advice form 19s 601ms

And Click advice save button and wait for advice form to disappear 33s 261ms

And Go to "TRANSPORT_TABLE" 490ms

And Go to transport details "CONTAINER" 2s 841ms

Then Check are advice values equals 3s 010ms

Hooks

After Hooks.deleteTransportAfterTest() 884ms

View Feature Transport transfer full scenario

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer and retransfer transport to carrier

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 674ms

And Get inputs from database "CREATE_TRANSPOSRT_ORDER" "super-admin-adama" 023ms

When Go to new transport "TRANSPORT" 729ms

And Fill transport form 28s 944ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 382ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 5s 257ms

And Check is transport "TRANSPORT" created in transport table and set transport id 1s 359ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 829ms

And Accept or reject "reject" transferred transport 17s 878ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 646ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 20s 154ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 661ms

And Accept or reject "accept" transferred transport 17s 937ms

Then Verify that transport is accept or reject "accept" 074ms

Hooks

After Hooks.deleteTransportAfterTest() 649ms

View Feature Transport transfer full scenario

@deleteTransportAfterTest @FLAKY-A-7905

Scenario Outline Check if possible to edit transport after advice cancellation.

Steps

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-piast" 019ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 060ms

When Show all transport types 1s 160ms

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

And Set advice window in schedule 3s 352ms

And Click button cancel in advice form 16s 159ms

And Go to "TRANSPORT_TABLE" 417ms

When Go to transport details "DELIVERY" 2s 845ms

And Fill transport form 1m 8s 562ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 477ms

And Go to transport details "DELIVERY" 2s 770ms

Then Check are transport values equals 062ms

Error message

org.junit.ComparisonFailure: Wartości w formularzu w polu percentage-of-execution są niepoprawne, wartość na stronie:  wartość poprawna: 22% expected:<[22%]> but was:<[]>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at CucumberTests.Transport.Transport.checkAreValuesEquals(Transport.java:122)
	at CucumberTests.Transport.Transport.checkValueInTransportDetails(Transport.java:258)
	at CucumberTests.Transport.CreateTransport.checkTransportValues(CreateTransport.java:238)
	at ✽.Check are transport values equals(file:Features/Scenario/TransportTransfer.feature:39)

Hooks

After Hooks.deleteTransportAfterTest() 909ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@deleteTransportAfterTest	3869	18	16	0	0	3903	386	18	404	6h 39m 12s 077ms	Failed

Tag Report