Cucumber-JVM Reports - Tag: @deleteTransportAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.66	03 lip 2021, 06:35

	Steps	Scenarios	Features
@deleteTransportAfterTest	3872	16	15	0	0	3903	388	16	404	6h 40m 1s 485ms	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" 5s 953ms

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

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

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

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

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

And Fill advice form 20s 143ms

And Click advice save button to check error message 195ms

Then Check if possible advice alert is displayed 076ms

Hooks

After Hooks.deleteTransportAfterTest() 702ms

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" 6s 484ms

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

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

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

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

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

And Fill advice form 10s 716ms

And Click advice save button to check error message 201ms

Then Check if possible advice alert is displayed 075ms

Hooks

After Hooks.deleteTransportAfterTest() 675ms

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

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

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

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

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

And Fill advice form 10s 792ms

And Click advice save button to check error message 199ms

Then Check if possible advice alert is displayed 079ms

Hooks

After Hooks.deleteTransportAfterTest() 691ms

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

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

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

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

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

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

And Fill advice form 16s 153ms

And Click advice save button to check error message 200ms

Then Check if possible advice alert is displayed 079ms

Hooks

After Hooks.deleteTransportAfterTest() 744ms

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

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

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

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

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

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

And Fill advice form 16s 480ms

And Click advice save button to check error message 189ms

Then Check if possible advice alert is displayed 077ms

Hooks

After Hooks.deleteTransportAfterTest() 695ms

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

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

And Show all transport types 1s 156ms

And Create advice "CREATE_ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 56s 873ms

And Go to "TRANSPORT_TABLE" 452ms

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

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

And Fill transport form 5s 179ms

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

And Expand advice panel 291ms

And Edit advice in transport details 15s 114ms

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

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

And Expand advice panel 250ms

Then Check are advice values equals after edition 737ms

Hooks

After Hooks.deleteTransportAfterTest() 942ms

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

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

And Show all transport types 1s 166ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 32s 210ms

And Go to "TRANSPORT_TABLE" 450ms

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

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

And Fill transport form 1m 8s 745ms

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

And Expand advice panel 270ms

And Edit advice in transport details 8s 189ms

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

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

And Expand advice panel 338ms

Then Check are advice values equals after edition 335ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 172ms

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

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

And Show all transport types 1s 161ms

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

And Go to "TRANSPORT_TABLE" 463ms

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

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

And Fill transport form 1m 3s 306ms

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

And Expand advice panel 275ms

And Edit advice in transport details 8s 212ms

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

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

And Expand advice panel 677ms

Then Check are advice values equals after edition 277ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 169ms

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

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

And Show all transport types 1s 178ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 52s 870ms

And Go to "TRANSPORT_TABLE" 402ms

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

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

And Fill transport form 28s 820ms

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

And Expand advice panel 277ms

And Edit advice in transport details 21s 402ms

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

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

And Expand advice panel 260ms

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 096ms

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

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

And Show all transport types 1s 189ms

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

And Go to "TRANSPORT_TABLE" 465ms

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

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

And Fill transport form 28s 880ms

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

And Expand advice panel 272ms

And Edit advice in transport details 21s 490ms

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

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

And Expand advice panel 278ms

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

Hooks

After Hooks.deleteTransportAfterTest() 878ms

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

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

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

When Show all transport types 1s 162ms

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

And Set advice window in schedule 3s 167ms

And Fill advice form 15s 947ms

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

And Go to "TRANSPORT_TABLE" 405ms

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

Then Check are advice values equals 893ms

Hooks

After Hooks.deleteTransportAfterTest() 847ms

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" 11s 807ms

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

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

When Show all transport types 1s 149ms

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

And Set advice window in schedule 7s 593ms

And Fill advice form 14s 634ms

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

And Go to "TRANSPORT_TABLE" 459ms

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

Then Check are advice values equals 2s 997ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 079ms

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

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

When Show all transport types 1s 157ms

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

And Set advice window in schedule 3s 618ms

And Fill advice form 10s 595ms

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

And Go to "TRANSPORT_TABLE" 450ms

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

Then Check are advice values equals 786ms

Hooks

After Hooks.deleteTransportAfterTest() 985ms

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

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 986ms

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

And Set advice window in schedule 3s 313ms

And Fill advice form 10s 664ms

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

And Go to "TRANSPORT_TABLE" 467ms

And Go to transport details "LOAD" 3s 037ms

Then Check are advice values equals 785ms

Hooks

After Hooks.deleteTransportAfterTest() 971ms

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

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

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

When Show all transport types 1s 168ms

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

And Set advice window in schedule 3s 272ms

And Fill advice form 16s 712ms

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

And Go to "TRANSPORT_TABLE" 433ms

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

Then Check are advice values equals 2s 928ms

Hooks

After Hooks.deleteTransportAfterTest() 963ms

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

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

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

When Show all transport types 1s 146ms

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

And Set advice window in schedule 3s 237ms

And Fill advice form 16s 485ms

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

And Go to "TRANSPORT_TABLE" 431ms

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

Then Check are advice values equals 2s 873ms

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

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

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

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

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

And Accept transferred transport by Api 850ms

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

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

When Show all transport types 1s 458ms

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

And Set advice window in schedule 3s 183ms

And Fill advice form 14s 463ms

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

And Go to "TRANSPORT_TABLE" 457ms

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

Then Check are advice values equals 2s 856ms

Hooks

After Hooks.deleteTransportAfterTest() 991ms

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

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

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

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

And Accept transferred transport by Api 831ms

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

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

When Show all transport types 1s 170ms

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

And Set advice window in schedule 3s 429ms

And Fill advice form 17s 755ms

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

And Go to "TRANSPORT_TABLE" 447ms

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

Then Check are advice values equals 3s 016ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 068ms

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

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

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

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

And Accept transferred transport by Api 807ms

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

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

When Show all transport types 1s 215ms

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

And Set advice window in schedule 3s 384ms

And Fill advice form 17s 985ms

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

And Go to "TRANSPORT_TABLE" 391ms

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

Then Check are advice values equals 2s 968ms

Hooks

After Hooks.deleteTransportAfterTest() 969ms

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

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

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

And Accept transferred transport by Api 809ms

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

When Show all transport types 1s 210ms

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

And Set week view 1s 900ms

And Show yesterday 1s 168ms

Then Check if advice restriction blockade windows are visible 044ms

Hooks

After Hooks.deleteTransportAfterTest() 654ms

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 15s 989ms

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

And Accept transferred transport by Api 763ms

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

When Show all transport types 1s 182ms

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

And Set week view 2s 336ms

And Show yesterday 1s 175ms

Then Check if advice restriction blockade windows are visible 087ms

Hooks

After Hooks.deleteTransportAfterTest() 734ms

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

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

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

And Accept transferred transport by Api 686ms

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

When Show all transport types 1s 167ms

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

And Set week view 2s 310ms

And Show yesterday 1s 316ms

Then Check if advice restriction blockade windows are visible 065ms

Hooks

After Hooks.deleteTransportAfterTest() 681ms

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" 3s 017ms

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

And Show all transport "false" 099ms

And Click on time window date 1s 688ms

And Select view "DAYS_4" 2s 179ms

And Move advice window "3" 1s 496ms

Then Check if advice window is in new location 062ms

Hooks

After Hooks.deleteTransportAfterTest() 4s 338ms

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" 6s 085ms

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

And Show all transport "false" 085ms

And Click on time window date 16s 038ms

And Select view "DAYS_4" 2s 190ms

And Move advice window "3" 1s 684ms

Then Check if advice window is in new location 093ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 574ms

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" 5s 042ms

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

And Show all transport "false" 092ms

And Click on time window date 15s 860ms

And Select view "DAYS_4" 2s 168ms

And Move advice window "3" 1s 641ms

Then Check if advice window is in new location 062ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 680ms

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" 4s 920ms

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

And Show all transport "false" 089ms

And Click on time window date 1s 883ms

And Select view "DAYS_4" 2s 180ms

And Move advice window "3" 1s 568ms

Then Check if advice window is in new location 063ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 746ms

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

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

And Show all transport "false" 088ms

And Click on time window date 1s 923ms

And Select view "DAYS_4" 2s 168ms

And Move advice window "3" 1s 482ms

Then Check if advice window is in new location 066ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 889ms

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

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

And Show all transport "true" 241ms

And Click on time window date 1s 772ms

And Select view "DAYS_4" 2s 140ms

And Move advice window "3" 1s 502ms

Then Check if advice window is in new location 065ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 391ms

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

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

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

When Show all transport types 1s 159ms

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

And Set advice window in schedule 3s 294ms

And Fill advice form 10s 529ms

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

And Go to "TRANSPORT_TABLE" 489ms

And Click on time window date 1s 801ms

And Select view "DAYS_4" 2s 130ms

And Move advice window "3" 1s 611ms

Then Check if advice window is in new location 071ms

Hooks

After Hooks.deleteTransportAfterTest() 4s 686ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 056ms

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

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

And Go to "TRANSPORT_TABLE" 412ms

And Show all transport types 1s 139ms

And Click on time window date 1s 721ms

And Scroll to time window "adviceWindow" 159ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 3s 240ms

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

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

And Go to "TRANSPORT_TABLE" 431ms

And Show all transport types 1s 162ms

And Click on time window date 1s 850ms

And Scroll to time window "adviceWindow" 143ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 920ms

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

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

And Go to "TRANSPORT_TABLE" 435ms

And Show all transport types 1s 142ms

And Click on time window date 1s 710ms

And Scroll to time window "adviceWindow" 159ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 966ms

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" 9s 074ms

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

And Go to "TRANSPORT_TABLE" 545ms

And Show all transport types 15s 045ms

And Click on time window date 16s 130ms

And Scroll to time window "adviceWindow" 221ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 3s 318ms

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

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

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

When Show all transport types 1s 152ms

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

And Set advice window in schedule 3s 340ms

And Fill advice form 10s 688ms

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

And Go to "TRANSPORT_TABLE" 501ms

And Click on time window date 1s 779ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 3s 775ms

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

And Go to "WAREHOUSE_TAB" 1s 174ms

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

When Go to new transport "DELIVERY" 676ms

And Fill transport form 45s 247ms

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

And Click previous page button in browser 062ms

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

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

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

And Go to "WAREHOUSE_TAB" 1s 175ms

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

When Go to new transport "DELIVERY" 684ms

And Fill transport form 45s 013ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 002ms

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

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

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

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

When Show all transport types 1s 157ms

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

And Fill advice form 13s 929ms

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

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

And Open statuses popup 182ms

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

Hooks

After Hooks.deleteTransportAfterTest() 764ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if time window details preview displays correctly

Steps

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

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

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

And Login as "farmacol-admin" 8s 143ms

And Go to "WAREHOUSE_TAB" 1s 110ms

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

And Set week view 2s 451ms

And Move cursor over time window element 470ms

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

Hooks

After Hooks.deleteTransportAfterTest() 889ms

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

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

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

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

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

When Go to "TRANSPORT_TABLE" 390ms

And Show all transport types 1s 158ms

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

And Fill advice form 10s 595ms

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

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

And Set advice window in schedule 3s 388ms

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

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

And Go to "TRANSPORT_TABLE" 437ms

And Show all transport types 1s 157ms

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

Then Check are advice values equals 2s 696ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 034ms

After Hooks.deleteModeOfTransportationAfterTest() 347ms

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

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

And Fill transport form 38s 844ms

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

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

And Set advice window in schedule 2s 379ms

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

Then Go to "OWN_COMPANY_TAB" 722ms

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 129ms

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

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

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

When Go to "TRANSPORT_TABLE" 367ms

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

And Show all transport types 1s 181ms

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

Hooks

After Hooks.deleteTransportAfterTest() 678ms

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

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

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

When Go to "TRANSPORT_TABLE" 432ms

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

And Show all transport types 1s 183ms

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

Hooks

After Hooks.deleteTransportAfterTest() 778ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 386ms

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

And Show all transport types 1s 180ms

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

Hooks

After Hooks.deleteTransportAfterTest() 697ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 411ms

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

And Show all transport types 1s 187ms

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

Hooks

After Hooks.deleteTransportAfterTest() 776ms

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

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

And Delete created transport by API 724ms

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

When Go to "ARCHIVE_TAB" 489ms

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

And Show "SMALLS_IMPORT" 185ms

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

Hooks

After Hooks.deleteTransportAfterTest() 915ms

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" 16s 085ms

And Delete created transport by API 734ms

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

When Go to "ARCHIVE_TAB" 454ms

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

And Show "SMALLS_IMPORT" 162ms

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

Hooks

After Hooks.deleteTransportAfterTest() 888ms

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

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

And Delete created transport by API 672ms

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

When Go to "ARCHIVE_TAB" 490ms

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

And Show "SMALLS_IMPORT" 175ms

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

Hooks

After Hooks.deleteTransportAfterTest() 985ms

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

And Delete created transport by API 711ms

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

When Go to "ARCHIVE_TAB" 474ms

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

And Show "SMALLS_IMPORT" 175ms

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

Hooks

After Hooks.deleteTransportAfterTest() 817ms

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

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

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

And Go to "TRANSPORT_TABLE" 368ms

And Show all transport "true" 260ms

And Select transportType "TRANSPORT_ORDER" 1s 317ms

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

Hooks

After Hooks.deleteTransportAfterTest() 722ms

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

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

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

And Accept transferred transport by Api 748ms

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

And Delete created transport by API 1s 013ms

When Go to "ARCHIVE_TAB" 512ms

And Show "SMALLS_IMPORT" 171ms

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 030ms

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

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

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

And Accept transferred transport by Api 740ms

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

And Delete created transport by API 930ms

When Go to "ARCHIVE_TAB" 549ms

And Show "SMALLS_EXPORT" 172ms

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

Hooks

After Hooks.deleteTransportAfterTest() 960ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 479ms

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

And Toggle transport table days limit filter 172ms

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 056ms

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

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

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

When Go to "TRANSPORT_TABLE" 468ms

And Go to auction form 1s 572ms

And Select contractors group "Kraj" 240ms

Then Verify that carrier "PSKZA1" is selected 081ms

Hooks

After Hooks.deleteTransportAfterTest() 694ms

After Hooks.removeContractorsGroup() 304ms

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

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

When Go to "TRANSPORT_TABLE" 481ms

And Go to auction form 1s 543ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 714ms

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

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

When Go to "TRANSPORT_TABLE" 472ms

And Go to auction form 1s 538ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 736ms

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

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

And Show all transport "false" 082ms

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

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

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

And Expand index panel 346ms

And Click add index button 319ms

And Fill index form 11s 744ms

And Click ok button in index form 15s 305ms

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

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

And Expand index panel 255ms

Then Check are transport values equals 273ms

Hooks

After Hooks.deleteTransportAfterTest() 756ms

After Hooks.deleteProductAfterTest() 205ms

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

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

And Show all transport "true" 249ms

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

And Expand index panel 324ms

And Click add index button 294ms

And Fill index form 8s 493ms

And Click ok button in index form 15s 280ms

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

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

And Expand index panel 294ms

Then Check are transport values equals 2s 394ms

Hooks

After Hooks.deleteTransportAfterTest() 735ms

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

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

And Show all transport "false" 082ms

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

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

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

And Add index to transport 27s 520ms

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

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

And Expand index panel 264ms

And Click delete index button 178ms

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

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

And Expand index panel 301ms

Then Verify that transport has no indexes 15s 082ms

Hooks

After Hooks.deleteTransportAfterTest() 747ms

After Hooks.deleteProductAfterTest() 145ms

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

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

And Show all transport "true" 215ms

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

And Add index to transport 24s 247ms

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

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

And Expand index panel 279ms

And Click delete index button 200ms

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

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

And Expand index panel 269ms

Then Verify that transport has no indexes 15s 026ms

Hooks

After Hooks.deleteTransportAfterTest() 638ms

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

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

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

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

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

And Add index to transport 25s 792ms

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

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 46s 203ms

When Click on index details icon 209ms

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

Hooks

After Hooks.deleteTransportAfterTest() 953ms

After Hooks.deleteProductAfterTest() 146ms

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

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

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

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

And Show all transport types 1s 161ms

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

And Set advice window in schedule 3s 159ms

And Fill advice form 14s 926ms

And Click advice save button and wait for advice form to disappear 18s 403ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 857ms

After Hooks.cleanUserDetailsAfterTest() 1s 308ms

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

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

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

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

And Show all transport types 1s 201ms

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

And Set advice window in schedule 3s 307ms

And Fill advice form 10s 496ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 876ms

After Hooks.cleanUserDetailsAfterTest() 1s 072ms

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

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

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

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

And Show all transport types 1s 151ms

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

And Set advice window in schedule 3s 206ms

And Fill advice form 16s 373ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 972ms

After Hooks.cleanUserDetailsAfterTest() 1s 465ms

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

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

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

And Show all transport types 1s 177ms

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

And Go to "TRANSPORT_TABLE" 488ms

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

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

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

And Fill transport form 5s 198ms

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

And Expand advice panel 253ms

And Edit advice in transport details 15s 063ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 927ms

After Hooks.cleanUserDetailsAfterTest() 1s 346ms

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

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

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

And Show all transport types 1s 142ms

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

And Go to "TRANSPORT_TABLE" 490ms

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

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

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

And Fill transport form 1m 8s 669ms

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

And Expand advice panel 261ms

And Edit advice in transport details 8s 198ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 179ms

After Hooks.cleanUserDetailsAfterTest() 1s 080ms

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

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

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

And Show all transport types 1s 128ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 52s 913ms

And Go to "TRANSPORT_TABLE" 443ms

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

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

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

And Fill transport form 28s 765ms

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

And Expand advice panel 282ms

And Edit advice in transport details 21s 504ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 990ms

After Hooks.cleanUserDetailsAfterTest() 1s 585ms

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

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

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

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

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

Then Check if user got a mail 000ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 969ms

After Hooks.cleanUserDetailsAfterTest() 926ms

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

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

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

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

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

And Wait "120" seconds 2m

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 992ms

After Hooks.cleanUserDetailsAfterTest() 1s 544ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 044ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 900ms

After Hooks.cleanUserDetailsAfterTest() 1s 982ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 739ms

After Hooks.cleanUserDetailsAfterTest() 2s 081ms

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

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

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

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

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

And Wait till auction end 1m 57s 019ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 820ms

After Hooks.cleanUserDetailsAfterTest() 1s 762ms

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

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

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

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

And Wait till auction end 1m 57s 018ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 728ms

After Hooks.cleanUserDetailsAfterTest() 1s 353ms

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" 5s 216ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 781ms

After Hooks.cleanUserDetailsAfterTest() 1s 934ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 714ms

After Hooks.cleanUserDetailsAfterTest() 2s 270ms

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Otrzymano zlecenie" 1m 1s 486ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 745ms

After Hooks.cleanUserDetailsAfterTest() 2s 029ms

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

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

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

And Go to "TRANSPORT_TABLE" 388ms

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

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

And Fill transport form 40s 631ms

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

And Fill discrepancy report section 41s 015ms

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

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

And Generate discrepancy report 21s 643ms

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

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() 1s 061ms

After Hooks.cleanUserDetailsAfterTest() 3s 671ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 706ms

After Hooks.cleanUserDetailsAfterTest() 2s 107ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 760ms

After Hooks.cleanUserDetailsAfterTest() 2s 287ms

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

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

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

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

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.ZaXtAd}, 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: 9275f62421ea78059964e579c60af950
	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() 719ms

After Hooks.cleanUserDetailsAfterTest() 2s 152ms

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

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

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

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

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.ZaXtAd}, 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: 9275f62421ea78059964e579c60af950
	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() 685ms

After Hooks.cleanUserDetailsAfterTest() 2s 062ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 793ms

After Hooks.cleanUserDetailsAfterTest() 1s 690ms

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

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

And Fill transport form 45s 885ms

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

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

And Set advice window in schedule 2s 400ms

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

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

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

And Go to "TRANSPORT_TABLE" 549ms

And Show all transport "false" 079ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 902ms

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

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

And Set status of MOT to "AWAITING_VERIFICATION" 294ms

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

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

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

When Login as "super-admin-bausch" 6s 160ms

And Go to "TRANSPORT_TABLE" 385ms

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

And Set advice window in schedule 3s 281ms

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

Hooks

After Hooks.deleteTransportAfterTest() 743ms

After Hooks.deleteModeOfTransportationAfterTest() 300ms

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

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

And Set status of MOT to "DISABLED" 293ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 467ms

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

And Set advice window in schedule 3s 310ms

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

Hooks

After Hooks.deleteTransportAfterTest() 699ms

After Hooks.deleteModeOfTransportationAfterTest() 277ms

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

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

And Set status of MOT to "ACCEPTED" 304ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 456ms

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

And Set advice window in schedule 3s 303ms

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

Hooks

After Hooks.deleteTransportAfterTest() 711ms

After Hooks.deleteModeOfTransportationAfterTest() 315ms

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

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

And Set status of MOT to "UPDATED" 296ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 483ms

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

And Set advice window in schedule 3s 292ms

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

Hooks

After Hooks.deleteTransportAfterTest() 657ms

After Hooks.deleteModeOfTransportationAfterTest() 297ms

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

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

And Set status of MOT to "REJECTED" 280ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 457ms

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

And Set advice window in schedule 3s 225ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 682ms

After Hooks.deleteModeOfTransportationAfterTest() 302ms

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

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

And Set status of MOT to "BLOCKED" 289ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 464ms

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

And Set advice window in schedule 3s 325ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 779ms

After Hooks.deleteModeOfTransportationAfterTest() 295ms

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

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

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

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

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

And Set advice window in schedule 3s 342ms

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

And Fill advice form 18s 037ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 124ms

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

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

When Add transport by SKApi in "MGW" 022ms

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

And Go to "TRANSPORT_TABLE" 370ms

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

Then Check are transport values equals 1s 301ms

Hooks

After Hooks.deleteTransportAfterTest() 710ms

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

When Add transport by SKApi in "MGW" 021ms

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

And Go to "TRANSPORT_TABLE" 367ms

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

Then Check are transport values equals 1s 279ms

Hooks

After Hooks.deleteTransportAfterTest() 689ms

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" and set token of apiUsername "super-admin-skz" 2s 650ms

When Add transport by SKApi in "MGW" 021ms

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

And Go to "TRANSPORT_TABLE" 403ms

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

Then Check are transport values equals 1s 311ms

Hooks

After Hooks.deleteTransportAfterTest() 722ms

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

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

When Add transport by SKApi in "HRL" 023ms

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

And Go to "TRANSPORT_TABLE" 430ms

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

Then Check are transport values equals 1s 358ms

Hooks

After Hooks.deleteTransportAfterTest() 806ms

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

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

When Add transport by SKApi in "HRL" 030ms

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

And Go to "TRANSPORT_TABLE" 386ms

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

Then Check are transport values equals 1s 296ms

Hooks

After Hooks.deleteTransportAfterTest() 759ms

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

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

When Add transport by SKApi in "HRL" 023ms

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

And Go to "TRANSPORT_TABLE" 379ms

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

Then Check are transport values equals 1s 325ms

Hooks

After Hooks.deleteTransportAfterTest() 791ms

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

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

And Set another client name "Pepsi" 000ms

When Add transport by SKApi in "MGW" 022ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 678ms

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

When Add transport by SKApi in "" 018ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 57s 800ms

And Go to "TRANSPORT_TABLE" 397ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 791ms

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

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

And Add transport by SKApi in "MGW" 021ms

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

And Check is transport "CONTAINER" created in transport table and set transport id 51s 976ms

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

And Set advice window in schedule 3s 378ms

And Fill advice form 18s 148ms

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

And Go to "TRANSPORT_TABLE" 467ms

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

Then Check are advice values equals 2s 935ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 043ms

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

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

And Add transport by SKApi in "MGW" 024ms

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

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

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

And Set advice window in schedule 3s 390ms

And Fill advice form 18s 063ms

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

And Go to "TRANSPORT_TABLE" 473ms

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

Then Check are advice values equals 2s 893ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 059ms

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

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

And Add transport by SKApi in "MGW" 023ms

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

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 52s 528ms

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

And Set advice window in schedule 3s 341ms

And Fill advice form 18s 020ms

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

And Go to "TRANSPORT_TABLE" 490ms

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

Then Check are advice values equals 2s 920ms

Hooks

After Hooks.deleteTransportAfterTest() 987ms

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

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

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

And Set advice window in schedule 3s 359ms

And Fill advice form 18s 048ms

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

And Go to "TRANSPORT_TABLE" 462ms

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 137ms

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

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

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 1m 1s 033ms

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

And Set advice window in schedule 3s 428ms

And Fill advice form 18s 070ms

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

And Go to "TRANSPORT_TABLE" 449ms

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 053ms

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

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

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 57s 712ms

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

And Set advice window in schedule 3s 370ms

And Fill advice form 18s 026ms

And Click advice save button and wait for advice form to disappear 34s 037ms

And Go to "TRANSPORT_TABLE" 461ms

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 114ms

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

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

And Add transport by SKApi in "MGW" 020ms

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

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

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

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

And Fill advice form 17s 905ms

And Click advice save button to check error message 199ms

Then Check if possible advice alert is displayed 067ms

Hooks

After Hooks.deleteTransportAfterTest() 819ms

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

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

And Add transport by SKApi in "MGW" 024ms

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

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

And Go to "TRANSPORT_TABLE" 459ms

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

And Expand advice panel 301ms

And Edit advice in transport details 16s 702ms

And Fill arrival date field 2s 535ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 046ms

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

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

And Add transport by SKApi in "MGW" 023ms

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

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

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

And Go to "TRANSPORT_TABLE" 448ms

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

And Expand advice panel 312ms

And Edit advice in transport details 16s 613ms

And Fill arrival date field 2s 544ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s

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

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

And Add transport by SKApi in "MGW" 021ms

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

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

And Go to "TRANSPORT_TABLE" 516ms

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

And Expand advice panel 309ms

And Edit advice in transport details 16s 678ms

And Fill arrival date field 2s 533ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 949ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 295ms

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

And Select view "DAYS_2" 2s 164ms

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

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

And Select view "DAYS_2" 2s 136ms

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 666ms

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

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

When Go to "WAREHOUSE_TAB" 1s 187ms

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

And Select view "DAYS_2" 2s 143ms

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

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

And Select view "DAYS_2" 2s 134ms

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 576ms

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

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

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

When Go to "WAREHOUSE_TAB" 1s 313ms

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

And Select view "DAYS_2" 2s 172ms

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

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

And Select view "DAYS_2" 2s 157ms

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 656ms

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

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

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

When Go to "WAREHOUSE_TAB" 891ms

And Select warehouse "MGW" 1s 389ms

And Select view "DAYS_2" 2s 157ms

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

And Select warehouse "HRL" 1s 518ms

And Select view "DAYS_2" 2s 132ms

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 600ms

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

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

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

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

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

And Fill transport form 37s 249ms

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

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

And Set advice window in schedule 2s 325ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 053ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 123ms

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

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

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

When Login as "neuca-admin" 2s 376ms

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

And Fill transport form 37s 373ms

And Get sum of pallets of "unload" in transport form 077ms

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

And Set advice window in schedule 2s 396ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 096ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 147ms

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

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

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

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

When Login as "neuca-admin" 2s 443ms

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

And Fill transport form 40s 279ms

And Get sum of pallets of "unload" in transport form 094ms

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

And Set advice window in schedule 2s 397ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 077ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 140ms

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

And Get custom field settings for "DELIVERY" transport type and "hochland" company 203ms

And Mark custom fields as not obligatory 007ms

And Login as "hochland-admin" 2s 845ms

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

When Find transport in table with status "advice-added" 3s 696ms

And Confirm statuses until reach "process-ended" 22s 979ms

Then Check if transport has "process-ended" 071ms

Hooks

After Hooks.deleteTransportAfterTest() 943ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 920ms

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

And Get custom field settings for "UNLOAD" transport type and "pgf" company 099ms

And Mark custom fields as not obligatory 005ms

And Login as "pgf-admin" 4s 619ms

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

When Find transport in table with status "planned" 17s 615ms

And Confirm statuses until reach "process-ended" 12s 560ms

Then Check if transport has "process-ended" 081ms

Hooks

After Hooks.deleteTransportAfterTest() 986ms

After Hooks.rollbackAllCustomFieldsSettings() 446ms

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 652ms

When Find transport in table with status "planned" 3s 577ms

And Confirm statuses until reach "process-ended" 11s 479ms

Then Check if transport has "process-ended" 064ms

Hooks

After Hooks.deleteTransportAfterTest() 792ms

After Hooks.rollbackAllCustomFieldsSettings() 408ms

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

And Get custom field settings for "DELIVERY" transport type and "lantmannen" company 097ms

And Mark custom fields as not obligatory 004ms

And Login as "lantmannen-admin" 4s 536ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 3s 020ms

When Find transport in table with status "potwierdzony" 3s 727ms

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

Then Check if transport has "process-ended" 075ms

Hooks

After Hooks.deleteTransportAfterTest() 874ms

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

And Get custom field settings for "LOAD" transport type and "lantmannen" company 100ms

And Mark custom fields as not obligatory 005ms

And Login as "lantmannen-admin" 2s 230ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 3s 040ms

When Find transport in table with status "created" 3s 721ms

And Confirm statuses until reach "process-ended" 27s 053ms

Then Check if transport has "process-ended" 079ms

Hooks

After Hooks.deleteTransportAfterTest() 863ms

After Hooks.rollbackAllCustomFieldsSettings() 005ms

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

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 112ms

And Mark custom fields as not obligatory 006ms

And Login as "keeeper-admin" 5s 929ms

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

When Find transport in table with status "planned" 3s 723ms

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

Then Check if transport has "process-ended" 070ms

Hooks

After Hooks.deleteTransportAfterTest() 913ms

After Hooks.rollbackAllCustomFieldsSettings() 465ms

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

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 117ms

And Mark custom fields as not obligatory 007ms

And Login as "keeeper-admin" 5s 610ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 935ms

When Find transport in table with status "planned" 3s 710ms

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

Then Check if transport has "process-ended" 080ms

Hooks

After Hooks.deleteTransportAfterTest() 951ms

After Hooks.rollbackAllCustomFieldsSettings() 597ms

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

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

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

When Accept or reject "accept" transferred transport 19s 588ms

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

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

And Set advice window in schedule 3s 384ms

And Fill advice form 17s 929ms

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

And Check if window is "silver" 4s 084ms

And Go to "TRANSPORT_TABLE" 438ms

Then Check if transport has "process-ended" 742ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 033ms

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

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

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

When Accept or reject "accept" transferred transport 19s 763ms

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

And Click button advice in transport table "SMALLS_EXPORT" 264ms

And Set advice window in schedule 3s 392ms

And Fill advice form 17s 913ms

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

And Check if window is "silver" 4s 084ms

And Go to "TRANSPORT_TABLE" 458ms

Then Check if transport has "process-ended" 857ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 019ms

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

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_ADVICE" "CHECKPOINT_BASED" "ARRIVAL" 471ms

And Get custom field settings for "DELIVERY" transport type and "hochland" company 191ms

And Mark custom fields as not obligatory 006ms

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

When Login as "hochland-admin" 9s 965ms

And Find transport in table with status "advice-added" 3s 783ms

And Confirm statuses until reach "arrived" 6s 268ms

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

Then Check if it is not possible to edit advice 901ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 031ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 863ms

After Hooks.rollbackAddedActionAuthorities() 308ms

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

And Get custom field settings for "DELIVERY" transport type and "hochland" company 192ms

And Mark custom fields as not obligatory 008ms

And Login as "hochland-admin" 9s 587ms

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

When Find transport in table with status "advice-added" 3s 690ms

And Check if transport row is "blue" 3s 224ms

And Confirm statuses until reach "arrived" 6s 269ms

And Check if transport row is "green" 3s 226ms

And Confirm statuses until reach "during-unload" 6s 238ms

Then Check if transport row is "orange" 3s 226ms

And Confirm statuses until reach "unloaded" 6s 232ms

Then Check if transport row is "darkgoldenrod" 3s 206ms

And Confirm statuses until reach "process-ended" 6s 170ms

Then Check if transport row is "silver" 3s 224ms

Hooks

After Hooks.deleteTransportAfterTest() 993ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 775ms

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

And Get custom field settings for "DELIVERY" transport type and "piast" company 234ms

And Mark custom fields as not obligatory 009ms

And Login as "piast-admin" 5s 690ms

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

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

And Show all transport types 1s 157ms

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

And Set advice window in schedule 3s 317ms

And Fill advice form 10s 527ms

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

And Go to "TRANSPORT_TABLE" 482ms

And Find transport in table with status "advice-added" 3s 713ms

And Confirm statuses until reach "left-the-area" 31s 364ms

Then Check if next status is not possible to confirm 316ms

Hooks

After Hooks.deleteTransportAfterTest() 957ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 805ms

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

And Get custom field settings for "LOAD" transport type and "piast" company 248ms

And Mark custom fields as not obligatory 009ms

And Login as "piast-admin" 5s 912ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 970ms

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

And Show all transport types 1s 121ms

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

And Set advice window in schedule 3s 220ms

And Fill advice form 10s 577ms

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

And Go to "TRANSPORT_TABLE" 448ms

And Find transport in table with status "advice-added" 3s 714ms

And Confirm statuses until reach "left-the-area" 32s 444ms

Then Check if next status is not possible to confirm 331ms

Hooks

After Hooks.deleteTransportAfterTest() 944ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 399ms

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

And Get custom field settings for "DELIVERY" transport type and "piast" company 239ms

And Mark custom fields as not obligatory 009ms

And Login as "piast-admin" 5s 669ms

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

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

And Show all transport types 1s 154ms

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

And Set advice window in schedule 3s 340ms

And Fill advice form 10s 310ms

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

And Go to "TRANSPORT_TABLE" 459ms

And Find transport in table with status "advice-added" 3s 697ms

When Add file to transport by API 2s 006ms

And Confirm statuses until reach "process-ended" 37s 485ms

Then Check if transport has "process-ended" 076ms

Hooks

After Hooks.deleteTransportAfterTest() 963ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 815ms

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

And Get custom field settings for "LOAD" transport type and "piast" company 251ms

And Mark custom fields as not obligatory 009ms

And Login as "piast-admin" 5s 919ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 946ms

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

And Show all transport types 1s 155ms

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

And Set advice window in schedule 3s 357ms

And Fill advice form 10s 673ms

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

And Go to "TRANSPORT_TABLE" 446ms

And Find transport in table with status "advice-added" 3s 719ms

When Add file to transport by API 1s 521ms

And Confirm statuses until reach "process-ended" 37s 539ms

Then Check if transport has "process-ended" 077ms

Hooks

After Hooks.deleteTransportAfterTest() 874ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 166ms

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

And Get custom field settings for "TRANSFER_BETWEEN_WAREHOUSES" transport type and "hochland" company 241ms

And Mark custom fields as not obligatory 007ms

And Set custom field "Magazynier (R)" with "EDIT_TRANSFER_BETWEEN_WAREHOUSES_WAREHOUSEMAN_U_CFD" in "TRANSFER_BETWEEN_WAREHOUSES" - "hochland" by "super-admin-hochland" 502ms

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

And Set "advice" inputs from JSON file "ADVICE_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 001ms

And Login as "hochland-admin" 9s 740ms

And Show all transport types 1s 165ms

And Click button advice in transport table "TRANSFER_BETWEEN_WAREHOUSES" 1s 255ms

And Set advice window in schedule 7s 512ms

And Fill advice form 16s 530ms

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

And Go to "TRANSPORT_TABLE" 465ms

And Find transport in table with status "advice-added" 3s 658ms

And Confirm statuses until reach "during-load" 11s 518ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 588ms

And Check if next status is not possible to confirm in status confirmation modal 293ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 022ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 026ms

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

And Mark custom fields as not obligatory 006ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_LOAD_SANITARY_CONDITIONS_CFD" in "LOAD" - "keeeper" by "super-admin-keeeper" 207ms

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

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper" 002ms

And Login as "keeeper-admin" 5s 942ms

And Show all transport types 1s 156ms

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

And Set advice window in schedule 3s 263ms

And Fill advice form 16s 373ms

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

And Go to "TRANSPORT_TABLE" 442ms

And Find transport in table with status "advice-added" 3s 671ms

And Confirm statuses until reach "arrived" 6s 254ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 569ms

And Check if next status is not possible to confirm in status confirmation modal 265ms

Hooks

After Hooks.deleteTransportAfterTest() 896ms

After Hooks.rollbackAllCustomFieldsSettings() 759ms

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

And Get custom field settings for "CONTAINER" transport type and "keeeper" company 128ms

And Mark custom fields as not obligatory 006ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_CONTAINER_SANITARY_CONDITIONS_CFD" in "CONTAINER" - "keeeper" by "super-admin-keeeper" 244ms

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

And Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-keeeper" 002ms

And Login as "keeeper-admin" 5s 825ms

And Show all transport types 1s 144ms

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

And Set advice window in schedule 3s 161ms

And Fill advice form 16s 486ms

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

And Go to "TRANSPORT_TABLE" 459ms

And Find transport in table with status "advice-added" 3s 638ms

And Confirm statuses until reach "arrived" 6s 253ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 550ms

And Check if next status is not possible to confirm in status confirmation modal 272ms

Hooks

After Hooks.deleteTransportAfterTest() 840ms

After Hooks.rollbackAllCustomFieldsSettings() 773ms

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

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 133ms

And Mark custom fields as not obligatory 006ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 234ms

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

And Login as "keeeper-admin" 6s 405ms

And Go to "TRANSPORT_TABLE" 410ms

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

And Confirm statuses until reach "arrived" 6s 275ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 567ms

And Check if next status is not possible to confirm in status confirmation modal 282ms

Hooks

After Hooks.deleteTransportAfterTest() 964ms

After Hooks.rollbackAllCustomFieldsSettings() 493ms

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

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 119ms

And Mark custom fields as not obligatory 007ms

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

And Login as "keeeper-admin" 5s 605ms

And Go to "TRANSPORT_TABLE" 427ms

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

And Confirm statuses until reach "arrived" 6s 221ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 592ms

And Check if next status is not possible to confirm in status confirmation modal 262ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 066ms

After Hooks.rollbackAllCustomFieldsSettings() 626ms

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

And Mark custom fields as not obligatory 006ms

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 1s 183ms

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

And Login as "hochland-admin" 9s 420ms

And Go to "TRANSPORT_TABLE" 503ms

And Find transport in table with status "advice-added" 3s 700ms

And Confirm statuses until reach "during-unload" 11s 536ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 655ms

And Check if next status is not possible to confirm in status confirmation modal 254ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 186ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 931ms

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

And Get custom field settings for "LOAD" transport type and "keeeper" company 126ms

And Mark custom fields as not obligatory 007ms

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper" 001ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_LOAD_SANITARY_CONDITIONS_CFD" in "LOAD" - "keeeper" by "super-admin-keeeper" 214ms

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

And Login as "keeeper-admin" 5s 771ms

And Show all transport types 1s 254ms

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

And Set advice window in schedule 3s 284ms

And Fill advice form 16s 504ms

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

And Go to "TRANSPORT_TABLE" 468ms

And Find transport in table with status "advice-added" 3s 670ms

When Confirm statuses until reach "arrived" 6s 242ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 560ms

And Check if next status is not possible to confirm in status confirmation modal 252ms

And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper" 001ms

And Click cancel in status confirmation modal 15s 393ms

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

And Open section: "advice-panel" 1s 173ms

And Fill transport form 28s 737ms

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

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

And Open section: "advice-panel" 1s 153ms

And Fill "meeting-sanitary-and-technical-conditions" in transport form 17s 335ms

And Confirm statuses until reach "process-ended" 16s 692ms

Then Check if transport has "process-ended" 065ms

Hooks

After Hooks.deleteTransportAfterTest() 869ms

After Hooks.rollbackAllCustomFieldsSettings() 722ms

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

And Get custom field settings for "CONTAINER" transport type and "keeeper" company 121ms

And Mark custom fields as not obligatory 008ms

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

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

And Login as "keeeper-admin" 6s 244ms

And Show all transport types 1s 161ms

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

And Set advice window in schedule 3s 226ms

And Fill advice form 16s 385ms

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

And Go to "TRANSPORT_TABLE" 464ms

And Find transport in table with status "advice-added" 3s 669ms

When Confirm statuses until reach "arrived" 6s 245ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 555ms

And Check if next status is not possible to confirm in status confirmation modal 272ms

And Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-keeeper" 001ms

And Click cancel in status confirmation modal 15s 412ms

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

And Open section: "advice-panel" 1s 167ms

And Fill transport form 28s 676ms

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

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

And Open section: "advice-panel" 1s 170ms

And Fill "meeting-sanitary-and-technical-conditions" in transport form 17s 309ms

And Confirm statuses until reach "process-ended" 16s 667ms

Then Check if transport has "process-ended" 070ms

Hooks

After Hooks.deleteTransportAfterTest() 888ms

After Hooks.rollbackAllCustomFieldsSettings() 770ms

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

And Get custom field settings for "TRANSFER_BETWEEN_WAREHOUSES" transport type and "hochland" company 232ms

And Mark custom fields as not obligatory 008ms

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

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

And Login as "hochland-admin" 10s 215ms

And Show all transport types 1s 162ms

And Click button advice in transport table "TRANSFER_BETWEEN_WAREHOUSES" 1s 086ms

And Set advice window in schedule 7s 517ms

And Fill advice form 16s 343ms

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

And Go to "TRANSPORT_TABLE" 447ms

And Find transport in table with status "advice-added" 3s 630ms

When Confirm statuses until reach "during-load" 11s 510ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 596ms

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

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 3s 004ms

And Open section: "advice-panel" 1s 176ms

And Fill transport form 39s 948ms

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

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

And Open section: "advice-panel" 1s 369ms

And Fill "warehouseman-(u)" in transport form 18s 027ms

And Confirm statuses until reach "process-ended" 32s 340ms

Then Check if transport has "process-ended" 063ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 220ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 057ms

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

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 111ms

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

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

And Login as "keeeper-admin" 6s 096ms

And Go to "TRANSPORT_TABLE" 435ms

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

When Confirm statuses until reach "arrived" 6s 255ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 593ms

And Check if next status is not possible to confirm in status confirmation modal 283ms

And Click cancel in status confirmation modal 15s 339ms

And Go to transport details "UNLOAD" 2s 893ms

And Fill transport form 40s 872ms

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

And Confirm statuses until reach "process-ended" 16s 645ms

Then Check if transport has "process-ended" 074ms

Hooks

After Hooks.deleteTransportAfterTest() 987ms

After Hooks.rollbackAllCustomFieldsSettings() 492ms

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

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 132ms

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

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

And Login as "keeeper-admin" 5s 882ms

And Go to "TRANSPORT_TABLE" 426ms

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

When Confirm statuses until reach "arrived" 6s 235ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 597ms

And Check if next status is not possible to confirm in status confirmation modal 281ms

And Click cancel in status confirmation modal 15s 430ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 888ms

And Fill transport form 40s 993ms

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

And Confirm statuses until reach "process-ended" 16s 733ms

Then Check if transport has "process-ended" 064ms

Hooks

After Hooks.deleteTransportAfterTest() 871ms

After Hooks.rollbackAllCustomFieldsSettings() 583ms

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

And Get custom field settings for "DELIVERY" transport type and "hochland" company 186ms

And Mark custom fields as not obligatory 020ms

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

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

And Login as "hochland-admin" 10s 291ms

And Go to "TRANSPORT_TABLE" 488ms

And Find transport in table with status "advice-added" 3s 700ms

When Confirm statuses until reach "during-unload" 11s 447ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 626ms

And Check if next status is not possible to confirm in status confirmation modal 251ms

And Click cancel in status confirmation modal 15s 529ms

And Go to transport details "DELIVERY" 3s 004ms

And Fill transport form 40s 680ms

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

And Confirm statuses until reach "process-ended" 11s 501ms

Then Check if transport has "process-ended" 057ms

Hooks

After Hooks.deleteTransportAfterTest() 892ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 927ms

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

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

And Confirm status "REPORTING" by Public API "v1" 469ms

And Confirm status "ARRIVAL" by Public API "v1" 703ms

And Login as "swiss-krono-delivery-guard" 5s 296ms

And Go to "TRANSPORT_TABLE" 546ms

When Confirm "Departure" status in transport row 190ms

Then Verify that "Departure" has been confirmed 1s 390ms

Hooks

After Hooks.deleteTransportAfterTest() 842ms

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

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 111ms

And Mark custom fields as not obligatory 004ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 16s 789ms

When Login as "keeeper-admin" 5s 828ms

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

And Confirm statuses until reach "arrived" 6s 264ms

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

And Click cancel in status confirmation modal 15s 431ms

And Go to transport details "UNLOAD" 2s 877ms

And Fill transport form 40s 899ms

Then Check if confirm status modal appeared on confirming next status in transport "details" 281ms

And Check if next status is not possible to confirm in status confirmation modal 229ms

Hooks

After Hooks.deleteTransportAfterTest() 884ms

After Hooks.rollbackAllCustomFieldsSettings() 512ms

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

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 117ms

And Mark custom fields as not obligatory 007ms

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

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 3s 073ms

When Login as "keeeper-admin" 5s 298ms

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

And Confirm statuses until reach "arrived" 6s 264ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 557ms

And Check if next status is not possible to confirm in status confirmation modal 282ms

And Click cancel in status confirmation modal 15s 409ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 947ms

And Fill transport form 40s 666ms

Then Check if confirm status modal appeared on confirming next status in transport "details" 280ms

And Check if next status is not possible to confirm in status confirmation modal 262ms

Hooks

After Hooks.deleteTransportAfterTest() 886ms

After Hooks.rollbackAllCustomFieldsSettings() 611ms

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

And Get custom field settings for "DELIVERY" transport type and "hochland" company 205ms

And Mark custom fields as not obligatory 007ms

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

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

When Login as "hochland-admin" 10s 050ms

And Find transport in table with status "advice-added" 3s 746ms

And Confirm statuses until reach "during-unload" 11s 530ms

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

And Click cancel in status confirmation modal 15s 808ms

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

And Fill transport form 40s 713ms

Then Check if confirm status modal appeared on confirming next status in transport "details" 309ms

And Check if next status is not possible to confirm in status confirmation modal 270ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 028ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 917ms

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

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 170ms

And Mark custom fields as not obligatory 007ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 771ms

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

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" 4s 621ms

And Login as "bausch-admin" 5s 813ms

And Go to "TRANSPORT_TABLE" 514ms

And Find transport in table with status "advice-added" 3s 692ms

And Confirm statuses until reach "on-the-way" 16s 815ms

When Open statuses popup 152ms

And Toggle status date confirmation checkbox 388ms

And Confirm statuses until reach "process-ended" 6s 217ms

Then Check if transport has "process-ended" 057ms

Hooks

After Hooks.deleteTransportAfterTest() 996ms

After Hooks.rollbackAllCustomFieldsSettings() 1s 887ms

After Hooks.deleteModeOfTransportationAfterTest() 352ms

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

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 186ms

And Mark custom fields as not obligatory 005ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 767ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 181ms

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

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" 4s 307ms

And Login as "bausch-admin" 6s 075ms

And Go to "TRANSPORT_TABLE" 496ms

And Find transport in table with status "advice-added" 3s 717ms

And Confirm statuses until reach "on-the-way" 15s 681ms

And Open statuses popup 150ms

And Toggle status date confirmation checkbox 385ms

And Change status execution date to "1" days from today 2s 487ms

Then Verify that status cannot be confirmed 1s 223ms

Hooks

After Hooks.deleteTransportAfterTest() 930ms

After Hooks.rollbackAllCustomFieldsSettings() 1s 817ms

After Hooks.deleteModeOfTransportationAfterTest() 329ms

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

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 182ms

And Mark custom fields as not obligatory 009ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 760ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 233ms

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

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" 4s 663ms

And Login as "bausch-admin" 5s 894ms

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

And Open statuses popup 155ms

And Toggle status date confirmation checkbox 394ms

And Change status execution date to "-1" days from today 2s 447ms

Then Verify that status cannot be confirmed 1s 170ms

Hooks

After Hooks.deleteTransportAfterTest() 998ms

After Hooks.rollbackAllCustomFieldsSettings() 1s 764ms

After Hooks.deleteModeOfTransportationAfterTest() 330ms

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

And Get custom field settings for "EXTERNAL_DELIVERY" transport type and "farmacol" company 108ms

And Mark custom fields as not obligatory 005ms

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

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 4s 166ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 112ms

When Login as "farmacol-admin" 7s 410ms

And Go to "TRANSPORT_TABLE" 458ms

And Confirm statuses until reach "during-unload" 16s 846ms

And Set actual confirmed transport status list 2s 079ms

And Disable task by API 203ms

And Go to transport details "EXTERNAL_DELIVERY" 2s 902ms

And Edit transport hours and recalculate statuses 19s 088ms

Then Verify that all confirmed statuses are still on transport status list 434ms

Hooks

After Hooks.deleteTransportAfterTest() 903ms

After Hooks.rollbackAllCustomFieldsSettings() 352ms

After Hooks.rollbackTaskChanges() 208ms

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

And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 396ms

And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 4s 758ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 943ms

And Check if reject date is not visible 15s 062ms

When Reject status: Book of disinfection 15s 033ms

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.ZaXtAd}, 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: 9275f62421ea78059964e579c60af950
*** 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() 873ms

After Hooks.cleanUserDetailsAfterTest() 986ms

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" 4s 960ms

And Create transport "CREATE_LOAD_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 2s 924ms

And Check if reject date is not visible 15s 079ms

When Reject status: Book of disinfection 200ms

And Check if reject date is visible 699ms

And Get rejection date 089ms

And Wait "60" seconds 1m

And Reject status: Book of disinfection 179ms

Then Check if reject date has changed 1s 224ms

Hooks

After Hooks.deleteTransportAfterTest() 983ms

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 881ms

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

And Check if reject date is not visible 15s 083ms

When Reject status: Book of disinfection 184ms

Then Check if reject date is visible 581ms

Hooks

After Hooks.deleteTransportAfterTest() 898ms

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 901ms

And Open statuses popup 211ms

And Check if reject date is not visible 15s 062ms

When Reject status: Book of disinfection 205ms

Then Open statuses popup 150ms

And Check if reject date is visible 449ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 014ms

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" 10s 261ms

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

And Confirm to the last status by API 1s 320ms

When Find statuses for transport in table 3s 144ms

And Revoke statuses until reach "advice-added" 8s 049ms

Then Check if transport has "advice-added" 068ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 003ms

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

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

And Confirm to the last status by API 1s 403ms

When Find statuses for transport in table 2s 515ms

And Revoke statuses until reach "planned" 8s 068ms

Then Check if transport has "planned" 074ms

Hooks

After Hooks.deleteTransportAfterTest() 838ms

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

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 987ms

When Find transport in table with status "new" 3s 707ms

And Open statuses popup 209ms

Then Check if transport has checkpoints from list "Utworzenie zlecenia,Dodanie awizacji,Potwierdzenie okna czasowego" in "0" 153ms

Hooks

After Hooks.deleteTransportAfterTest() 734ms

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

And Get inputs from database "ADVICE_EXTERNAL_DELIVERY" "super-admin-farmacol" 017ms

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

And Click button advice in transport table "EXTERNAL_DELIVERY" 267ms

And Set advice window in schedule 3s 555ms

And Fill advice form 14s 594ms

And Click advice save button and wait for advice form to disappear 33s 821ms

And Go to "TRANSPORT_TABLE" 493ms

When Find transport in table with status "advice-added" 3s 695ms

And Open statuses popup 207ms

Then Check if transport has checkpoints from list "Zgłoszenie kierowcy,Rozpoczęcie rozładunku,Zakończenie rozładunku" in "1" 169ms

Hooks

After Hooks.deleteTransportAfterTest() 987ms

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" 233ms

And Get custom field settings for "EXTERNAL_DELIVERY" transport type and "farmacol" company 106ms

And Mark custom fields as not obligatory 006ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 933ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 3s 835ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 121ms

When Login as "farmacol-admin" 2s 267ms

And Go to "TRANSPORT_TABLE" 517ms

And Confirm statuses until reach "registered-katowice-przyjęcia" 11s 540ms

And Disable task by API 191ms

And Find transport pencil button in transports table 1s 877ms

And Click pencil and move transport to next day in schedule 22s 883ms

And Go to "TRANSPORT_TABLE" 487ms

Then Verify that "START_OF_UNLOADING" is not visible 351ms

Hooks

After Hooks.deleteTransportAfterTest() 985ms

After Hooks.rollbackAllCustomFieldsSettings() 345ms

After Hooks.rollbackTaskChanges() 190ms

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" 3s 053ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 215ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 297ms

When Go to "WAREHOUSE_TAB" 1s 239ms

And Select warehouse "Serownia" 1s 620ms

And Set week view 1s 245ms

And Show yesterday 1s 151ms

And Move window into the past 447ms

Then Check if window is "red" 4s 062ms

Hooks

After Hooks.deleteTransportAfterTest() 875ms

After Hooks.rollbackAddedAuthorities() 190ms

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 201ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 936ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "lantmannen-admin" 186ms

When Go to "WAREHOUSE_TAB" 1s 188ms

And Select warehouse "Magazyn - Nowa Sól" 2s 648ms

And Set week view 1s 275ms

And Show yesterday 1s 173ms

And Move window into the past 605ms

Then Check if window is "red" 4s 067ms

Hooks

After Hooks.deleteTransportAfterTest() 917ms

After Hooks.rollbackAddedAuthorities() 132ms

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 557ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 015ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "piast-admin" 190ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 020ms

When Show all transport types 1s 153ms

And Click button advice in transport table "DELIVERY" 258ms

And Set advice window in schedule 3s 371ms

And Fill advice form 10s 536ms

And Click advice save button and wait for advice form to disappear 33s 395ms

And Select warehouse "Magazyn Hala A" 1s 414ms

And Set week view 2s 236ms

And Show yesterday 1s 208ms

And Move window into the past 962ms

Then Check if window is "red" 4s 085ms

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() 879ms

After Hooks.rollbackAddedAuthorities() 134ms

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 153ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 022ms

And Set algorithm setting for "super-admin-hochland" in "Magazyn Zimny Kaźmierz" on "Magazyn Zimny" 1s 203ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 3s 167ms

When Go to "WAREHOUSE_TAB" 1s 122ms

And Select warehouse "Magazyn Zimny Kaźmierz" 1s 956ms

And Set week view 1s 275ms

And Check if time window length is correct after "CREATE" 084ms

And Change number of pallets in transport 59s 981ms

And Click "save-transport-and-close" save button and wait for form to disappear 20s 418ms

And Check if time window length is correct after "EDIT" 077ms

Hooks

After Hooks.deleteTransportAfterTest() 988ms

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 795ms

And Get package type settings for transportType "UNLOAD" from "keeeper" 150ms

And Set package type "PALLETS" settings with values: "defaultValue;required", "4;true" 231ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 668ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 982ms

When Go to "WAREHOUSE_TAB" 725ms

And Select warehouse "Magazyn Surowców" 1s 384ms

And Set week view 1s 249ms

Then Check if time window has proper "60" 066ms

Hooks

After Hooks.deleteTransportAfterTest() 893ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 139ms

After Hooks.clearAlgorithmSettings() 606ms

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 891ms

And Get package type settings for transportType "UNLOAD" from "keeeper" 126ms

And Set package type "PALLETS" settings with values: "defaultValue;required", "4;false" 202ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 625ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 970ms

When Go to "WAREHOUSE_TAB" 721ms

And Select warehouse "Magazyn Surowców" 1s 374ms

And Set week view 1s 244ms

Then Check if time window has proper "60" 069ms

Hooks

After Hooks.deleteTransportAfterTest() 887ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 130ms

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 860ms

And Get package type settings for transportType "LOAD" from "keeeper" 125ms

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" 620ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 905ms

And Get inputs from database "ADVICE_LOAD" "super-admin-keeeper" 020ms

And Show all transport types 1s 152ms

And Click button advice in transport table "LOAD" 264ms

And Set advice window in schedule 3s 245ms

And Fill advice form 16s 351ms

And Click advice save button and wait for advice form to disappear 33s 318ms

Then Check if time window has proper "30" 086ms

Hooks

After Hooks.deleteTransportAfterTest() 957ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 130ms

After Hooks.clearAlgorithmSettings() 541ms

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 975ms

And Get package type settings for transportType "CONTAINER" from "keeeper" 108ms

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" 591ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 933ms

And Get inputs from database "ADVICE_CONTAINER" "super-admin-keeeper" 021ms

And Show all transport types 1s 169ms

And Click button advice in transport table "CONTAINER" 268ms

And Set advice window in schedule 3s 233ms

And Fill advice form 16s 448ms

And Click advice save button and wait for advice form to disappear 33s 311ms

Then Check if time window has proper "60" 077ms

Hooks

After Hooks.deleteTransportAfterTest() 980ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 122ms

After Hooks.clearAlgorithmSettings() 550ms

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" 253ms

And Set algorithm setting for "super-admin-hochland" in "Serownia" on "Magazyn Sera" 809ms

And Set token of apiUsername "dha1-supplier-2@qa.qa-test" 211ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 16s 985ms

And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "super-admin-hochland" 7s 547ms

When Go to transport details "DELIVERY" 30s 869ms

And Change filled value in transport details "number-of-pallets-step-0" "number" "25" "0" 1s 548ms

And Click "save-transport-and-close" save button and wait for form to disappear 19s 300ms

And Go to "WAREHOUSE_TAB" 1s 169ms

And Select warehouse "Serownia" 1s 645ms

And Set week view 1s 254ms

Then Check if time window has proper "60" 082ms

Hooks

After Hooks.deleteTransportAfterTest() 981ms

After Hooks.clearAlgorithmSettings() 937ms

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 047ms

And Set basic authorities "ROLE_ACCESS_TO_NUMBER_OF_WINDOWS" to user "keeeper-admin" 132ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 881ms

When Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 52s 959ms

And Check if time window counter value equals "1" 207ms

And Select view "DAYS_2" 2s 162ms

And Move advice window "2" 1s 514ms

And Select view "DAY" 2s 153ms

Then Check if time window counter value equals "0" 168ms

And Delete created transport by API 826ms

And Check if time window counter value equals "0" 151ms

And Click in free spot in schedule page to create gray window 509ms

And Check if time window counter value equals "0" 145ms

And Click in free spot in schedule page to create dedicated window 2s 126ms

And Check if time window counter value equals "0" 188ms

Hooks

After Hooks.deleteTransportAfterTest() 784ms

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" 019ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 554ms

When Go to new transport "DELIVERY" 685ms

And Fill transport form 13s 538ms

And Click "save-transport" save button and wait for form to disappear 15s 782ms

And Set advice window in schedule 2s 384ms

And Check is transport created in schedule and set transport id 2s 489ms

And Go to "TRANSPORT_TABLE" 488ms

When Click on time window date 1s 675ms

And Open transport form when in schedule 1s 278ms

Then Check are transport values equals 464ms

Hooks

After Hooks.deleteTransportAfterTest() 825ms

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 938ms

When Go to new transport "DELIVERY" 705ms

And Fill transport form 44s 159ms

And Click "save-transport" save button and wait for form to disappear 15s 766ms

And Set advice window in schedule 2s 375ms

And Check is transport created in schedule and set transport id 2s 924ms

And Go to "TRANSPORT_TABLE" 457ms

When Click on time window date 1s 604ms

And Open transport form when in schedule 1s 361ms

Then Check are transport values equals 20s 078ms

Hooks

After Hooks.deleteTransportAfterTest() 972ms

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" 019ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 082ms

When Go to new transport "CISTERN_DELIVERY" 735ms

And Fill transport form 46s 215ms

And Click "save-transport" save button and wait for form to disappear 15s 756ms

And Set advice window in schedule 2s 425ms

And Check is transport created in schedule and set transport id 2s 488ms

And Go to "TRANSPORT_TABLE" 427ms

When Click on time window date 2s 818ms

And Open transport form when in schedule 1s 395ms

Then Check are transport values equals 7s 203ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 086ms

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 149ms

When Go to new transport "CISTERN_COLLECTION" 669ms

And Fill transport form 32s 060ms

And Click "save-transport" save button and wait for form to disappear 15s 748ms

And Set advice window in schedule 2s 441ms

And Check is transport created in schedule and set transport id 2s 431ms

And Go to "TRANSPORT_TABLE" 491ms

When Click on time window date 2s 879ms

And Open transport form when in schedule 1s 358ms

Then Check are transport values equals 22s 065ms

Hooks

After Hooks.deleteTransportAfterTest() 854ms

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" 018ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 5s 066ms

When Go to new transport "DELIVERY" 691ms

And Fill transport form 42s 835ms

And Click "save-transport" save button and wait for form to disappear 15s 722ms

And Set advice window in schedule 2s 372ms

And Check is transport created in schedule and set transport id 2s 647ms

And Go to "TRANSPORT_TABLE" 443ms

When Click on time window date 1s 732ms

And Open transport form when in schedule 1s 306ms

Then Check are transport values equals 19s 922ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 064ms

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 519ms

When Go to new transport "LOAD" 652ms

And Fill transport form 42s 668ms

And Click "save-transport" save button and wait for form to disappear 15s 734ms

And Set advice window in schedule 2s 397ms

And Check is transport created in schedule and set transport id 2s 609ms

And Go to "TRANSPORT_TABLE" 505ms

When Click on time window date 1s 779ms

And Open transport form when in schedule 1s 316ms

Then Check are transport values equals 19s 962ms

Hooks

After Hooks.deleteTransportAfterTest() 987ms

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" 348ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 356ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 328ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 319ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 916ms

And Login as "farmacol-admin" 6s 812ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 37s 334ms

And Go to "TRANSPORT_TABLE" 562ms

When Go to transport details "EXTERNAL_DELIVERY" 2s 848ms

And Add step "unload" 199ms

And Change filled value in transport details "warehouse-select-step-2" "select" "Mory Przyjęcia" "0" 3s 833ms

And Change filled value in transport details "weight-step-2" "number" "23" "0" 1s 575ms

And Change filled value in transport details "number-of-pallets-step-2" "number" "23" "0" 1s 567ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 761ms

Then Click "save-transport" save button 331ms

And Set advice window in schedule in "2" days 5s 591ms

And Click advice save button and wait for advice form to disappear 35s 501ms

And Go to "TRANSPORT_TABLE" 498ms

And Check if transport has "2" time windows 042ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 238ms

After Hooks.rollbackTransportTypeSettings() 300ms

After Hooks.rollbackAddedActionAuthorities() 303ms

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" 226ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 166ms

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 095ms

And Set double window advice 000ms

And Login as "farmacol-admin" 6s 983ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 57s 923ms

And Go to "TRANSPORT_TABLE" 558ms

And Get checkpoint colors for transport 032ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "true" 39s 038ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 228ms

After Hooks.rollbackTransportTypeSettings() 311ms

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" 231ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 156ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 298ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 2s 062ms

And Set double window advice 000ms

And Login as "farmacol-admin" 2s 632ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 58s 039ms

And Go to "TRANSPORT_TABLE" 553ms

And Get checkpoint colors for transport 023ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "false" 39s 159ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 155ms

After Hooks.rollbackTransportTypeSettings() 313ms

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" 236ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 165ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 264ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 2s 062ms

And Set double window advice 000ms

And Login as "farmacol-admin" 2s 594ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 57s 790ms

And Get checkpoint colors for transport 018ms

And Go to "TRANSPORT_TABLE" 592ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true" 9s 470ms

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 184ms

After Hooks.rollbackTransportTypeSettings() 343ms

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" 241ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 152ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 294ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 15s 903ms

And Set double window advice 000ms

And Login as "farmacol-admin" 2s 572ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 57s 994ms

And Get checkpoint colors for transport 018ms

And Go to "TRANSPORT_TABLE" 538ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "false" 29s 999ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 172ms

After Hooks.rollbackTransportTypeSettings() 298ms

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" 240ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 993ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 3s 768ms

And Login as "super-admin-farmacol" 7s 699ms

And Show all transport types 1s 162ms

And Click on time window date 2s 026ms

Then Open transport form when in schedule 1s 407ms

And Click create similar button 15s 241ms

And Click cancel button in transport form 234ms

And Open transport form when in schedule 1s 387ms

Then Check if transport form modal is visible 099ms

Hooks

After Hooks.deleteTransportAfterTest() 920ms

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" 242ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 937ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 3s 823ms

And Get min and max advice date of created transport as "super-admin-farmacol" 440ms

And Login as "farmacol-admin" 2s 598ms

And Show all transport types 1s 162ms

And Click on time window date 2s 035ms

And Set week view 2s 629ms

And Move advice window "3" 1s 879ms

Then Check if min and max advice date changed after moving advice window as "super-admin-farmacol" 699ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 224ms

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 301ms

And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 018ms

And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 127ms

And Set proper delay time to move order to archive after task timeout 137ms

When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 1s 969ms

And Go to "WAREHOUSE_TAB" 987ms

And Change warehouse in schedule to: "Katowice" 1s 547ms

And Wait "60" seconds 1m

And Verify that transport window is grey 086ms

And Verify that transport is in archive 10s 760ms

Then Restore transport from archive 2s 633ms

And Verify that transport has been successfully restored 15s 655ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 016ms

After Hooks.rollbackSettings() 122ms

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 883ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 136ms

When Go to "TRANSPORT_TABLE" 421ms

And Delete transport 19s 459ms

When Go to "ARCHIVE_TAB" 567ms

And Show "OWN_COLLECTION" 177ms

And Verify that created transport is "true" in transport table 15s 147ms

Hooks

After Hooks.deleteTransportAfterTest() 765ms

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" 232ms

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 099ms

And Mark custom fields as not obligatory 005ms

And Login as "dayco-admin" 2s 166ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 075ms

And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 128ms

And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 030ms

When Go to "TRANSPORT_TABLE" 413ms

And Click button advice in transport table "OWN_COLLECTION" 1s 384ms

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 45s 588ms

And Go to "TRANSPORT_TABLE" 429ms

And Find transport in table with status "planned-magazyn-tychy" 3s 671ms

And Confirm statuses until reach "process-ended" 16s 710ms

And Wait "12" seconds 12s

Then Go to "ARCHIVE_TAB" 506ms

And Show "OWN_COLLECTION" 160ms

And Verify that created transport is "true" in transport table 1m 32s 320ms

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() 1s 059ms

After Hooks.rollbackAllCustomFieldsSettings() 459ms

After Hooks.rollbackSettings() 134ms

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" 4s 990ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 079ms

When Fill auction form 16s 138ms

Then Verify that the auction has been added to transport 170ms

Hooks

After Hooks.deleteTransportAfterTest() 683ms

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 954ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 110ms

When Fill auction form 16s 282ms

Then Verify that the auction has been added to transport 157ms

Hooks

After Hooks.deleteTransportAfterTest() 693ms

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 095ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 822ms

When If user is login then logout 234ms

And Login as "paa1-carrier@qa.qa-test" 5s 043ms

And Go to auction offer 1s 597ms

And Accept transport with minimum rate 17s 008ms

Then Check if carrier is assigned to transport 071ms

Hooks

After Hooks.deleteTransportAfterTest() 786ms

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 451ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 127ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 849ms

When If user is login then logout 233ms

And Login as "paa1-carrier@qa.qa-test" 2s 517ms

And Go to auction offer 1s 608ms

And Reject auction offer 15s 807ms

Then Verify that offer has been removed from transport 15s 067ms

Hooks

After Hooks.deleteTransportAfterTest() 851ms

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 795ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 112ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 834ms

When If user is login then logout 235ms

And Login as "pskza1-carrier@qa.qa-test" 6s 651ms

And Go to auction offer 2s 393ms

And Reject auction offer 15s 771ms

Then Verify that offer has been removed from transport 15s 079ms

Hooks

After Hooks.deleteTransportAfterTest() 852ms

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 481ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 089ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 821ms

When If user is login then logout 266ms

And Login as "paa1-carrier@qa.qa-test" 2s 410ms

And Go to auction offer 1s 607ms

And Offer prize above maximum - "20000" 387ms

Then Verify that is not possible to add offer 837ms

Hooks

After Hooks.deleteTransportAfterTest() 741ms

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 380ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 120ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 792ms

When If user is login then logout 269ms

And Login as "pskza1-carrier@qa.qa-test" 2s 422ms

And Go to auction offer 2s 417ms

And Offer prize above maximum - "20000" 392ms

Then Verify that is not possible to add offer 846ms

Hooks

After Hooks.deleteTransportAfterTest() 731ms

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 327ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 135ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 817ms

And Wait till auction end 1m 58s 016ms

Then Verify that is possible to add auction 151ms

Hooks

After Hooks.deleteTransportAfterTest() 797ms

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 550ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 153ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 825ms

And Wait till auction end 1m 58s 015ms

Then Verify that is possible to add auction 155ms

Hooks

After Hooks.deleteTransportAfterTest() 809ms

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 735ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 467ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 838ms

And Go to auction offer 1s 543ms

When Offer "1000" 357ms

Then Verify that offer with "1000" has been added to auction 3s 095ms

Hooks

After Hooks.deleteTransportAfterTest() 748ms

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 516ms

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 792ms

And Go to auction offer 1s 545ms

When Offer "1000" 369ms

Then Verify that offer with "1000" has been added to auction 3s 082ms

Hooks

After Hooks.deleteTransportAfterTest() 755ms

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 537ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 302ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 826ms

And Go to auction offer 1s 506ms

When Offer "1000" 338ms

And Verify that offer with "1000" has been added to auction 3s 075ms

Then Go to auction offer 1s 515ms

And Revoke current offer 720ms

And Verify that offer has been revoked 33s 041ms

Hooks

After Hooks.deleteTransportAfterTest() 743ms

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 663ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 290ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 813ms

And Go to auction offer 1s 551ms

When Offer "1000" 372ms

And Verify that offer with "1000" has been added to auction 3s 091ms

Then Go to auction offer 1s 525ms

And Offer "1500" 362ms

And Verify that offer with "1500" has been added to auction 3s 080ms

Hooks

After Hooks.deleteTransportAfterTest() 710ms

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 455ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 283ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 789ms

And Go to auction offer 1s 543ms

When Offer "1000" 383ms

And Verify that offer with "1000" has been added to auction 3s 090ms

Then Login as "swisskrono-admin" 2s 296ms

And Go to auction details 2s 162ms

And Finish active auction 136ms

And Verify that the transport has no active auction 667ms

Hooks

After Hooks.deleteTransportAfterTest() 777ms

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 429ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 191ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 816ms

And Go to auction offer 1s 556ms

When Offer "1000" 360ms

Then Verify that carrier can see current place in auction depending on the "true" role 862ms

Hooks

After Hooks.deleteTransportAfterTest() 789ms

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 546ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 263ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 806ms

And Go to auction offer 1s 543ms

When Offer "1000" 353ms

Then Verify that carrier can see current place in auction depending on the "false" role 15s 036ms

Hooks

After Hooks.deleteTransportAfterTest() 744ms

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 627ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 263ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 773ms

And Go to auction offer 1s 496ms

When Offer "300" 359ms

And Verify that carrier can't add offer to auction 093ms

Hooks

After Hooks.deleteTransportAfterTest() 734ms

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 361ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 067ms

And Show all transport "false" 076ms

When Go to auction form 1s 588ms

Then Verify carrier selection value "false" 152ms

Hooks

After Hooks.deleteTransportAfterTest() 685ms

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 358ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 266ms

And Show all transport "true" 248ms

When Go to auction form 1s 564ms

Then Verify carrier selection value "true" 145ms

Hooks

After Hooks.deleteTransportAfterTest() 678ms

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 165ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 088ms

When Open transport auction form 448ms

And Select all companies checkbox in transport auction form 163ms

And Unselect company "PAA2" in transport auction form 194ms

And Put transport on auction 15s 476ms

And Open transport auction history 217ms

And Open participants section in transport auction history 152ms

Then Check if unselected "PAA2" is in transport auction history as participant 15s 065ms

Hooks

After Hooks.deleteTransportAfterTest() 776ms

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 620ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 083ms

When Open transport auction form 485ms

And Select all companies checkbox in transport auction form 139ms

And Unselect company "PSKZA2" in transport auction form 132ms

And Put transport on auction 15s 449ms

And Open transport auction history 216ms

And Open participants section in transport auction history 151ms

Then Check if unselected "PSKZA2" is in transport auction history as participant 15s 032ms

Hooks

After Hooks.deleteTransportAfterTest() 801ms

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" 210ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-varrocrychvald" 2s 346ms

And Set transport on auction with "1000" and "1500" by JSON file as "super-admin-varrocrychvald" 2s 737ms

And Add a bid "1500" to an auction by JSON file as "pvra1-carrier" for "super-admin-varrocrychvald" 889ms

And Add a bid "1000" to an auction by JSON file as "pvra2-carrier-2" for "super-admin-varrocrychvald" 971ms

When Login as "varrocrychvald-admin" and set token of apiUsername "super-admin-varrocrychvald" 5s 003ms

And Show all transport "true" 257ms

And Open transport auction history 1s 076ms

And Pass transport to "2" carrier in auction history 1s 197ms

Then Verify if "REASON" is visible in pass transport modal 092ms

And Confirm pass transport to carrier in pass transport modal 160ms

And Verify that "REASON" in pass transport modal has validation error 1s 075ms

Hooks

After Hooks.deleteTransportAfterTest() 741ms

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 042ms

When Go to new transport "UNLOAD" 15s 483ms

And Fill transport form 28s 290ms

And Click "save-transport" save button and wait for form to disappear 15s 780ms

And Set advice window in schedule 2s 436ms

And Check is transport created in schedule and set transport id 2s 647ms

And Go to "TRANSPORT_TABLE" 454ms

And Go to transport details "UNLOAD" 30s 689ms

Then Check are transport values equals 22s 143ms

Hooks

After Hooks.deleteTransportAfterTest() 849ms

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 568ms

When Go to new transport "DELIVERY" 638ms

And Fill transport form 13s 314ms

And Click "save-transport" save button and wait for form to disappear 15s 769ms

And Set advice window in schedule 2s 413ms

And Check is transport created in schedule and set transport id 2s 562ms

And Go to "TRANSPORT_TABLE" 516ms

And Go to transport details "DELIVERY" 2s 756ms

Then Check are transport values equals 423ms

Hooks

After Hooks.deleteTransportAfterTest() 840ms

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 421ms

When Go to new transport "OWN_COLLECTION" 659ms

And Fill transport form 20s 643ms

And Click "save-transport" save button and wait for form to disappear 15s 683ms

And Set advice window in schedule 2s 395ms

And Check is transport created in schedule and set transport id 2s 515ms

And Go to "TRANSPORT_TABLE" 385ms

And Go to transport details "OWN_COLLECTION" 2s 744ms

Then Check are transport values equals 517ms

Hooks

After Hooks.deleteTransportAfterTest() 920ms

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 217ms

When Go to new transport "DELIVERY" 709ms

And Fill transport form 44s 063ms

And Click "save-transport" save button and wait for form to disappear 15s 751ms

And Set advice window in schedule 2s 380ms

And Check is transport created in schedule and set transport id 2s 937ms

And Go to "TRANSPORT_TABLE" 533ms

And Go to transport details "DELIVERY" 2s 869ms

Then Check are transport values equals 20s 200ms

Hooks

After Hooks.deleteTransportAfterTest() 966ms

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" 020ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 041ms

When Go to new transport "CISTERN_DELIVERY" 738ms

And Fill transport form 46s 227ms

And Click "save-transport" save button and wait for form to disappear 15s 774ms

And Set advice window in schedule 2s 428ms

And Check is transport created in schedule and set transport id 2s 679ms

And Go to "TRANSPORT_TABLE" 468ms

And Go to transport details "CISTERN_DELIVERY" 2s 803ms

Then Check are transport values equals 7s 133ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 030ms

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" 020ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 910ms

When Go to new transport "CISTERN_COLLECTION" 656ms

And Fill transport form 32s 123ms

And Click "save-transport" save button and wait for form to disappear 15s 733ms

And Set advice window in schedule 2s 437ms

And Check is transport created in schedule and set transport id 2s 399ms

And Go to "TRANSPORT_TABLE" 451ms

And Go to transport details "CISTERN_COLLECTION" 3s 018ms

Then Check are transport values equals 21s 975ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 028ms

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" 3s 038ms

When Go to new transport "OWN_COLLECTION" 670ms

And Fill transport form 36s 926ms

And Click "save-transport" save button and wait for form to disappear 15s 788ms

And Set advice window in schedule 2s 377ms

And Check is transport created in schedule and set transport id 2s 931ms

And Go to "TRANSPORT_TABLE" 461ms

And Go to transport details "OWN_COLLECTION" 2s 796ms

Then Check are transport values equals 19s 990ms

Hooks

After Hooks.deleteTransportAfterTest() 853ms

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" 019ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 051ms

When Go to new transport "OWN_COLLECTION_POWDER_FACTORY" 691ms

And Fill transport form 37s 138ms

And Click "save-transport" save button and wait for form to disappear 15s 728ms

And Set advice window in schedule 2s 398ms

And Check is transport created in schedule and set transport id 2s 646ms

And Go to "TRANSPORT_TABLE" 463ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 3s 461ms

Then Check are transport values equals 4s 979ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 064ms

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" 022ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 918ms

When Go to new transport "EXPORT" 755ms

And Fill transport form 45s 528ms

And Click "save-transport" save button and wait for form to disappear 15s 759ms

And Set advice window in schedule 2s 368ms

And Check is transport created in schedule and set transport id 2s 995ms

And Go to "TRANSPORT_TABLE" 474ms

And Go to transport details "EXPORT" 2s 957ms

Then Check are transport values equals 321ms

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 249ms

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" 020ms

And Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 5s 253ms

When Go to new transport "DELIVERY" 15s 426ms

And Fill transport form 31s 998ms

And Click "save-transport" save button and wait for form to disappear 15s 762ms

And Set advice window in schedule 2s 377ms

And Check is transport created in schedule and set transport id 2s 498ms

And Go to "TRANSPORT_TABLE" 515ms

And Go to transport details "DELIVERY" 30s 578ms

Then Check are transport values equals 36s 897ms

Hooks

After Hooks.deleteTransportAfterTest() 888ms

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" 021ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 5s 113ms

When Go to new transport "DELIVERY" 699ms

And Fill transport form 42s 893ms

And Click "save-transport" save button and wait for form to disappear 15s 784ms

And Set advice window in schedule 2s 392ms

And Check is transport created in schedule and set transport id 2s 633ms

And Go to "TRANSPORT_TABLE" 472ms

And Go to transport details "DELIVERY" 2s 757ms

Then Check are transport values equals 19s 989ms

Hooks

After Hooks.deleteTransportAfterTest() 921ms

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" 018ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 535ms

When Go to new transport "LOAD" 669ms

And Fill transport form 42s 888ms

And Click "save-transport" save button and wait for form to disappear 15s 759ms

And Set advice window in schedule 2s 378ms

And Check is transport created in schedule and set transport id 2s 659ms

And Go to "TRANSPORT_TABLE" 490ms

And Go to transport details "LOAD" 2s 790ms

Then Check are transport values equals 19s 979ms

Hooks

After Hooks.deleteTransportAfterTest() 969ms

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" 021ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 6s 058ms

When Go to new transport "UNLOAD" 669ms

And Fill transport form 42s 559ms

And Click "save-transport" save button and wait for form to disappear 758ms

And Set advice window in schedule 2s 530ms

And Check is transport created in schedule and set transport id 2s 785ms

And Go to "TRANSPORT_TABLE" 481ms

And Go to transport details "UNLOAD" 2s 811ms

Then Check are transport values equals 22s 227ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 031ms

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" 019ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 540ms

When Go to new transport "TANKER_GRANULATE_DELIVERY" 652ms

And Fill transport form 42s 366ms

And Click "save-transport" save button and wait for form to disappear 808ms

And Set advice window in schedule 2s 585ms

And Check is transport created in schedule and set transport id 2s 714ms

And Go to "TRANSPORT_TABLE" 435ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 779ms

Then Check are transport values equals 22s 264ms

Hooks

After Hooks.deleteTransportAfterTest() 837ms

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" 023ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 554ms

When Go to new transport "DELIVERY" 669ms

And Fill transport form 26s 296ms

And Click "save-transport" save button and wait for form to disappear 15s 699ms

And Set advice window in schedule 2s 387ms

And Check is transport created in schedule and set transport id 2s 525ms

And Go to "TRANSPORT_TABLE" 477ms

And Go to transport details "DELIVERY" 2s 766ms

Then Check are transport values equals 17s 667ms

Hooks

After Hooks.deleteTransportAfterTest() 865ms

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" 016ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 914ms

When Go to new transport "WEIGHING" 652ms

And Fill transport form 15s 780ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 907ms

And Show all transport "false" 072ms

And Go to "TRANSPORT_TABLE" 447ms

And Go to transport details "WEIGHING" 2s 930ms

And Check are transport values equals 2s 520ms

Hooks

After Hooks.deleteTransportAfterTest() 908ms

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 502ms

When Go to new transport "TRANSPORT" 717ms

And Fill transport form 29s 090ms

And Click "save-transport-and-close" save button and wait for form to disappear 1s 431ms

And Show all transport "false" 073ms

And Go to "TRANSPORT_TABLE" 426ms

And Go to transport details "TRANSPORT" 2s 863ms

And Check are transport values equals 6s 692ms

Hooks

After Hooks.deleteTransportAfterTest() 817ms

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 595ms

When Go to new transport "CONTAINER" 663ms

And Fill transport form 12s 087ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 357ms

And Show all transport "false" 070ms

And Go to "TRANSPORT_TABLE" 327ms

And Go to transport details "CONTAINER" 2s 698ms

And Check are transport values equals 162ms

Hooks

After Hooks.deleteTransportAfterTest() 786ms

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" 020ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 861ms

When Go to new transport "TRANSFER_BETWEEN_WAREHOUSES" 706ms

And Fill transport form 14s 403ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 336ms

And Show all transport "false" 075ms

And Go to "TRANSPORT_TABLE" 429ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 906ms

And Check are transport values equals 4s 701ms

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_DELIVERY" "super-admin-piast" 020ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 272ms

When Go to new transport "DELIVERY" 649ms

And Fill transport form 24s 681ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 376ms

And Show all transport "false" 074ms

And Go to "TRANSPORT_TABLE" 433ms

And Go to transport details "DELIVERY" 2s 888ms

And Check are transport values equals 17s 490ms

Hooks

After Hooks.deleteTransportAfterTest() 754ms

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" 020ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 483ms

When Go to new transport "LOAD" 642ms

And Fill transport form 28s 537ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 403ms

And Show all transport "false" 084ms

And Go to "TRANSPORT_TABLE" 419ms

And Go to transport details "LOAD" 2s 944ms

And Check are transport values equals 2s 691ms

Hooks

After Hooks.deleteTransportAfterTest() 702ms

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 469ms

When Go to new transport "LOAD" 623ms

And Fill transport form 27s 175ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 387ms

And Show all transport "false" 074ms

And Go to "TRANSPORT_TABLE" 437ms

And Go to transport details "LOAD" 2s 812ms

And Check are transport values equals 19s 542ms

Hooks

After Hooks.deleteTransportAfterTest() 683ms

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" 018ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 485ms

When Go to new transport "CONTAINER" 601ms

And Fill transport form 27s 224ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 377ms

And Show all transport "false" 070ms

And Go to "TRANSPORT_TABLE" 422ms

And Go to transport details "CONTAINER" 2s 838ms

And Check are transport values equals 19s 659ms

Hooks

After Hooks.deleteTransportAfterTest() 606ms

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" 019ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 903ms

When Go to new transport "SMALLS_IMPORT" 696ms

And Fill transport form 40s 280ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 935ms

And Show all transport "false" 074ms

And Go to "TRANSPORT_TABLE" 434ms

And Go to transport details "SMALLS_IMPORT" 2s 925ms

And Check are transport values equals 11s 147ms

Hooks

After Hooks.deleteTransportAfterTest() 683ms

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" 020ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 661ms

When Go to new transport "SMALLS_EXPORT" 725ms

And Fill transport form 40s 177ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 968ms

And Show all transport "false" 073ms

And Go to "TRANSPORT_TABLE" 424ms

And Go to transport details "SMALLS_EXPORT" 2s 805ms

And Check are transport values equals 11s 155ms

Hooks

After Hooks.deleteTransportAfterTest() 722ms

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" 019ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 504ms

When Go to new transport "TRANSPORT_ORDER" 721ms

And Fill transport form 33s 267ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 941ms

And Show all transport "true" 260ms

And Go to "TRANSPORT_TABLE" 410ms

And Go to transport details "TRANSPORT_ORDER" 2s 871ms

And Check are transport values equals 19s 907ms

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_TRANSPORT_ORDER_WITHOUT_WAREHOUSES" "super-admin-adama" 019ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 460ms

When Go to new transport "TRANSPORT" 729ms

And Fill transport form 40s 900ms

And Click "save-transport-and-close" save button and wait for form to disappear 1s 433ms

And Show all transport "false" 071ms

And Go to "TRANSPORT_TABLE" 430ms

And Go to transport details "TRANSPORT" 2s 903ms

And Check are transport values equals 4s 701ms

Hooks

After Hooks.deleteTransportAfterTest() 734ms

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" 020ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 399ms

When Go to new transport "INBOUND" 655ms

And Fill transport form 43s 608ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 932ms

And Show all transport "true" 239ms

And Go to "TRANSPORT_TABLE" 370ms

And Go to transport details "INBOUND" 2s 782ms

And Check are transport values equals 2s 842ms

Hooks

After Hooks.deleteTransportAfterTest() 760ms

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" 021ms

And Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 7s 528ms

When Go to new transport "EXTERNAL_DELIVERY" 674ms

And Fill transport form 59s 821ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 435ms

And Show all transport "false" 072ms

And Go to "TRANSPORT_TABLE" 398ms

And Go to transport details "EXTERNAL_DELIVERY" 2s 821ms

And Check are transport values equals 5s 504ms

Hooks

After Hooks.deleteTransportAfterTest() 782ms

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" 020ms

And Login as "dfa1-supplier" and set token of apiUsername "dfa1-supplier" 6s 801ms

When Go to new transport "EXTERNAL_DELIVERY" 15s 491ms

And Fill transport form 52s 915ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 325ms

And Show all transport "false" 070ms

And Go to "TRANSPORT_TABLE" 424ms

And Go to transport details "EXTERNAL_DELIVERY" 2s 911ms

And Check are transport values equals 5s 346ms

Hooks

After Hooks.deleteTransportAfterTest() 715ms

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 511ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 022ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 17s 752ms

And Show all transport "false" 080ms

When Go to transport details "UNLOAD" 30s 804ms

And Fill transport form 33s 848ms

And Click "save-transport-and-close" save button and wait for form to disappear 19s 251ms

And Go to transport details "UNLOAD" 30s 696ms

Then Check are transport values equals 4s 873ms

Hooks

After Hooks.deleteTransportAfterTest() 922ms

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 593ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 021ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 122ms

And Show all transport "false" 074ms

When Go to transport details "TRANSPORT" 2s 847ms

And Fill transport form 11s 275ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 863ms

And Go to transport details "TRANSPORT" 2s 866ms

Then Check are transport values equals 4s 367ms

Hooks

After Hooks.deleteTransportAfterTest() 665ms

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 455ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 018ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 885ms

And Show all transport "false" 078ms

When Go to transport details "CONTAINER" 2s 830ms

And Fill transport form 5s 159ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 927ms

And Go to transport details "CONTAINER" 2s 776ms

Then Check are transport values equals 122ms

Hooks

After Hooks.deleteTransportAfterTest() 668ms

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 360ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 021ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 670ms

And Show all transport "false" 076ms

When Go to transport details "DELIVERY" 2s 808ms

And Fill transport form 13s 625ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 532ms

And Go to transport details "DELIVERY" 2s 785ms

Then Check are transport values equals 457ms

Hooks

After Hooks.deleteTransportAfterTest() 753ms

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 450ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-adama" 018ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-adama" 2s 815ms

And Show all transport "false" 078ms

When Go to transport details "OWN_COLLECTION" 2s 846ms

And Fill transport form 24s 400ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 490ms

And Go to transport details "OWN_COLLECTION" 2s 744ms

Then Check are transport values equals 2s 667ms

Hooks

After Hooks.deleteTransportAfterTest() 935ms

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 908ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 023ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 179ms

And Show all transport "false" 078ms

When Go to transport details "DELIVERY" 2s 927ms

And Fill transport form 40s 666ms

And Click "save-transport-and-close" save button and wait for form to disappear 18s 061ms

And Go to transport details "DELIVERY" 2s 844ms

Then Check are transport values equals 11s 528ms

Hooks

After Hooks.deleteTransportAfterTest() 902ms

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 888ms

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" 2s 964ms

And Show all transport "false" 079ms

When Go to transport details "OWN_COLLECTION" 2s 987ms

And Fill transport form 41s 102ms

And Click "save-transport-and-close" save button and wait for form to disappear 2s 608ms

And Go to transport details "OWN_COLLECTION" 2s 900ms

Then Check are transport values equals 6s 929ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 015ms

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 948ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 020ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 3s 070ms

And Show all transport "false" 082ms

When Go to transport details "EXPORT" 3s 046ms

And Fill transport form 53s 854ms

And Click "save-transport-and-close" save button and wait for form to disappear 18s 070ms

And Go to transport details "EXPORT" 2s 925ms

Then Check are transport values equals 9s 387ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 013ms

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_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 021ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 916ms

And Show all transport "false" 077ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 885ms

And Fill transport form 39s 796ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 519ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 830ms

Then Check are transport values equals 13s 334ms

Hooks

After Hooks.deleteTransportAfterTest() 728ms

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 938ms

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 732ms

And Show all transport "false" 071ms

When Go to transport details "CISTERN_DELIVERY" 2s 873ms

And Fill transport form 30s 576ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 493ms

And Go to transport details "CISTERN_DELIVERY" 2s 748ms

Then Check are transport values equals 6s 862ms

Hooks

After Hooks.deleteTransportAfterTest() 899ms

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 058ms

And Get inputs from database "EDIT_CISTERN_COLLECTION" "super-admin-hochland" 020ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 2s 629ms

And Show all transport "false" 073ms

When Go to transport details "CISTERN_COLLECTION" 2s 896ms

And Fill transport form 28s 897ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 529ms

And Go to transport details "CISTERN_COLLECTION" 2s 830ms

Then Check are transport values equals 6s 834ms

Hooks

After Hooks.deleteTransportAfterTest() 917ms

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 129ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 021ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 2s 129ms

And Show all transport "false" 080ms

When Go to transport details "WEIGHING" 2s 863ms

And Fill transport form 14s 222ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 942ms

And Go to transport details "WEIGHING" 2s 786ms

Then Check are transport values equals 2s 144ms

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() 646ms

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 671ms

And Get inputs from database "EDIT_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 021ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 2s 602ms

And Show all transport "false" 079ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 2s 976ms

And Fill transport form 39s 489ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 553ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 2s 923ms

Then Check are transport values equals 7s 062ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 004ms

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 479ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 021ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 16s 674ms

And Show all transport "false" 072ms

When Go to transport details "DELIVERY" 30s 707ms

And Fill transport form 28s 534ms

And Click "save-transport-and-close" save button and wait for form to disappear 1s 995ms

And Go to transport details "DELIVERY" 30s 659ms

Then Check are transport values equals 2s 623ms

Hooks

After Hooks.deleteTransportAfterTest() 902ms

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 643ms

And Get inputs from database "EDIT_LOAD" "super-admin-piast" 022ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 970ms

And Show all transport "false" 073ms

When Go to transport details "LOAD" 2s 945ms

And Fill transport form 1m 3s 052ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 548ms

And Go to transport details "LOAD" 2s 890ms

Then Check are transport values equals 26s 327ms

Hooks

After Hooks.deleteTransportAfterTest() 813ms

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 496ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 928ms

And Show all transport "false" 074ms

When Go to transport details "DELIVERY" 2s 784ms

And Fill transport form 17s 972ms

And Click "save-transport-and-close" save button and wait for form to disappear 1s 992ms

And Go to transport details "DELIVERY" 2s 717ms

Then Check are transport values equals 239ms

Hooks

After Hooks.deleteTransportAfterTest() 942ms

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 365ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 020ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 931ms

And Show all transport "false" 078ms

When Go to transport details "LOAD" 2s 809ms

And Fill transport form 31s 814ms

And Click "save-transport-and-close" save button and wait for form to disappear 19s 209ms

And Go to transport details "LOAD" 2s 773ms

Then Check are transport values equals 2s 739ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 036ms

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 585ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 947ms

And Show all transport "false" 076ms

When Go to transport details "UNLOAD" 2s 939ms

And Fill transport form 42s 466ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 485ms

And Go to transport details "UNLOAD" 2s 822ms

Then Check are transport values equals 7s 122ms

Hooks

After Hooks.deleteTransportAfterTest() 851ms

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 527ms

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 035ms

And Show all transport "false" 086ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 882ms

And Fill transport form 40s 918ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 495ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 818ms

Then Check are transport values equals 7s 074ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 022ms

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 569ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 021ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 923ms

And Show all transport "false" 078ms

When Go to transport details "LOAD" 2s 789ms

And Fill transport form 28s 768ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 835ms

And Go to transport details "LOAD" 2s 792ms

Then Check are transport values equals 4s 660ms

Hooks

After Hooks.deleteTransportAfterTest() 651ms

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 475ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 020ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 917ms

And Show all transport "false" 076ms

When Go to transport details "CONTAINER" 2s 829ms

And Fill transport form 28s 747ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 899ms

And Go to transport details "CONTAINER" 2s 739ms

Then Check are transport values equals 4s 711ms

Hooks

After Hooks.deleteTransportAfterTest() 737ms

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 694ms

And Get inputs from database "EDIT_SMALLS_EXPORT" "super-admin-skz" 022ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 141ms

And Show all transport "false" 073ms

When Go to transport details "SMALLS_EXPORT" 2s 826ms

And Fill transport form 36s 239ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 888ms

And Go to transport details "SMALLS_EXPORT" 2s 822ms

Then Check are transport values equals 8s 980ms

Hooks

After Hooks.deleteTransportAfterTest() 698ms

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 562ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 2s 813ms

And Show all transport "true" 242ms

When Go to transport details "DELIVERY" 2s 863ms

And Fill transport form 22s 444ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 441ms

And Go to transport details "DELIVERY" 2s 786ms

Then Check are transport values equals 527ms

Hooks

After Hooks.deleteTransportAfterTest() 884ms

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 409ms

And Get inputs from database "EDIT_TRANSPORT_ORDER" "super-admin-alrec" 020ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 217ms

And Show all transport "true" 248ms

When Go to transport details "TRANSPORT_ORDER" 2s 860ms

And Fill transport form 29s 487ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 938ms

And Go to transport details "TRANSPORT_ORDER" 2s 884ms

Then Check are transport values equals 2s 753ms

Hooks

After Hooks.deleteTransportAfterTest() 664ms

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 624ms

And Get inputs from database "EDIT_CONTAINER_WAREHOUSEMAN_CUSTOMFIELDS" "super-admin-keeeper" 020ms

And Create transport "CREATE_CONTAINER_KEEEPER_WAIMEA" by JSON file as "super-admin-keeeper" 1s 886ms

And Show all transport "false" 076ms

When Go to transport details "CONTAINER" 2s 785ms

And Fill transport form 11s 360ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 938ms

And Go to transport details "CONTAINER" 2s 745ms

Then Check are transport values equals 112ms

Error message

org.openqa.selenium.StaleElementReferenceException: stale element reference: element is not attached to the page document
  (Session info: headless chrome=91.0.4472.114)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/stale_element_reference.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.ZaXtAd}, 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: 9275f62421ea78059964e579c60af950
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	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.RemoteWebElement.execute(RemoteWebElement.java:279)
	at org.openqa.selenium.remote.RemoteWebElement.getAttribute(RemoteWebElement.java:128)
	at CucumberTests.Transport.Transport.checkAreValuesEquals(Transport.java:120)
	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() 617ms

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 961ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 174ms

And Show all transport "false" 080ms

When Delete transport 21s 382ms

Then Transport not displayed in table of transports 15s 103ms

Hooks

After Hooks.deleteTransportAfterTest() 915ms

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 500ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 880ms

And Show all transport "false" 078ms

When Delete transport 20s 873ms

Then Transport not displayed in table of transports 15s 119ms

Hooks

After Hooks.deleteTransportAfterTest() 761ms

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 433ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 941ms

And Show all transport "false" 076ms

When Delete transport 20s 707ms

Then Transport not displayed in table of transports 15s 116ms

Hooks

After Hooks.deleteTransportAfterTest() 11s 725ms

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 532ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 957ms

And Show all transport "false" 079ms

When Delete transport 18s 343ms

Then Transport not displayed in table of transports 15s 119ms

Hooks

After Hooks.deleteTransportAfterTest() 747ms

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 668ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 115ms

And Show all transport "false" 081ms

When Delete transport 18s 431ms

Then Transport not displayed in table of transports 15s 084ms

Hooks

After Hooks.deleteTransportAfterTest() 872ms

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 744ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 133ms

And Show all transport "false" 080ms

When Delete transport 19s 055ms

Then Transport not displayed in table of transports 15s 092ms

Hooks

After Hooks.deleteTransportAfterTest() 861ms

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 430ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 2s 814ms

And Show all transport "true" 245ms

When Delete transport 19s 554ms

Then Transport not displayed in table of transports 15s 067ms

Hooks

After Hooks.deleteTransportAfterTest() 799ms

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 578ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 213ms

And Show all transport "true" 239ms

When Delete transport 19s 605ms

Then Transport not displayed in table of transports 15s 115ms

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 "pgf-admin" and set token of apiUsername "super-admin-pgf" 2s 355ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 020ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 17s 736ms

And Show all transport "false" 072ms

When Go to transport details "UNLOAD" 30s 804ms

And Fill transport form 33s 797ms

And Click "save-transport" save button 4s 278ms

And Click cancel button in transport form 177ms

And Go to transport details "UNLOAD" 30s 754ms

Then Check are transport values equals 4s 816ms

Hooks

After Hooks.deleteTransportAfterTest() 849ms

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 312ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 019ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 016ms

And Show all transport "false" 066ms

When Go to transport details "TRANSPORT" 2s 967ms

And Fill transport form 11s 252ms

And Click "save-transport" save button 2s 053ms

And Click cancel button in transport form 170ms

And Go to transport details "TRANSPORT" 2s 835ms

Then Check are transport values equals 4s 383ms

Hooks

After Hooks.deleteTransportAfterTest() 621ms

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_CONTAINER" "super-admin-adama" 019ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 979ms

And Show all transport "false" 077ms

When Go to transport details "CONTAINER" 2s 761ms

And Fill transport form 5s 166ms

And Click "save-transport" save button 2s 054ms

And Click cancel button in transport form 167ms

And Go to transport details "CONTAINER" 2s 773ms

Then Check are transport values equals 148ms

Hooks

After Hooks.deleteTransportAfterTest() 648ms

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 411ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 793ms

And Show all transport "false" 076ms

When Go to transport details "DELIVERY" 2s 820ms

And Fill transport form 13s 386ms

And Click "save-transport" save button 2s 628ms

And Click cancel button in transport form 182ms

And Go to transport details "DELIVERY" 2s 739ms

Then Check are transport values equals 470ms

Hooks

After Hooks.deleteTransportAfterTest() 857ms

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 436ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-adama" 020ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-adama" 2s 812ms

And Show all transport "false" 075ms

When Go to transport details "OWN_COLLECTION" 2s 827ms

And Fill transport form 24s 537ms

And Click "save-transport" save button 2s 601ms

And Click cancel button in transport form 186ms

And Go to transport details "OWN_COLLECTION" 2s 744ms

Then Check are transport values equals 2s 640ms

Hooks

After Hooks.deleteTransportAfterTest() 839ms

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 899ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 022ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 068ms

And Show all transport "false" 074ms

When Go to transport details "DELIVERY" 2s 874ms

And Fill transport form 40s 752ms

And Click "save-transport" save button 3s 226ms

And Click cancel button in transport form 183ms

And Go to transport details "DELIVERY" 2s 788ms

Then Check are transport values equals 11s 465ms

Hooks

After Hooks.deleteTransportAfterTest() 946ms

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 077ms

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" 3s 005ms

And Show all transport "false" 076ms

When Go to transport details "OWN_COLLECTION" 2s 892ms

And Fill transport form 41s 075ms

And Click "save-transport" save button 2s 787ms

And Click cancel button in transport form 180ms

And Go to transport details "OWN_COLLECTION" 2s 802ms

Then Check are transport values equals 6s 989ms

Hooks

After Hooks.deleteTransportAfterTest() 985ms

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 915ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 020ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 3s 158ms

And Show all transport "false" 080ms

When Go to transport details "EXPORT" 3s 034ms

And Fill transport form 53s 729ms

And Click "save-transport" save button 2s 723ms

And Click cancel button in transport form 233ms

And Go to transport details "EXPORT" 2s 823ms

Then Check are transport values equals 9s 453ms

Hooks

After Hooks.deleteTransportAfterTest() 971ms

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 956ms

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 949ms

And Show all transport "false" 075ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 875ms

And Fill transport form 39s 714ms

And Click "save-transport" save button 2s 624ms

And Click cancel button in transport form 193ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 774ms

Then Check are transport values equals 13s 396ms

Hooks

After Hooks.deleteTransportAfterTest() 677ms

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 261ms

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 771ms

And Show all transport "false" 075ms

When Go to transport details "CISTERN_DELIVERY" 2s 881ms

And Fill transport form 30s 476ms

And Click "save-transport" save button 2s 618ms

And Click cancel button in transport form 194ms

And Go to transport details "CISTERN_DELIVERY" 2s 783ms

Then Check are transport values equals 6s 864ms

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 "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 001ms

And Get inputs from database "EDIT_CISTERN_COLLECTION" "super-admin-hochland" 019ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 2s 681ms

And Show all transport "false" 072ms

When Go to transport details "CISTERN_COLLECTION" 2s 845ms

And Fill transport form 28s 828ms

And Click "save-transport" save button 2s 615ms

And Click cancel button in transport form 191ms

And Go to transport details "CISTERN_COLLECTION" 2s 802ms

Then Check are transport values equals 6s 822ms

Hooks

After Hooks.deleteTransportAfterTest() 992ms

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 939ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 022ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 2s 197ms

And Show all transport "false" 081ms

When Go to transport details "WEIGHING" 2s 860ms

And Fill transport form 14s 163ms

And Click "save-transport" save button 2s 017ms

And Click cancel button in transport form 174ms

And Go to transport details "WEIGHING" 2s 742ms

Then Check are transport values equals 2s 168ms

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() 670ms

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 929ms

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 797ms

And Show all transport "false" 076ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 3s 002ms

And Fill transport form 39s 327ms

And Click "save-transport" save button 2s 693ms

And Click cancel button in transport form 178ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 2s 843ms

Then Check are transport values equals 7s 005ms

Hooks

After Hooks.deleteTransportAfterTest() 967ms

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 574ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 16s 579ms

And Show all transport "false" 072ms

When Go to transport details "DELIVERY" 30s 748ms

And Fill transport form 28s 345ms

And Click "save-transport" save button 2s 038ms

And Click cancel button in transport form 179ms

And Go to transport details "DELIVERY" 30s 573ms

Then Check are transport values equals 2s 596ms

Hooks

After Hooks.deleteTransportAfterTest() 826ms

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 590ms

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 978ms

And Show all transport "false" 078ms

When Go to transport details "LOAD" 2s 924ms

And Fill transport form 1m 2s 826ms

And Click "save-transport" save button 2s 788ms

And Click cancel button in transport form 158ms

And Go to transport details "LOAD" 2s 753ms

Then Check are transport values equals 26s 348ms

Hooks

After Hooks.deleteTransportAfterTest() 836ms

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 533ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 858ms

And Show all transport "false" 081ms

When Go to transport details "DELIVERY" 2s 825ms

And Fill transport form 18s 076ms

And Click "save-transport" save button 2s 638ms

And Click cancel button in transport form 194ms

And Go to transport details "DELIVERY" 2s 704ms

Then Check are transport values equals 196ms

Hooks

After Hooks.deleteTransportAfterTest() 911ms

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 295ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 020ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 952ms

And Show all transport "false" 076ms

When Go to transport details "LOAD" 2s 797ms

And Fill transport form 31s 790ms

And Click "save-transport" save button 4s 296ms

And Click cancel button in transport form 171ms

And Go to transport details "LOAD" 2s 871ms

Then Check are transport values equals 2s 712ms

Hooks

After Hooks.deleteTransportAfterTest() 924ms

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_DELIVERY" "super-admin-keeeper" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 941ms

And Show all transport "false" 065ms

When Go to transport details "UNLOAD" 2s 871ms

And Fill transport form 42s 470ms

And Click "save-transport" save button 2s 640ms

And Click cancel button in transport form 201ms

And Go to transport details "UNLOAD" 2s 785ms

Then Check are transport values equals 7s 176ms

Hooks

After Hooks.deleteTransportAfterTest() 938ms

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 364ms

And Get inputs from database "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 020ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 856ms

And Show all transport "false" 071ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 861ms

And Fill transport form 40s 847ms

And Click "save-transport" save button 2s 612ms

And Click cancel button in transport form 177ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 776ms

Then Check are transport values equals 7s 016ms

Hooks

After Hooks.deleteTransportAfterTest() 886ms

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 343ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 020ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 876ms

And Show all transport "false" 080ms

When Go to transport details "LOAD" 2s 827ms

And Fill transport form 28s 738ms

And Click "save-transport" save button 2s 078ms

And Click cancel button in transport form 170ms

And Go to transport details "LOAD" 2s 707ms

Then Check are transport values equals 4s 675ms

Hooks

After Hooks.deleteTransportAfterTest() 689ms

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 463ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 020ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 954ms

And Show all transport "false" 080ms

When Go to transport details "CONTAINER" 2s 782ms

And Fill transport form 28s 777ms

And Click "save-transport" save button 2s 086ms

And Click cancel button in transport form 184ms

And Go to transport details "CONTAINER" 2s 702ms

Then Check are transport values equals 4s 674ms

Hooks

After Hooks.deleteTransportAfterTest() 618ms

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 710ms

And Get inputs from database "EDIT_SMALLS_IMPORT" "super-admin-skz" 021ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 137ms

And Show all transport "false" 078ms

When Go to transport details "SMALLS_IMPORT" 2s 917ms

And Fill transport form 36s 255ms

And Click "save-transport" save button 2s 088ms

And Click cancel button in transport form 188ms

And Go to transport details "SMALLS_IMPORT" 2s 747ms

Then Check are transport values equals 9s 005ms

Hooks

After Hooks.deleteTransportAfterTest() 689ms

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 546ms

And Get inputs from database "EDIT_SMALLS_EXPORT" "super-admin-skz" 024ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 171ms

And Show all transport "false" 078ms

When Go to transport details "SMALLS_EXPORT" 2s 847ms

And Fill transport form 36s 200ms

And Click "save-transport" save button 2s 080ms

And Click cancel button in transport form 193ms

And Go to transport details "SMALLS_EXPORT" 2s 775ms

Then Check are transport values equals 8s 998ms

Hooks

After Hooks.deleteTransportAfterTest() 692ms

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 736ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 2s 788ms

And Show all transport "true" 272ms

When Go to transport details "DELIVERY" 2s 792ms

And Fill transport form 22s 618ms

And Click "save-transport" save button 2s 568ms

And Click cancel button in transport form 176ms

And Go to transport details "DELIVERY" 2s 790ms

Then Check are transport values equals 536ms

Hooks

After Hooks.deleteTransportAfterTest() 884ms

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 452ms

And Get inputs from database "EDIT_TRANSPORT_ORDER" "super-admin-alrec" 020ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 189ms

And Show all transport "true" 245ms

When Go to transport details "TRANSPORT_ORDER" 2s 851ms

And Fill transport form 29s 628ms

And Click "save-transport" save button 2s 075ms

And Click cancel button in transport form 188ms

And Go to transport details "TRANSPORT_ORDER" 2s 784ms

Then Check are transport values equals 2s 750ms

Hooks

After Hooks.deleteTransportAfterTest() 650ms

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 563ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 939ms

And Create gray windows "CREATE_GRAY_WINDOW_MWG" on "PRZESYŁKI DROBNICOWE" in "Magazyn Wyrobów Gotowych" as "super-admin-keeeper" 1s 207ms

And If user is login then logout 277ms

Then Login as "dka1-supplier" 5s 902ms

And Click button advice in transport table "LOAD" 734ms

And Check if moved to first possible start date in schedule 1s 161ms

Hooks

After Hooks.deleteTransportAfterTest() 618ms

After Hooks.deleteAllGrayWindowsAfterTest() 1m 31s 963ms

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" 258ms

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 594ms

Then Go to new transport "LOAD" 728ms

And Fill transport form 25s 974ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 371ms

And Go to "COMPANIES_TAB" 966ms

And Go to company "Dostawca Piast Automat 1" details 572ms

And Check if new address with "Adresat" is visible in company details 322ms

And Go to "TRANSPORT_TABLE" 448ms

And Go to transport details "LOAD" 2s 879ms

Hooks

After Hooks.deleteTransportAfterTest() 943ms

After Hooks.deleteAddressAfterTest() 122ms

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 574ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 058ms

When Go to "TRANSPORT_TABLE" 408ms

And Show all transport types 1s 150ms

And Verify that transport has "0" files 089ms

Then Add file to transport by API 1s 629ms

And Verify that transport has "1" files 2s 572ms

Hooks

After Hooks.deleteTransportAfterTest() 707ms

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 946ms

When Go to "TRANSPORT_TABLE" 419ms

And Show all transport types 1s 159ms

And Verify that transport has "0" files 087ms

Then Add file to transport by API 1s 335ms

And Verify that transport has "1" files 301ms

Hooks

After Hooks.deleteTransportAfterTest() 621ms

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 803ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 176ms

When Go to "TRANSPORT_TABLE" 414ms

And Show all transport types 1s 130ms

And Verify that transport has "0" files 094ms

Then Add file to transport by API 1s 718ms

And Verify that transport has "1" files 3s 166ms

Hooks

After Hooks.deleteTransportAfterTest() 992ms

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 355ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 902ms

When Go to "TRANSPORT_TABLE" 419ms

And Show all transport types 1s 163ms

And Verify that transport has "0" files 083ms

Then Add file to transport by API 1s 433ms

And Verify that transport has "1" files 361ms

Hooks

After Hooks.deleteTransportAfterTest() 554ms

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 412ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 974ms

And Delete transport 17s 913ms

When Go to "ARCHIVE_TAB" 560ms

And Show "DELIVERY" 150ms

And Verify that transport has "0" files 6s 933ms

Then Add file to transport 409ms

And Verify that transport has "1" files 1s 819ms

Hooks

After Hooks.deleteTransportAfterTest() 738ms

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 551ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 937ms

And Delete transport 19s 679ms

When Go to "ARCHIVE_TAB" 529ms

And Show "LOAD" 202ms

And Verify that transport has "0" files 6s 108ms

Then Add file to transport 415ms

And Verify that transport has "1" files 1s 910ms

Hooks

After Hooks.deleteTransportAfterTest() 729ms

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 906ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 153ms

And Delete transport 21s 349ms

When Go to "ARCHIVE_TAB" 564ms

And Show "DELIVERY" 140ms

And Verify that transport has "0" files 6s 727ms

Then Add file to transport 417ms

And Verify that transport has "1" files 2s 039ms

Hooks

After Hooks.deleteTransportAfterTest() 891ms

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 434ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 896ms

And Delete transport 18s 348ms

When Go to "ARCHIVE_TAB" 536ms

And Show "CONTAINER" 202ms

And Verify that transport has "0" files 4s 387ms

Then Add file to transport 421ms

And Verify that transport has "1" files 1s 751ms

Hooks

After Hooks.deleteTransportAfterTest() 649ms

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 972ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 610ms

And Accept transferred transport by Api 748ms

And Login as "paa1-carrier@qa.qa-test" 2s 312ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 17s 545ms

Hooks

After Hooks.deleteTransportAfterTest() 627ms

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 716ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 192ms

And Transfer transport to carrier by JSON file "super-admin-adama" "false" confirmation 922ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 17s 819ms

Hooks

After Hooks.deleteTransportAfterTest() 696ms

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" 225ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 071ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 908ms

And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 1s 660ms

And Login as "paa1-carrier@qa.qa-test" 2s 287ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 17s 823ms

Hooks

After Hooks.deleteTransportAfterTest() 656ms

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 332ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 118ms

When Go to "TRANSPORT_TABLE" 397ms

And Show all transport "true" 248ms

Then Verify that transport has "1" CMR file 1s 574ms

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() 668ms

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 340ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 2s 426ms

When Go to "TRANSPORT_TABLE" 393ms

And Show all transport "true" 253ms

Then Verify that transport has "2" CMR file 1s 639ms

Hooks

After Hooks.deleteTransportAfterTest() 696ms

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 342ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 2s 385ms

When Go to "TRANSPORT_TABLE" 332ms

And Show all transport "true" 254ms

Then Verify that "CMR" document can be downloaded 18s 993ms

Hooks

After Hooks.deleteTransportAfterTest() 743ms

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 665ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 2s 458ms

And Show all transport "true" 236ms

And Delete transport 19s 111ms

When Go to "ARCHIVE_TAB" 502ms

And Show "TRANSPORT_ORDER" 155ms

Then Verify that "CMR" document can be downloaded 23s 443ms

Hooks

After Hooks.deleteTransportAfterTest() 830ms

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 988ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 116ms

And Show all transport "false" 077ms

When Find transport pencil button in transports table 1s 728ms

And Click pencil and move transport to next day in schedule 5s 721ms

Then Check if transport is in new location in schedule 2s 244ms

And Check if dates in transport form are correct 3s 933ms

Hooks

After Hooks.deleteTransportAfterTest() 835ms

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 625ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 757ms

And Show all transport "false" 078ms

When Find transport pencil button in transports table 1s 841ms

And Click pencil and move transport to next day in schedule 20s 630ms

Then Check if transport is in new location in schedule 2s 284ms

And Check if dates in transport form are correct 3s 854ms

Hooks

After Hooks.deleteTransportAfterTest() 846ms

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 456ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 916ms

And Show all transport "false" 078ms

When Find transport pencil button in transports table 1s 795ms

And Click pencil and move transport to next day in schedule 21s 432ms

Then Check if transport is in new location in schedule 2s 288ms

And Check if dates in transport form are correct 3s 948ms

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 363ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 819ms

And Show all transport "false" 076ms

When Find transport pencil button in transports table 1s 828ms

And Click pencil and move transport to next day in schedule 20s 551ms

Then Check if transport is in new location in schedule 2s 258ms

And Check if dates in transport form are correct 3s 906ms

Hooks

After Hooks.deleteTransportAfterTest() 946ms

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 562ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 3s 016ms

And Show all transport "false" 079ms

When Find transport pencil button in transports table 1s 816ms

And Click pencil and move transport to next day in schedule 20s 589ms

Then Check if transport is in new location in schedule 2s 276ms

And Check if dates in transport form are correct 3s 913ms

Hooks

After Hooks.deleteTransportAfterTest() 840ms

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 559ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-alrec" 2s 985ms

And Show all transport "true" 286ms

When Find transport pencil button in transports table 1s 793ms

And Click pencil and move transport to next day in schedule 20s 194ms

Then Check if transport is in new location in schedule 2s 273ms

And Check if dates in transport form are correct 3s 935ms

Hooks

After Hooks.deleteTransportAfterTest() 916ms

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 574ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 028ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 022ms

When Show all transport types 1s 154ms

And Click button advice in transport table "DELIVERY" 259ms

And Set advice window in schedule 3s 323ms

And Fill advice form 10s 304ms

And Click advice save button and wait for advice form to disappear 33s 361ms

And Go to "TRANSPORT_TABLE" 483ms

And Find transport pencil button in transports table 1s 781ms

And Click pencil and move transport to next day in schedule 7s 177ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[contains(@class, 'btn btn-primary save-advice-button')] (tried for 4 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.ZaXtAd}, 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: 9275f62421ea78059964e579c60af950
	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:219)
	at Pages.Schedule.SchedulePage.moveTransportToNextDayUsingPencilButton(SchedulePage.java:180)
	at CucumberTests.AdviceEdition.PencilEdition.clickInPencilAndMoveAdviceWindowInNewLocationInSchedule(PencilEdition.java:44)
	at ✽.Click pencil and move transport to next day in schedule(file:Features/Atom/Transport/PencilEdition.feature:33)

Then Check if transport is in new location in schedule 000ms

And Check if dates in transport form are correct 000ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 128ms

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" 2s 949ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 234ms

And Show all transport "false" 079ms

When Find transport pencil button in transports table 1s 744ms

And Click pencil and move transport to next day in schedule 20s 552ms

And Move advice window "3" 1s 528ms

Then Check if advice window is in new location 057ms

Hooks

After Hooks.deleteTransportAfterTest() 4s 146ms

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 263ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 749ms

And Show all transport "false" 071ms

When Find transport pencil button in transports table 1s 739ms

And Click pencil and move transport to next day in schedule 20s 366ms

And Move advice window "3" 1s 655ms

Then Check if advice window is in new location 062ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 353ms

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 407ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 832ms

And Show all transport "false" 078ms

When Find transport pencil button in transports table 1s 717ms

And Click pencil and move transport to next day in schedule 21s 327ms

And Move advice window "3" 1s 616ms

Then Check if advice window is in new location 067ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 833ms

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 506ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 897ms

And Show all transport "false" 077ms

When Find transport pencil button in transports table 1s 840ms

And Click pencil and move transport to next day in schedule 20s 581ms

And Move advice window "3" 1s 505ms

Then Check if advice window is in new location 055ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 638ms

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_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 3s 035ms

And Show all transport "false" 073ms

When Find transport pencil button in transports table 1s 831ms

And Click pencil and move transport to next day in schedule 20s 564ms

And Move advice window "3" 1s 523ms

Then Check if advice window is in new location 062ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 712ms

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 502ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 2s 773ms

And Show all transport "true" 244ms

When Find transport pencil button in transports table 1s 838ms

And Click pencil and move transport to next day in schedule 20s 236ms

And Move advice window "3" 1s 570ms

Then Check if advice window is in new location 064ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 295ms

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" 3s 025ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 180ms

And Go to transport details "DELIVERY" 2s 917ms

When Open section: "discrepancy-report-panel" 1s 173ms

Then Verify that no discrepancies found label is visible in discrepancy report section 169ms

And Select "NIE" in the "insp.-accord.-with-ins." 2s 696ms

And Verify that discrepancy report custom fields are visible in discrepancy report section 265ms

Hooks

After Hooks.deleteTransportAfterTest() 972ms

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 803ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 128ms

And Go to transport details "DELIVERY" 2s 879ms

And Fill transport form 40s 791ms

And Click "save-transport-and-close" save button and wait for form to disappear 18s 070ms

When Go to transport details "DELIVERY" 2s 878ms

Then Select "NIE" in the "insp.-accord.-with-ins." 2s 725ms

And Click "save-transport" save button 908ms

And Wait "2" seconds 2s

And Verify that discrepancy report section is open 069ms

And Verify that discrepancy report section contains validation errors 064ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 013ms

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 030ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 131ms

When Go to transport details "DELIVERY" 2s 926ms

Then Verify that discrepancy report section is available 074ms

And Open section: "discrepancy-report-panel" 1s 260ms

And Verify that generate new discrepancy report button is visible 094ms

Hooks

After Hooks.deleteTransportAfterTest() 842ms

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 887ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 2s 957ms

When Go to transport details "OWN_COLLECTION" 2s 944ms

Then Verify that discrepancy report section is available 090ms

And Open section: "discrepancy-report-panel" 1s 213ms

And Verify that generate new discrepancy report button is visible 085ms

Hooks

After Hooks.deleteTransportAfterTest() 800ms

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 830ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 2s 813ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 2s 929ms

Then Verify that discrepancy report section is available 078ms

And Open section: "discrepancy-report-panel" 1s 152ms

And Verify that generate new discrepancy report button is visible 083ms

Hooks

After Hooks.deleteTransportAfterTest() 876ms

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 813ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 3s 142ms

When Go to transport details "EXPORT" 2s 995ms

Then Verify that discrepancy report section is available 075ms

And Open section: "discrepancy-report-panel" 1s 132ms

And Verify that generate new discrepancy report button is visible 108ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 529ms

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 023ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 939ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 923ms

Then Verify that discrepancy report section is available 099ms

And Open section: "discrepancy-report-panel" 1s 219ms

And Verify that generate new discrepancy report button is visible 095ms

Hooks

After Hooks.deleteTransportAfterTest() 664ms

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 746ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 2s 735ms

When Go to transport details "CISTERN_DELIVERY" 2s 924ms

Then Verify that discrepancy report section is not available 15s 087ms

Hooks

After Hooks.deleteTransportAfterTest() 987ms

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 974ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 2s 671ms

When Go to transport details "CISTERN_COLLECTION" 2s 903ms

Then Verify that discrepancy report section is not available 15s 062ms

Hooks

After Hooks.deleteTransportAfterTest() 956ms

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 954ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 2s 215ms

When Go to transport details "WEIGHING" 2s 808ms

Then Verify that discrepancy report section is not available 15s 064ms

Hooks

After Hooks.deleteTransportAfterTest() 694ms

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 804ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 174ms

When Go to "TRANSPORT_TABLE" 424ms

And Go to transport details "DELIVERY" 2s 918ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 843ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 530ms

And Open section: "discrepancy-report-panel" 1s 160ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 019ms

And Fill transport form 40s 834ms

And Fill discrepancy report section without closing the form 22s 174ms

And Generate discrepancy report 19s 992ms

And Download discrepancy report 366ms

Then Verify that discrepancy report file has correct values 16s 340ms

Hooks

After Hooks.deleteTransportAfterTest() 927ms

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 971ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 2s 939ms

When Go to "TRANSPORT_TABLE" 399ms

And Go to transport details "DELIVERY" 2s 886ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 020ms

And Fill transport form 40s 897ms

And Open section: "discrepancy-report-panel" 1s 158ms

And Fill discrepancy report section without closing the form 22s 197ms

And Generate discrepancy report 19s 462ms

And Download discrepancy report 379ms

And Verify that discrepancy report file has correct values 15s 709ms

And Fill edited discrepancy report section 18s 659ms

And Generate edited discrepancy report 2s 753ms

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.ZaXtAd}, 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: 9275f62421ea78059964e579c60af950
	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 106ms

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" 331ms

And Get "LOAD" settings from "piast" 156ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "false" 297ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-piast" 1s 983ms

And Login as "piast-admin" 5s 616ms

And Go to "TRANSPORT_TABLE" 505ms

When Go to transport details "LOAD" 2s 970ms

And Add step "unload" 285ms

And Change filled value in transport details "company-step-2" "autocomplete" "DPA2" "0" 7s 082ms

And Change filled value in transport details "recipient-step-2" "autocomplete" "Testowy" "0" 6s 996ms

Then Click "save-transport-and-close" save button and wait for form to disappear 2s 041ms

And Go to transport details "LOAD" 3s

And Verify that transport has "3" steps 048ms

Hooks

After Hooks.deleteTransportAfterTest() 689ms

After Hooks.rollbackTransportTypeSettings() 192ms

After Hooks.rollbackAddedActionAuthorities() 241ms

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" 6s 916ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 240ms

When Go to "TRANSPORT_TABLE" 418ms

And Go to transport details "SMALLS_IMPORT" 17s 356ms

Then Verify that user can't edit time range for load and unload 15s 035ms

Hooks

After Hooks.deleteTransportAfterTest() 661ms

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" 217ms

And Create transport "CREATE_DELIVERY_TWO_LOADS" by JSON file as "super-admin-neuca" 3s 209ms

And Login as "neuca-admin" 2s 033ms

And Go to "TRANSPORT_TABLE" 492ms

And Show all transport types 15s 032ms

When Go to transport details "DELIVERY" 30s 811ms

Then Check if sum of number of pallets in transport form in "load" steps is correct 213ms

Hooks

After Hooks.deleteTransportAfterTest() 970ms

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" 231ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 17s 071ms

And Login as "hochland-admin" 4s 064ms

And Go to "TRANSPORT_TABLE" 423ms

And Show all transport types 1s 176ms

When Go to transport details "EXPORT" 3s 027ms

Then Check if sum of number of pallets in transport form in "unload" steps is correct 138ms

Hooks

After Hooks.deleteTransportAfterTest() 994ms

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" 294ms

And Get "DELIVERY" settings from "neuca" 238ms

And Set transportType settings with values: "quantitySumCheckValue", "33" 370ms

And Login as "neuca-admin" 2s 330ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 17s 041ms

When Go to "TRANSPORT_TABLE" 561ms

And Go to transport details "DELIVERY" 30s 811ms

And Set number of pallets in "load" step in transport - "32" 294ms

And Check if number of pallets check message is not visible in transport form 15s 078ms

And Set number of pallets in "load" step in transport - "34" 262ms

Then Check if number of pallets check message is visible in transport form 070ms

Hooks

After Hooks.deleteTransportAfterTest() 917ms

After Hooks.rollbackTransportTypeSettings() 436ms

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" 231ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 334ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 291ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 278ms

And Login as "farmacol-admin" 6s 671ms

And Go to new transport "EXTERNAL_DELIVERY" 666ms

And Add step "unload" 211ms

And Click "save-transport-and-close" save button 896ms

Then Verify that "time-range-from-date-2" has validation error 1s 080ms

Then Verify that "time-range-to-date-2" has validation error 1s 076ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 779ms

And Click "save-transport-and-close" save button 904ms

And Verify that "time-range-from-date-2" has no validation error 069ms

And Verify that "time-range-to-date-2" has no validation error 071ms

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.rollbackTransportTypeSettings() 272ms

After Hooks.rollbackAddedActionAuthorities() 254ms

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" 243ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_LOAD_STEP_FROM_UNLOAD" "ACTIVE" 314ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 995ms

When Login as "piast-admin" 5s 559ms

And Go to transport details "LOAD" 3s 069ms

And Get inputs from database "PIAST_LOAD_ADD_UNLOAD_STEP" "super-admin-piast" 018ms

And Add step "unload" 322ms

And Fill step data 16s 107ms

And Get inputs from database "PIAST_LOAD_ADD_LOAD_STEP" "super-admin-piast" 022ms

And Add step "load" 212ms

And Fill step data 5s 746ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 473ms

Then Go to transport details "LOAD" 3s 040ms

And Check if "unload" step is added as "3" step in transport form 091ms

And Check if "load" step is added as "4" step in transport form 099ms

Hooks

After Hooks.deleteTransportAfterTest() 634ms

After Hooks.rollbackAddedActionAuthorities() 266ms

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" 236ms

And Add action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_LOAD_STEPS" "UNLIMITED" 319ms

And Remove action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_UNLOAD_STEPS" "UNLIMITED" 058ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 135ms

When Login as "super-admin-skz" 9s 164ms

And Go to transport details "SMALLS_EXPORT" 2s 870ms

And Check if step is draggable "LOAD" 098ms

And Check if step is not draggable "UNLOAD" 129ms

Hooks

After Hooks.deleteTransportAfterTest() 706ms

After Hooks.rollbackAddedActionAuthorities() 286ms

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 507ms

When Go to new transport "SMALLS_IMPORT" 674ms

And Fill transport form 21s 309ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 400ms

And Show all transport "false" 073ms

And Go to transport details "SMALLS_IMPORT" 2s 978ms

And Click create similar button 15s 225ms

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 359ms

And Open similar transport details 539ms

Then Check are transport values equals 2s 389ms

Hooks

After Hooks.deleteTransportAfterTest() 671ms

After Hooks.deleteSimilarTransportAfterTest() 680ms

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 089ms

When Go to new transport "DELIVERY" 15s 582ms

And Fill transport form 40s 529ms

And Click "save-transport" save button and wait for form to disappear 15s 734ms

And Set advice window in schedule 2s 415ms

And Check is transport created in schedule and set transport id 3s 520ms

And Go to "TRANSPORT_TABLE" 466ms

And Go to transport details "DELIVERY" 30s 609ms

And Click create similar button 15s 290ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 11s 676ms

And Click "save-transport" save button and wait for form to disappear 15s 753ms

And Set advice window in schedule in "2" days 4s 489ms

And Go to "TRANSPORT_TABLE" 425ms

And Open similar transport details 2s 732ms

Then Check are transport values equals 24s 276ms

Hooks

After Hooks.deleteTransportAfterTest() 969ms

After Hooks.deleteSimilarTransportAfterTest() 890ms

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 449ms

When Go to new transport "DELIVERY" 15s 557ms

And Fill transport form 40s 599ms

And Click "save-transport" save button and wait for form to disappear 15s 756ms

And Set advice window in schedule 2s 383ms

And Check is transport created in schedule and set transport id 3s 423ms

And Go to "TRANSPORT_TABLE" 472ms

And Go to transport details "DELIVERY" 30s 607ms

And Click create similar button 15s 279ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 11s 710ms

And Click "save-transport" save button and wait for form to disappear 15s 795ms

And Set advice window in schedule in "2" days 4s 544ms

And Go to "TRANSPORT_TABLE" 440ms

And Open similar transport details 2s 795ms

Then Check is field "CARRIER" of type "autocomplete" equals "Przewoźnik Neuca Automat 1" 076ms

Hooks

After Hooks.deleteTransportAfterTest() 990ms

After Hooks.deleteSimilarTransportAfterTest() 977ms

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" 021ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 664ms

When Go to new transport "SMALLS_IMPORT" 723ms

And Fill transport form 36s 384ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 975ms

And Go to transport details "SMALLS_IMPORT" 2s 903ms

And Go to transport print details form 3s 581ms

Then Check are transport values equals 8s 963ms

Hooks

After Hooks.deleteTransportAfterTest() 788ms

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 864ms

And Get inputs from database "CREATE_SMALLS_IMPORT" "super-admin-skz" 019ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 182ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 860ms

And Go to transport details "SMALLS_IMPORT" 2s 834ms

Then Verify that the transport can be edited 2s 039ms

And Close transport details 15s 257ms

And If user is login then logout 304ms

And Login as "pskza1-carrier@qa.qa-test" 2s 656ms

And Go to transport details "SMALLS_IMPORT" 3s 556ms

And Verify that the transport cannot be edited 46s 947ms

Hooks

After Hooks.deleteTransportAfterTest() 771ms

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 769ms

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 145ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 833ms

And Go to transport details "SMALLS_EXPORT" 2s 869ms

Then Verify that the transport can be edited 1s 807ms

And Close transport details 15s 155ms

And If user is login then logout 296ms

And Login as "pskza1-carrier@qa.qa-test" 2s 728ms

And Go to transport details "SMALLS_EXPORT" 3s 547ms

And Verify that the transport cannot be edited 46s 928ms

Hooks

After Hooks.deleteTransportAfterTest() 738ms

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 683ms

And Get inputs from database "HIDDEN_DATA_SMALLS_IMPORT" "super-admin-skz" 018ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 358ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 831ms

And Go to transport details "SMALLS_IMPORT" 2s 791ms

Then Verify that the hidden data in transport are not visible 1s 112ms

And Close transport details 15s 201ms

And If user is login then logout 312ms

And Login as "swisskrono-admin" 2s 782ms

And Go to transport details "SMALLS_IMPORT" 2s 953ms

And Verify that the hidden data in transport are visible 1s 694ms

Hooks

After Hooks.deleteTransportAfterTest() 743ms

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 574ms

And Get inputs from database "HIDDEN_DATA_SMALLS_EXPORT" "super-admin-skz" 022ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 373ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 850ms

And Go to transport details "SMALLS_EXPORT" 2s 874ms

Then Verify that the hidden data in transport are not visible 1s 118ms

And Close transport details 15s 220ms

And If user is login then logout 290ms

And Login as "swisskrono-admin" 2s 752ms

And Go to transport details "SMALLS_EXPORT" 3s 040ms

And Verify that the hidden data in transport are visible 1s 678ms

Hooks

After Hooks.deleteTransportAfterTest() 916ms

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" 3s 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 182ms

When Go to transport details "DELIVERY" 2s 944ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 549ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 850ms

And Change filled value in transport details "insp.-accord.-with-ins." "select" "NIE" "1" 3s 768ms

And Fill discrepancy report section without closing the form 22s 125ms

And Click "save-transport" save button 3s 266ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 468ms

And Check if transport details form is disappeared 15s 026ms

Hooks

After Hooks.deleteTransportAfterTest() 962ms

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" 234ms

And Add action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 324ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 3s 025ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 3s 224ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 10s 866ms

When Go to "TRANSPORT_TABLE" 474ms

And Go to transport details "DELIVERY" 2s 929ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 509ms

Then Verify that "transport-description" in transport has value "opis" 066ms

Hooks

After Hooks.deleteTransportAfterTest() 949ms

After Hooks.rollbackAddedActionAuthorities() 244ms

After Hooks.rollbackWarehousesAccess() 660ms

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" 232ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 3s 141ms

And Remove action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 354ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 699ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 8s 847ms

When Go to "TRANSPORT_TABLE" 494ms

And Go to transport details "DELIVERY" 3s 376ms

Then Verify that "transport-description" in transport form is disabled 071ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 213ms

After Hooks.rollbackRemovedActionAuthorities() 282ms

After Hooks.rollbackWarehousesAccess() 684ms

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" 243ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 350ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 180ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 086ms

And Show all transport "false" 082ms

When Go to "TRANSPORT_TABLE" 478ms

And Go to transport details "DELIVERY" 2s 904ms

Then Verify that "CARRIER" in transport form is visible 085ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 211ms

After Hooks.rollbackAddedActionAuthorities() 263ms

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" 244ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 323ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 074ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 978ms

And Show all transport "false" 085ms

When Go to "TRANSPORT_TABLE" 439ms

And Go to transport details "TRANSPORT" 2s 910ms

Then Verify that "CARRIER" in transport form is visible 150ms

Hooks

After Hooks.deleteTransportAfterTest() 811ms

After Hooks.rollbackAddedActionAuthorities() 279ms

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" 238ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 329ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 179ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 4s 642ms

And Show all transport "true" 251ms

When Go to "TRANSPORT_TABLE" 308ms

And Go to transport details "TRANSPORT_ORDER" 2s 745ms

Then Verify that "CARRIER" in transport form is visible 127ms

Hooks

After Hooks.deleteTransportAfterTest() 643ms

After Hooks.rollbackAddedActionAuthorities() 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-hochland" 242ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 347ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 136ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 102ms

And Show all transport "false" 079ms

When Go to "TRANSPORT_TABLE" 509ms

And Go to transport details "DELIVERY" 2s 950ms

Then Verify that "CARRIER" in transport form is not visible 15s 046ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 017ms

After Hooks.rollbackRemovedActionAuthorities() 285ms

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" 230ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 340ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 068ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 234ms

And Show all transport "false" 083ms

When Go to "TRANSPORT_TABLE" 400ms

And Go to transport details "TRANSPORT" 2s 973ms

Then Verify that "CARRIER" in transport form is not visible 15s 086ms

Hooks

After Hooks.deleteTransportAfterTest() 644ms

After Hooks.rollbackRemovedActionAuthorities() 269ms

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" 235ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 328ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 246ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 4s 937ms

And Show all transport "true" 248ms

When Go to "TRANSPORT_TABLE" 503ms

And Go to transport details "TRANSPORT_ORDER" 2s 949ms

Then Verify that "CARRIER" in transport form is not visible 15s 030ms

Hooks

After Hooks.deleteTransportAfterTest() 771ms

After Hooks.rollbackRemovedActionAuthorities() 263ms

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" 225ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 283ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 304ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 011ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 8s 969ms

And Show all transport "false" 083ms

When Go to "TRANSPORT_TABLE" 507ms

And Go to transport details "DELIVERY" 2s 916ms

Then Verify that "CARRIER" in transport form is not disabled 074ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 292ms

After Hooks.rollbackAddedActionAuthorities() 548ms

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" 234ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 324ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 305ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 063ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 099ms

And Show all transport "false" 074ms

When Go to "TRANSPORT_TABLE" 363ms

And Go to transport details "TRANSPORT" 2s 826ms

Then Verify that "CARRIER" in transport form is not disabled 142ms

Hooks

After Hooks.deleteTransportAfterTest() 676ms

After Hooks.rollbackAddedActionAuthorities() 497ms

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" 212ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 299ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 292ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 2s 030ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 4s 504ms

And Show all transport "true" 272ms

When Go to "TRANSPORT_TABLE" 386ms

And Go to transport details "TRANSPORT_ORDER" 2s 877ms

Then Verify that "CARRIER" in transport form is not disabled 112ms

Hooks

After Hooks.deleteTransportAfterTest() 625ms

After Hooks.rollbackAddedActionAuthorities() 576ms

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" 234ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 328ms

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 140ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 078ms

And Show all transport "false" 078ms

When Go to "TRANSPORT_TABLE" 492ms

And Go to transport details "DELIVERY" 2s 944ms

Then Verify that "CARRIER" in transport form is disabled 086ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 127ms

After Hooks.rollbackAddedActionAuthorities() 244ms

After Hooks.rollbackRemovedActionAuthorities() 274ms

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" 215ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 320ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 062ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 079ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 020ms

And Show all transport "false" 086ms

When Go to "TRANSPORT_TABLE" 448ms

And Go to transport details "TRANSPORT" 2s 955ms

Then Verify that "CARRIER" in transport form is disabled 152ms

Hooks

After Hooks.deleteTransportAfterTest() 675ms

After Hooks.rollbackAddedActionAuthorities() 293ms

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" 236ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 315ms

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 158ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 4s 597ms

And Show all transport "true" 273ms

When Go to "TRANSPORT_TABLE" 421ms

And Go to transport details "TRANSPORT_ORDER" 2s 858ms

Then Verify that "CARRIER" in transport form is disabled 125ms

Hooks

After Hooks.deleteTransportAfterTest() 898ms

After Hooks.rollbackAddedActionAuthorities() 266ms

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" 203ms

And Get custom field settings for "DELIVERY" transport type and "" company 086ms

And Mark custom fields as not obligatory 004ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 619ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_MAIN_DATA_SECTION" "UNLIMITED" 298ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_ADVICE" "UNLIMITED" 281ms

And Add action authority with: "adama" "adama-admin" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 296ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 827ms

When Find transport in table with status "planned" 3s 788ms

And Confirm statuses until reach "process-ended" 11s 526ms

And Wait "90" seconds 1m 30s

And Go to "ARCHIVE_TAB" 518ms

And Show "DELIVERY" 178ms

And Go to transport details "DELIVERY" 30s 728ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 575ms

And Click "save-transport-and-close" save button and wait for form to disappear 1s 946ms

And Wait "7" seconds 7s

And Go to transport details "DELIVERY" 30s 625ms

Then Verify that "transport-description" in transport has value "opis" 086ms

Hooks

After Hooks.deleteTransportAfterTest() 809ms

After Hooks.rollbackAllCustomFieldsSettings() 004ms

After Hooks.rollbackAddedActionAuthorities() 274ms

After Hooks.rollbackRemovedActionAuthorities() 537ms

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 707ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 168ms

When Go to transport details "DELIVERY" 2s 919ms

And Fill transport form 40s 840ms

And Change filled value in transport details "driver-name" "text" "XXX ZZZ" "0" 1s 684ms

And Click "save-transport-and-close" save button and wait for form to disappear 18s 046ms

And Go to new transport "DELIVERY" 619ms

Then Verify that driver "XXX ZZZ" is in list 981ms

Hooks

After Hooks.deleteTransportAfterTest() 977ms

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 743ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 156ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 5s 278ms

And If user is login then logout 250ms

And Login as "pskza1-carrier@qa.qa-test" 2s 536ms

Then Verify that the transport has been transferred 3s 108ms

And Accept or reject "accept" transferred transport 16s 637ms

And Go to transport details "SMALLS_IMPORT" 2s 842ms

And Verify that "transaction-price" in transport form is visible 130ms

And Verify that transaction price field has correct value 088ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_IMPORT" 131ms

Hooks

After Hooks.deleteTransportAfterTest() 650ms

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 612ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 138ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 20s 159ms

And If user is login then logout 276ms

And Login as "pskza1-carrier@qa.qa-test" 2s 691ms

Then Verify that the transport has been transferred 3s 212ms

And Accept or reject "accept" transferred transport 16s 535ms

And Go to transport details "SMALLS_EXPORT" 2s 900ms

And Verify that "transaction-price" in transport form is visible 100ms

And Verify that transaction price field has correct value 114ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_EXPORT" 202ms

Hooks

After Hooks.deleteTransportAfterTest() 746ms

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" 226ms

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 113ms

And Mark custom fields as not obligatory 004ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 107ms

And Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 001ms

When Login as "dayco-admin" 4s 714ms

And Click button advice in transport table "OWN_COLLECTION" 939ms

And Set advice window in schedule 3s 228ms

And Fill advice form 9s 221ms

And Click advice save button and wait for advice form to disappear 33s 289ms

And Go to "TRANSPORT_TABLE" 400ms

And Find transport in table with status "planned" 3s 669ms

And Confirm statuses until reach "on-the-area" 6s 265ms

And Go to transport details "OWN_COLLECTION" 2s 881ms

And Click create similar button 15s 279ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 6s 987ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 360ms

And Open similar transport details 525ms

Then Check if transport form modal is visible 117ms

Hooks

After Hooks.deleteTransportAfterTest() 894ms

After Hooks.deleteSimilarTransportAfterTest() 627ms

After Hooks.rollbackAllCustomFieldsSettings() 468ms

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" 235ms

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 1s 560ms

And Mark custom fields as not obligatory 004ms

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 998ms

And Click button advice in transport table "OWN_COLLECTION" 859ms

And Set advice window in schedule 3s 241ms

And Fill advice form 9s 001ms

And Click advice save button and wait for advice form to disappear 33s 272ms

And Go to "TRANSPORT_TABLE" 440ms

And Find transport in table with status "planned" 3s 699ms

And Confirm statuses until reach "during-load" 11s 461ms

And Go to transport details "OWN_COLLECTION" 2s 876ms

And Click create similar button 15s 208ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 6s 982ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 325ms

And Open similar transport details 443ms

Then Check if transport form modal is visible 101ms

Hooks

After Hooks.deleteTransportAfterTest() 978ms

After Hooks.deleteSimilarTransportAfterTest() 616ms

After Hooks.rollbackAllCustomFieldsSettings() 484ms

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" 210ms

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 097ms

When Login as "lisner-admin" and set token of apiUsername "super-admin-lisner" 6s 393ms

And Go to new transport "DELIVERY" 650ms

And Fill transport form 31s 300ms

And Click "save-transport" save button and wait for form to disappear 15s 779ms

And Set advice window in schedule 2s 392ms

And Go to "TRANSPORT_TABLE" 448ms

And Show all transport types 1s 178ms

And Go to transport details "DELIVERY" 2s 727ms

Then Verify that "date-and-time" in transport form is visible 092ms

Hooks

After Hooks.deleteTransportAfterTest() 975ms

After Hooks.deleteCustomFieldAfterTest() 2s 726ms

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 903ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 166ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 663ms

When Click invoice button 3s 321ms

And Set default invoice currency value 150ms

Then Check that default currency value in invoice form is "EUR" 111ms

When Change invoice default currency value in database for "USD" transport type alias "SMALLS_IMPORT" and principal alias "swisskrono" 112ms

And Clear all cache 2s 439ms

And Login as "swisskrono-admin" 11s 088ms

And Go to "TRANSPORT_TABLE" 424ms

And Show all transport types 1s 185ms

And Click invoice button 632ms

Then Check that default currency value in invoice form is "USD" 147ms

Hooks

After Hooks.deleteTransportAfterTest() 966ms

After Hooks.rollbackInvoiceCurrency() 2s 306ms

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" 11s 014ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 092ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 637ms

When Click invoice button 3s 478ms

And Set default invoice currency value 167ms

Then Check that default currency value in invoice form is "EUR" 133ms

When Change invoice default currency value in database for "USD" transport type alias "SMALLS_EXPORT" and principal alias "swisskrono" 109ms

And Clear all cache 2s 307ms

And Login as "swisskrono-admin" 10s 679ms

And Go to "TRANSPORT_TABLE" 412ms

And Show all transport types 1s 178ms

And Click invoice button 815ms

Then Check that default currency value in invoice form is "USD" 153ms

Hooks

After Hooks.deleteTransportAfterTest() 973ms

After Hooks.rollbackInvoiceCurrency() 2s 319ms

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 190ms

And Create transport "CREATE_DELIVERY_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 2s 999ms

And Show all transport types 1s 140ms

Then Check if transport number is visible "DELIVERY" 15s 184ms

And Check if transport details is not visible 15s 050ms

Hooks

After Hooks.deleteTransportAfterTest() 920ms

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 056ms

And Show all transport "false" 077ms

And Go to "TRANSPORT_TABLE" 414ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 177ms

When Click on transport row 169ms

Then Verify if transport row is selected 081ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 018ms

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 510ms

And Show all transport "false" 083ms

And Go to "TRANSPORT_TABLE" 442ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 748ms

When Click on transport row 176ms

Then Verify if transport row is selected 074ms

Hooks

After Hooks.deleteTransportAfterTest() 874ms

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 730ms

And Show all transport "false" 078ms

And Go to "TRANSPORT_TABLE" 403ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 16s 637ms

When Click on transport row 183ms

Then Verify if transport row is selected 097ms

Hooks

After Hooks.deleteTransportAfterTest() 945ms

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 214ms

And Show all transport "false" 083ms

And Go to "TRANSPORT_TABLE" 476ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 3s

When Click on transport row 167ms

Then Verify if transport row is selected 082ms

Hooks

After Hooks.deleteTransportAfterTest() 950ms

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 695ms

And Show all transport "false" 091ms

And Go to "TRANSPORT_TABLE" 409ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 932ms

When Click on transport row 167ms

Then Verify if transport row is selected 081ms

Hooks

After Hooks.deleteTransportAfterTest() 913ms

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 310ms

And Show all transport "true" 265ms

And Go to "TRANSPORT_TABLE" 428ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 2s 824ms

When Click on transport row 168ms

Then Verify if transport row is selected 080ms

Hooks

After Hooks.deleteTransportAfterTest() 886ms

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 794ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 351ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 612ms

When Accept or reject "accept" transferred transport 17s 915ms

Then Verify that transport is accept or reject "accept" 079ms

Hooks

After Hooks.deleteTransportAfterTest() 642ms

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 664ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 389ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 609ms

When Accept or reject "reject" transferred transport 17s 533ms

Then Verify that transport is accept or reject "reject" 15s 077ms

Hooks

After Hooks.deleteTransportAfterTest() 743ms

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 113ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 314ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 679ms

When Accept or reject "accept" transferred transport 19s 881ms

Then Verify that transport is accept or reject "accept" 075ms

Hooks

After Hooks.deleteTransportAfterTest() 701ms

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 735ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 291ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 668ms

When Accept or reject "reject" transferred transport 19s 621ms

Then Verify that transport is accept or reject "reject" 15s 112ms

Hooks

After Hooks.deleteTransportAfterTest() 791ms

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 868ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 446ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 644ms

When Accept or reject "accept" transferred transport 20s 132ms

Then Verify that transport is accept or reject "accept" 074ms

Hooks

After Hooks.deleteTransportAfterTest() 689ms

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 662ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 561ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 580ms

When Accept or reject "reject" transferred transport 19s 778ms

Then Verify that transport is accept or reject "reject" 15s 101ms

Hooks

After Hooks.deleteTransportAfterTest() 785ms

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 663ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 083ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 5s 300ms

And If user is login then logout 234ms

And Login as "paa1-carrier@qa.qa-test" 2s 536ms

Then Verify that the transport has been transferred with "true" 1s 745ms

Hooks

After Hooks.deleteTransportAfterTest() 900ms

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 456ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 071ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 20s 769ms

And If user is login then logout 260ms

And Login as "paa1-carrier@qa.qa-test" 2s 560ms

Then Verify that the transport has been transferred with "false" 1s 663ms

Hooks

After Hooks.deleteTransportAfterTest() 699ms

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 647ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 147ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 20s 247ms

And If user is login then logout 658ms

And Login as "pskza1-carrier@qa.qa-test" 2s 422ms

Then Verify that the transport has been transferred 3s 161ms

Hooks

After Hooks.deleteTransportAfterTest() 954ms

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 745ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 026ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 20s 071ms

And If user is login then logout 282ms

And Login as "pskza1-carrier@qa.qa-test" 2s 653ms

Then Verify that the transport has been transferred 3s 166ms

Hooks

After Hooks.deleteTransportAfterTest() 951ms

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 535ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 248ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 836ms

And Go to auction offer 1s 545ms

When Offer "1000" 384ms

And Verify that offer with "1000" has been added to auction 3s 087ms

And If user is login then logout 272ms

And Login as "swisskrono-admin" 2s 615ms

Then Go to auction details 1s 808ms

And Pass transport to carrier from auction details 1s 507ms

And If user is login then logout 1s 379ms

And Login as "pskza1-carrier@qa.qa-test" 2s 310ms

And Verify that the transport has been transferred 3s 090ms

Hooks

After Hooks.deleteTransportAfterTest() 900ms

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 554ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 370ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 837ms

And Go to auction offer 1s 500ms

When Offer "1000" 331ms

And Verify that offer with "1000" has been added to auction 3s 091ms

And Wait till auction end 1m 53s 014ms

And If user is login then logout 233ms

Then Login as "swisskrono-admin" 2s 863ms

And Go to auction details 2s 198ms

And Pass transport to carrier from auction details 1s 515ms

And If user is login then logout 6s 223ms

And Login as "pskza1-carrier@qa.qa-test" 2s 295ms

And Verify that the transport has been transferred 3s 245ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 012ms

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 647ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 121ms

And Go to "TRANSPORT_TABLE" 481ms

When Open transport transfer modal 1s 655ms

Then Verify that all enabled companies from "swisskrono" are shown in select 322ms

Hooks

After Hooks.deleteTransportAfterTest() 720ms

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" 269ms

And Reject main section of a "Przewoźnik Adama Automat 1" in "adama" by API 776ms

And Login as "adama-admin" 2s 143ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 982ms

And Go to "TRANSPORT_TABLE" 341ms

When Open transport transfer modal 1s 598ms

Then Verify that "Przewoźnik Adama Automat 1" is blocked in select 214ms

Hooks

After Hooks.deleteTransportAfterTest() 738ms

After Hooks.rollbackRejectedSections() 446ms

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 345ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 040ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" with "120" seconds to accept transport 5s 611ms

And If user is login then logout 219ms

When Login as "paa1-carrier@qa.qa-test" 4s 809ms

And Verify that the transport has been transferred with "true" 1s 910ms

And Wait "120" seconds 2m

Then Verify if transport is not visible to carrier after expiring time to accept transport 15s 092ms

Hooks

After Hooks.deleteTransportAfterTest() 684ms

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 500ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 3s 060ms

When Go to "TRANSPORT_TABLE" 492ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 819ms

Then Check if new assortment group is disabled in transport form 075ms

Hooks

After Hooks.deleteTransportAfterTest() 925ms

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 425ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 923ms

And Get inputs from database "CREATE_ADVICE_CONTAINER" "super-admin-adama" 021ms

When Show all transport types 1s 160ms

And Click button advice in transport table "CONTAINER" 343ms

And Set advice window in schedule 3s 147ms

And Click button cancel in advice form 16s 175ms

And Set advice window in schedule 2s 397ms

And Click button cancel in advice form 16s 098ms

And Set advice window in schedule 2s 329ms

And Fill advice form 19s 699ms

And Click advice save button and wait for advice form to disappear 33s 282ms

And Go to "TRANSPORT_TABLE" 461ms

And Go to transport details "CONTAINER" 2s 870ms

Then Check are advice values equals 3s 015ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 045ms

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 622ms

And Get inputs from database "CREATE_TRANSPOSRT_ORDER" "super-admin-adama" 021ms

When Go to new transport "TRANSPORT" 716ms

And Fill transport form 28s 978ms

And Click "save-transport-and-close" save button and wait for form to disappear 1s 412ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 5s 253ms

And Check is transport "TRANSPORT" created in transport table and set transport id 1s 325ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 612ms

And Accept or reject "reject" transferred transport 17s 578ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 565ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 5s 292ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 540ms

And Accept or reject "accept" transferred transport 17s 950ms

Then Verify that transport is accept or reject "accept" 059ms

Hooks

After Hooks.deleteTransportAfterTest() 763ms

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 605ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-piast" 020ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 028ms

When Show all transport types 1s 160ms

And Click button advice in transport table "DELIVERY" 318ms

And Set advice window in schedule 3s 330ms

And Click button cancel in advice form 16s 180ms

And Go to "TRANSPORT_TABLE" 465ms

When Go to transport details "DELIVERY" 2s 878ms

And Fill transport form 1m 8s 651ms

And Click "save-transport-and-close" save button and wait for form to disappear 17s 504ms

And Go to transport details "DELIVERY" 2s 778ms

Then Check are transport values equals 146ms

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() 761ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@deleteTransportAfterTest	3872	16	15	0	0	3903	388	16	404	6h 40m 1s 485ms	Failed

Tag Report