Cucumber-JVM Reports - Tag: @deleteTransportAfterTest

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

	Steps	Scenarios	Features
@deleteTransportAfterTest	3378	45	82	0	0	3505	338	47	385	6h 10m 23s 578ms	Failed

View Feature Advice transport

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

Steps

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

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 3s 514ms

And Get inputs from database "CREATE_ADVICE_CONTAINER" "super-admin-adama" 1s 675ms

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

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

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

And Fill advice form 16s 056ms

And Click advice save button to check error message 104ms

Then Check if possible advice alert is displayed 019ms

Hooks

After Hooks.deleteTransportAfterTest() 312ms

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

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

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

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

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

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

And Fill advice form 8s 417ms

And Click advice save button to check error message 068ms

Then Check if possible advice alert is displayed 043ms

Hooks

After Hooks.deleteTransportAfterTest() 137ms

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

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

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

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

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

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

And Fill advice form 8s 336ms

And Click advice save button to check error message 086ms

Then Check if possible advice alert is displayed 019ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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

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

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

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

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

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

And Fill advice form 13s 199ms

And Click advice save button to check error message 068ms

Then Check if possible advice alert is displayed 020ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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

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

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

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

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

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

And Fill advice form 13s 119ms

And Click advice save button to check error message 092ms

Then Check if possible advice alert is displayed 025ms

Hooks

After Hooks.deleteTransportAfterTest() 185ms

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

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

And Show all transport types 1s 039ms

And Create advice "CREATE_ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 49s 595ms

And Go to "TRANSPORT_TABLE" 203ms

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

When Go to transport details "CONTAINER" 4s 399ms

And Fill transport form 4s 779ms

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

And Expand advice panel 096ms

And Edit advice in transport details 12s 471ms

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

And Go to transport details "CONTAINER" 4s 337ms

And Expand advice panel 090ms

Then Check are advice values equals after edition 189ms

Hooks

After Hooks.deleteTransportAfterTest() 176ms

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

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

And Show all transport types 1s 044ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 41s 805ms

And Go to "TRANSPORT_TABLE" 207ms

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

When Go to transport details "DELIVERY" 4s 425ms

And Fill transport form 1m 1s 979ms

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

And Expand advice panel 097ms

And Edit advice in transport details 6s 536ms

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

And Go to transport details "DELIVERY" 4s 485ms

And Expand advice panel 109ms

Then Check are advice values equals after edition 090ms

Hooks

After Hooks.deleteTransportAfterTest() 184ms

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

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

And Show all transport types 1s 034ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-piast" 41s 657ms

And Go to "TRANSPORT_TABLE" 187ms

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

When Go to transport details "LOAD" 4s 641ms

And Fill transport form 56s 798ms

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

And Expand advice panel 109ms

And Edit advice in transport details 6s 613ms

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

And Go to transport details "LOAD" 4s 572ms

And Expand advice panel 091ms

Then Check are advice values equals after edition 080ms

Hooks

After Hooks.deleteTransportAfterTest() 212ms

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

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

And Show all transport types 1s 037ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 46s 257ms

And Go to "TRANSPORT_TABLE" 170ms

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

When Go to transport details "LOAD" 4s 428ms

And Fill transport form 24s 522ms

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

And Expand advice panel 101ms

And Edit advice in transport details 18s 414ms

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

And Go to transport details "LOAD" 4s 393ms

And Expand advice panel 101ms

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

Hooks

After Hooks.deleteTransportAfterTest() 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" 1s 114ms

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

And Show all transport types 1s 043ms

And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-keeeper" 46s 639ms

And Go to "TRANSPORT_TABLE" 177ms

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

When Go to transport details "CONTAINER" 4s 386ms

And Fill transport form 24s 501ms

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

And Expand advice panel 088ms

And Edit advice in transport details 18s 452ms

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

And Go to transport details "CONTAINER" 4s 403ms

And Expand advice panel 097ms

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

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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

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

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

When Show all transport types 1s 040ms

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

And Set advice window in schedule 2s 433ms

And Fill advice form 12s 271ms

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

And Go to "TRANSPORT_TABLE" 180ms

And Go to transport details "CONTAINER" 4s 393ms

Then Check are advice values equals 277ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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

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

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

When Show all transport types 1s 031ms

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

And Set advice window in schedule 6s 476ms

And Fill advice form 11s 750ms

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

And Go to "TRANSPORT_TABLE" 192ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 604ms

Then Check are advice values equals 2s 270ms

Hooks

After Hooks.deleteTransportAfterTest() 250ms

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

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

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

When Show all transport types 1s 037ms

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

And Set advice window in schedule 2s 619ms

And Fill advice form 8s 213ms

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

And Go to "TRANSPORT_TABLE" 183ms

And Go to transport details "DELIVERY" 4s 524ms

Then Check are advice values equals 353ms

Hooks

After Hooks.deleteTransportAfterTest() 142ms

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

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

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

When Show all transport types 1s 044ms

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

And Set advice window in schedule 2s 590ms

And Fill advice form 8s 314ms

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

And Go to "TRANSPORT_TABLE" 172ms

And Go to transport details "LOAD" 4s 695ms

Then Check are advice values equals 202ms

Hooks

After Hooks.deleteTransportAfterTest() 135ms

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

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

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

When Show all transport types 1s 034ms

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

And Set advice window in schedule 2s 463ms

And Fill advice form 13s 067ms

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

And Go to "TRANSPORT_TABLE" 182ms

And Go to transport details "LOAD" 4s 397ms

Then Check are advice values equals 2s 281ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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

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

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

When Show all transport types 1s 037ms

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

And Set advice window in schedule 2s 515ms

And Fill advice form 12s 970ms

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

And Go to "TRANSPORT_TABLE" 211ms

And Go to transport details "CONTAINER" 4s 382ms

Then Check are advice values equals 2s 282ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 238ms

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

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

And Accept transferred transport by Api 381ms

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

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

When Show all transport types 1s 081ms

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

And Set advice window in schedule 2s 498ms

And Fill advice form 11s 667ms

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

And Go to "TRANSPORT_TABLE" 218ms

And Go to transport details "TRANSPORT" 4s 458ms

Then Check are advice values equals 2s 267ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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

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

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

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

And Accept transferred transport by Api 125ms

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

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

When Show all transport types 1s 090ms

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

And Set advice window in schedule 2s 692ms

And Fill advice form 14s 403ms

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

And Go to "TRANSPORT_TABLE" 165ms

And Go to transport details "SMALLS_IMPORT" 4s 469ms

Then Check are advice values equals 2s 289ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

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

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

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

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

And Accept transferred transport by Api 119ms

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

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

When Show all transport types 1s 121ms

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

And Set advice window in schedule 2s 647ms

And Fill advice form 14s 466ms

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

And Go to "TRANSPORT_TABLE" 154ms

And Go to transport details "SMALLS_EXPORT" 4s 440ms

Then Check are advice values equals 2s 294ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 218ms

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

And Accept transferred transport by Api 097ms

And Login as "paa1-carrier@qa.qa-test" 1s 241ms

When Show all transport types 1s 141ms

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

And Set week view 1s 527ms

And Show yesterday 1s 062ms

Then Check if advice restriction blockade windows are visible 025ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

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

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

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

And Accept transferred transport by Api 114ms

And Login as "pskza1-carrier@qa.qa-test" 1s 103ms

When Show all transport types 1s 088ms

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

And Set week view 2s 022ms

And Show yesterday 1s 097ms

Then Check if advice restriction blockade windows are visible 021ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 15s 229ms

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

And Accept transferred transport by Api 102ms

And Login as "pskza1-carrier@qa.qa-test" 1s 404ms

When Show all transport types 1s 099ms

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

And Set week view 2s 015ms

And Show yesterday 1s 081ms

Then Check if advice restriction blockade windows are visible 032ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 462ms

And Show all transport "false" 026ms

And Click on time window date 1s 292ms

And Select view "DAYS_4" 2s 048ms

And Move advice window "3" 1s 308ms

Then Check if advice window is in new location 024ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

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

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 645ms

And Show all transport "false" 017ms

And Click on time window date 15s 665ms

And Select view "DAYS_4" 2s 059ms

And Move advice window "3" 1s 420ms

Then Check if advice window is in new location 036ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 293ms

And Show all transport "false" 014ms

And Click on time window date 15s 547ms

And Select view "DAYS_4" 2s 065ms

And Move advice window "3" 1s 369ms

Then Check if advice window is in new location 023ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 330ms

And Show all transport "false" 018ms

And Click on time window date 1s 418ms

And Select view "DAYS_4" 2s 056ms

And Move advice window "3" 1s 383ms

Then Check if advice window is in new location 019ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 400ms

And Show all transport "false" 015ms

And Click on time window date 1s 282ms

And Select view "DAYS_4" 2s 055ms

And Move advice window "3" 1s 287ms

Then Check if advice window is in new location 022ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

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

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

And Show all transport "true" 062ms

And Click on time window date 1s 348ms

And Select view "DAYS_4" 2s 054ms

And Move advice window "3" 1s 309ms

Then Check if advice window is in new location 022ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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

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

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

When Show all transport types 1s 031ms

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

And Set advice window in schedule 2s 647ms

And Fill advice form 8s 271ms

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

And Go to "TRANSPORT_TABLE" 312ms

And Click on time window date 1s 401ms

And Select view "DAYS_4" 2s 049ms

And Move advice window "3" 1s 376ms

Then Check if advice window is in new location 018ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 401ms

And Go to "TRANSPORT_TABLE" 149ms

And Show all transport types 1s 025ms

And Click on time window date 1s 280ms

And Scroll to time window "adviceWindow" 038ms

And Set time window height "80" "adviceWindow" 2s 367ms

Then Check height of the time window after expanding by "80" in "adviceWindow" 024ms

Error message

java.lang.AssertionError: Okno nie zmieniło swojego rozmiaru
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Schedule.ResizeTimeWindowTest.checkHeightOfTimeWindowAfterExpandingByIn(ResizeTimeWindowTest.java:35)
	at ✽.Check height of the time window after expanding by "80" in "adviceWindow"(file:Features/Atom/Advice/AdviceTransport.feature:186)

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 313ms

And Go to "TRANSPORT_TABLE" 109ms

And Show all transport types 1s 034ms

And Click on time window date 1s 423ms

And Scroll to time window "adviceWindow" 029ms

And Set time window height "120" "adviceWindow" 2s 363ms

Then Check height of the time window after expanding by "120" in "adviceWindow" 020ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 300ms

And Go to "TRANSPORT_TABLE" 115ms

And Show all transport types 1s 037ms

And Click on time window date 1s 316ms

And Scroll to time window "adviceWindow" 029ms

And Set time window height "48" "adviceWindow" 2s 367ms

Then Check height of the time window after expanding by "48" in "adviceWindow" 019ms

Error message

java.lang.AssertionError: Okno nie zmieniło swojego rozmiaru
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Schedule.ResizeTimeWindowTest.checkHeightOfTimeWindowAfterExpandingByIn(ResizeTimeWindowTest.java:35)
	at ✽.Check height of the time window after expanding by "48" in "adviceWindow"(file:Features/Atom/Advice/AdviceTransport.feature:186)

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 15s 369ms

And Go to "TRANSPORT_TABLE" 234ms

And Show all transport types 15s 059ms

And Click on time window date 15s 775ms

And Scroll to time window "adviceWindow" 037ms

And Set time window height "40" "adviceWindow" 2s 400ms

Then Check height of the time window after expanding by "40" in "adviceWindow" 034ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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

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

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

When Show all transport types 1s 041ms

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

And Set advice window in schedule 2s 619ms

And Fill advice form 8s 307ms

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

And Go to "TRANSPORT_TABLE" 203ms

And Click on time window date 1s 398ms

And Set time window height "120" "adviceWindow" 2s 379ms

Then Check height of the time window after expanding by "120" in "adviceWindow" 016ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 557ms

And Go to "WAREHOUSE_TAB" 814ms

And Select warehouse "Twarożkarnia wyrób gotowy" 1s 834ms

When Go to new transport "DELIVERY" 345ms

And Fill transport form 39s 432ms

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

And Click previous page button in browser 025ms

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

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

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 619ms

And Go to "WAREHOUSE_TAB" 772ms

And Select warehouse "Twarożkarnia wyrób gotowy" 1s 855ms

When Go to new transport "DELIVERY" 335ms

And Fill transport form 39s 478ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_TRANSPORT_WITHOUT_WAREHOUSES" by JSON file as "super-admin-adama" 1s 235ms

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

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

When Show all transport types 1s 036ms

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

And Fill advice form 11s 539ms

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

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

And Open statuses popup 125ms

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

Hooks

After Hooks.deleteTransportAfterTest() 081ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if time window details preview displays correctly

Steps

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

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 213ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 736ms

And Login as "farmacol-admin" 1s 335ms

And Go to "WAREHOUSE_TAB" 728ms

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

And Set week view 2s 258ms

And Move cursor over time window element 368ms

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

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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

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

And Fill transport form 34s 213ms

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

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

And Set advice window in schedule 2s 147ms

And Check is transport created in schedule and set transport id 980ms

Then Go to "OWN_COMPANY_TAB" 256ms

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

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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_SUPPLIER" "super-admin-alrec" 002ms

And Login as "daa1-supplier-3" and set token of apiUsername "super-admin-alrec" 1s 415ms

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

And Fill transport form 16s 168ms

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

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

And Set advice window in schedule 2s 140ms

And Check is transport created in schedule and set transport id 628ms

Then Go to "OWN_COMPANY_TAB" 270ms

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

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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

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

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

When Go to "TRANSPORT_TABLE" 193ms

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

And Show all transport types 1s 067ms

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

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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

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

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

When Go to "TRANSPORT_TABLE" 168ms

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

And Show all transport types 1s 075ms

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

Hooks

After Hooks.deleteTransportAfterTest() 088ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 101ms

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

And Show all transport types 1s 085ms

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

Hooks

After Hooks.deleteTransportAfterTest() 085ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 112ms

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

And Show all transport types 1s 068ms

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

Hooks

After Hooks.deleteTransportAfterTest() 076ms

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

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

And Delete created transport by API 070ms

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

When Go to "ARCHIVE_TAB" 225ms

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

And Show "SMALLS_IMPORT" 072ms

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

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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

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

And Delete created transport by API 084ms

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

When Go to "ARCHIVE_TAB" 199ms

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

And Show "SMALLS_IMPORT" 077ms

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

Hooks

After Hooks.deleteTransportAfterTest() 067ms

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

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

And Delete created transport by API 086ms

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

When Go to "ARCHIVE_TAB" 215ms

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

And Show "SMALLS_IMPORT" 065ms

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

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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

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

And Delete created transport by API 088ms

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

When Go to "ARCHIVE_TAB" 205ms

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

And Show "SMALLS_IMPORT" 070ms

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

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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

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

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

And Go to "TRANSPORT_TABLE" 111ms

And Show all transport "true" 082ms

And Select transportType "TRANSPORT_ORDER" 1s 112ms

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

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 238ms

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

And Toggle transport table days limit filter 066ms

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

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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

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

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

When Go to "TRANSPORT_TABLE" 112ms

And Go to auction form 1s 312ms

And Select contractors group "Kraj" 079ms

Then Verify that carrier "PSKZA1" is selected 020ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

After Hooks.removeContractorsGroup() 091ms

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

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

When Go to "TRANSPORT_TABLE" 116ms

And Go to auction form 1s 171ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 087ms

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

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

When Go to "TRANSPORT_TABLE" 091ms

And Go to auction form 1s 176ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 078ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 243ms

And Show all transport "false" 011ms

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

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

When Go to transport details "TRANSPORT" 4s 399ms

And Expand index panel 081ms

And Click add index button 123ms

And Fill index form 10s 458ms

And Click ok button in index form 15s 107ms

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

And Go to transport details "TRANSPORT" 4s 426ms

And Expand index panel 113ms

Then Check are transport values equals 080ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

After Hooks.deleteProductAfterTest() 065ms

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

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

And Show all transport "true" 072ms

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

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

When Go to transport details "TRANSPORT_ORDER" 4s 488ms

And Expand index panel 092ms

And Click add index button 120ms

And Fill index form 7s 395ms

And Click ok button in index form 15s 111ms

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

And Go to transport details "TRANSPORT_ORDER" 4s 368ms

And Expand index panel 102ms

Then Check are transport values equals 2s 104ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 243ms

And Show all transport "false" 011ms

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

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

When Go to transport details "TRANSPORT" 4s 424ms

And Add index to transport 25s 763ms

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

When Go to transport details "TRANSPORT" 4s 390ms

And Expand index panel 118ms

And Click delete index button 057ms

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

And Go to transport details "TRANSPORT" 4s 339ms

And Expand index panel 088ms

Then Verify that transport has no indexes 15s 015ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

After Hooks.deleteProductAfterTest() 041ms

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

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

And Show all transport "true" 072ms

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

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

When Go to transport details "TRANSPORT_ORDER" 4s 495ms

And Add index to transport 22s 776ms

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

When Go to transport details "TRANSPORT_ORDER" 4s 339ms

And Expand index panel 108ms

And Click delete index button 057ms

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

And Go to transport details "TRANSPORT_ORDER" 4s 305ms

And Expand index panel 082ms

Then Verify that transport has no indexes 15s 044ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

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

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 210ms

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

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

And Go to transport details "OWN_COLLECTION" 4s 416ms

And Add index to transport 24s 499ms

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

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 40s 228ms

When Click on index details icon 086ms

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

Hooks

After Hooks.deleteTransportAfterTest() 095ms

After Hooks.deleteProductAfterTest() 044ms

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

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

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

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

And Show all transport types 1s 040ms

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

And Set advice window in schedule 2s 473ms

And Fill advice form 11s 714ms

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

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

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/AdviceMail.feature:15)

Hooks

After Hooks.deleteTransportAfterTest() 133ms

After Hooks.cleanUserDetailsAfterTest() 144ms

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

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

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

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

And Show all transport types 1s 038ms

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

And Set advice window in schedule 2s 622ms

And Fill advice form 8s 317ms

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

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

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/AdviceMail.feature:15)

Hooks

After Hooks.deleteTransportAfterTest() 123ms

After Hooks.cleanUserDetailsAfterTest() 120ms

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

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

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

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

And Show all transport types 1s 040ms

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

And Set advice window in schedule 2s 478ms

And Fill advice form 13s 054ms

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

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

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/AdviceMail.feature:15)

Hooks

After Hooks.deleteTransportAfterTest() 121ms

After Hooks.cleanUserDetailsAfterTest() 125ms

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

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

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

And Show all transport types 1s 037ms

And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 45s 018ms

And Go to "TRANSPORT_TABLE" 172ms

And Go to transport details "CONTAINER" 4s 386ms

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

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

And Fill transport form 4s 713ms

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

And Expand advice panel 095ms

And Edit advice in transport details 12s 226ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zmiana w awizacji numer" 3m 15s 117ms

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/AdviceMail.feature:39)

Hooks

After Hooks.deleteTransportAfterTest() 133ms

After Hooks.cleanUserDetailsAfterTest() 114ms

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

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

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

And Show all transport types 1s 041ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 41s 669ms

And Go to "TRANSPORT_TABLE" 249ms

And Go to transport details "DELIVERY" 4s 509ms

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

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

And Fill transport form 1m 1s 881ms

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

And Expand advice panel 096ms

And Edit advice in transport details 6s 549ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zmiana w awizacji numer" 3m 24s 532ms

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/AdviceMail.feature:39)

Hooks

After Hooks.deleteTransportAfterTest() 165ms

After Hooks.cleanUserDetailsAfterTest() 130ms

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

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

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

And Show all transport types 1s 037ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 46s 208ms

And Go to "TRANSPORT_TABLE" 149ms

And Go to transport details "LOAD" 4s 366ms

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

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

And Fill transport form 24s 516ms

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

And Expand advice panel 092ms

And Edit advice in transport details 18s 416ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zmiana w awizacji numer" 3m 16s 822ms

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/AdviceMail.feature:39)

Hooks

After Hooks.deleteTransportAfterTest() 144ms

After Hooks.cleanUserDetailsAfterTest() 101ms

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 1s 330ms

And Confirm status "ARRIVAL" by Public API "v1" 359ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Potwierdzono status Wjazd na teren zakładu" 3m 21s 144ms

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/AdviceMail.feature:53)

And Confirm status "DEPARTURE" by Public API "v1" 000ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 164ms

After Hooks.cleanUserDetailsAfterTest() 118ms

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

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

Error message

java.lang.IllegalStateException: Transaction already active
	at org.hibernate.engine.transaction.internal.TransactionImpl.begin(TransactionImpl.java:75)
	at Utils.JpaUtils.Apollo.SelectService.ApolloUpdateDbService.updatePartnership(ApolloUpdateDbService.java:27)
	at CucumberTests.Company.EditCompanyTest.prepareCompanyVerificationMailSetting(EditCompanyTest.java:122)
	at ✽.Prepare company "Dostawca Hochland Automat 1" verification email setting "48h"(file:Features/Atom/Mail/AdviceMail.feature:64)

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

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

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

And Wait "120" seconds 000ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.cleanUserDetailsAfterTest() 000ms

Error message

java.lang.NullPointerException
	at Utils.JsonApiUtil.editJsonTextNode(JsonApiUtil.java:141)
	at CucumberTests.Hooks.cleanUserDetailsAfterTest(Hooks.java:302)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

After Hooks.rollbackVerificationEmailSettingAfterTest() 004ms

Error message

java.lang.IllegalStateException: Transaction already active
	at org.hibernate.engine.transaction.internal.TransactionImpl.begin(TransactionImpl.java:75)
	at Utils.JpaUtils.Apollo.SelectService.ApolloUpdateDbService.updatePartnership(ApolloUpdateDbService.java:27)
	at CucumberTests.Hooks.rollbackVerificationEmailSettingAfterTest(Hooks.java:547)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 246ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

After Hooks.cleanUserDetailsAfterTest() 148ms

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 218ms

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Nie otrzymano zlecenia" 3m 14s 429ms

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/AuctionMail.feature:25)

Hooks

After Hooks.deleteTransportAfterTest() 080ms

After Hooks.cleanUserDetailsAfterTest() 107ms

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

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

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

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

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

And Wait till auction end 1m 58s 019ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Dodano nową ofertę" 3m 13s 012ms

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/AuctionMail.feature:39)

Hooks

After Hooks.deleteTransportAfterTest() 124ms

After Hooks.cleanUserDetailsAfterTest() 137ms

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 234ms

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

And Wait till auction end 1m 58s 023ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Aukcja zakończona bez ofert" 3m 15s 512ms

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/AuctionMail.feature:52)

Hooks

After Hooks.deleteTransportAfterTest() 119ms

After Hooks.cleanUserDetailsAfterTest() 110ms

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 262ms

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Oferta przelicytowana" 3m 12s 300ms

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/AuctionMail.feature:66)

Hooks

After Hooks.deleteTransportAfterTest() 111ms

After Hooks.cleanUserDetailsAfterTest() 121ms

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 204ms

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Otrzymano zlecenie" 3m 14s 710ms

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/AuctionMail.feature:79)

Hooks

After Hooks.deleteTransportAfterTest() 085ms

After Hooks.cleanUserDetailsAfterTest() 098ms

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 243ms

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

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

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

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/AuctionMail.feature:93)

Hooks

After Hooks.deleteTransportAfterTest() 108ms

After Hooks.cleanUserDetailsAfterTest() 111ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail two hours before auction ends

Steps

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 219ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes 2s 114ms

And Wait "90" seconds 1m 30s

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zakończenie aukcji" 3m 13s 199ms

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/AuctionMail.feature:106)

Hooks

After Hooks.deleteTransportAfterTest() 129ms

After Hooks.cleanUserDetailsAfterTest() 103ms

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 602ms

And Go to "TRANSPORT_TABLE" 129ms

And Go to transport details "DELIVERY" 4s 477ms

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

And Fill transport form 35s 495ms

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

And Fill discrepancy report section 35s 515ms

And Go to transport details "DELIVERY" 4s 409ms

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

And Generate discrepancy report 17s 725ms

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

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

After Hooks.cleanUserDetailsAfterTest() 132ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackAddedAuthorities

Scenario Outline Check if mail was sent to after transport delay

Steps

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

And Prepare user "pha2-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 349ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 115ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 457ms

And Go to "WAREHOUSE_TAB" 750ms

And Select warehouse "Serownia" 1s 363ms

And Set week view 1s 080ms

And Show yesterday 1s 053ms

And Move window into the past 280ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "spóźnił się na" 3m 16s 523ms

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/TransportMail.feature:15)

Hooks

After Hooks.deleteTransportAfterTest() 126ms

After Hooks.cleanUserDetailsAfterTest() 275ms

After Hooks.rollbackAddedAuthorities() 052ms

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Drobnica import" 3m 22s 596ms

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/TransportMail.feature:26)

Hooks

After Hooks.deleteTransportAfterTest() 099ms

After Hooks.cleanUserDetailsAfterTest() 152ms

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

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

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

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

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/TransportMail.feature:26)

Hooks

After Hooks.deleteTransportAfterTest() 117ms

After Hooks.cleanUserDetailsAfterTest() 134ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 205ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zlecenie czeka na akceptację" 3m 14s 045ms

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/TransportTransferMail.feature:10)

Hooks

After Hooks.deleteTransportAfterTest() 112ms

After Hooks.cleanUserDetailsAfterTest() 105ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 237ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zostało przekazane nowe zlecenie" 3m 19s 803ms

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/TransportTransferMail.feature:22)

Hooks

After Hooks.deleteTransportAfterTest() 094ms

After Hooks.cleanUserDetailsAfterTest() 108ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

And Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 125ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zlecenie czeka na akceptację" 3m 14s 449ms

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/TransportTransferMail.feature:34)

Hooks

After Hooks.deleteTransportAfterTest() 134ms

After Hooks.cleanUserDetailsAfterTest() 262ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing inquiry

Steps

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

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

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

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

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

And Add a bid "500" to an auction by JSON file as "pskza2-carrier-2@qa.qa-test" for "pskza2-carrier-2@qa.qa-test" 297ms

Then If user is login then logout 277ms

And Login as "swisskrono-admin" 1s 365ms

And Go to auction details 1s 179ms

And Pass transport to carrier from auction details 1s 268ms

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nie otrzymano zlecenia" 3m 16s 596ms

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/TransportTransferMail.feature:52)

Hooks

After Hooks.deleteTransportAfterTest() 142ms

After Hooks.cleanUserDetailsAfterTest() 195ms

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

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

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

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

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nowe zapytanie ofertowe" 3m 15s 875ms

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/TransportTransferMail.feature:64)

Hooks

After Hooks.deleteTransportAfterTest() 095ms

After Hooks.cleanUserDetailsAfterTest() 144ms

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

And Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 1s 138ms

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

And Fill transport form 40s 712ms

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

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

And Set advice window in schedule 2s 160ms

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 15s 442ms

And Go to "TRANSPORT_TABLE" 218ms

And Show all transport "false" 006ms

And Go to transport details "DELIVERY" 32s 455ms

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

And Click "save-transport" save button 682ms

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

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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

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

And Set status of MOT to "AWAITING_VERIFICATION" 064ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 285ms

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

When Login as "super-admin-bausch" 1s 556ms

And Go to "TRANSPORT_TABLE" 195ms

And Click button advice in transport table "LOAD_PL" 084ms

And Set advice window in schedule 2s 880ms

Then Check if "AAAA0000" MOT is NOT visible in advice form 15s 384ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

After Hooks.deleteModeOfTransportationAfterTest() 071ms

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

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

And Set status of MOT to "DISABLED" 078ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 234ms

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

When Login as "super-admin-bausch" 1s 155ms

And Go to "TRANSPORT_TABLE" 219ms

And Click button advice in transport table "LOAD_PL" 088ms

And Set advice window in schedule 2s 822ms

Then Check if "AAAA0000" MOT is NOT visible in advice form 15s 413ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

After Hooks.deleteModeOfTransportationAfterTest() 078ms

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

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

And Set status of MOT to "ACCEPTED" 070ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 259ms

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

When Login as "super-admin-bausch" 1s 129ms

And Go to "TRANSPORT_TABLE" 206ms

And Click button advice in transport table "LOAD_PL" 088ms

And Set advice window in schedule 2s 850ms

Then Check if "AAAA0000" MOT can be selected in advice form 390ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

After Hooks.deleteModeOfTransportationAfterTest() 081ms

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

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

And Set status of MOT to "UPDATED" 069ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 191ms

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

When Login as "super-admin-bausch" 1s 082ms

And Go to "TRANSPORT_TABLE" 228ms

And Click button advice in transport table "LOAD_PL" 090ms

And Set advice window in schedule 3s 042ms

Then Check if "AAAA0000" MOT can be selected in advice form 350ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

After Hooks.deleteModeOfTransportationAfterTest() 089ms

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

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

And Set status of MOT to "REJECTED" 068ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 227ms

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

When Login as "super-admin-bausch" 1s 119ms

And Go to "TRANSPORT_TABLE" 246ms

And Click button advice in transport table "LOAD_PL" 105ms

And Set advice window in schedule 2s 960ms

Then Check if "AAAA0000" MOT is visible in advice form 355ms

And Check if "AAAA0000" MOT cannot be selected in advice form 084ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

After Hooks.deleteModeOfTransportationAfterTest() 087ms

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

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

And Set status of MOT to "BLOCKED" 074ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 253ms

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

When Login as "super-admin-bausch" 1s 117ms

And Go to "TRANSPORT_TABLE" 197ms

And Click button advice in transport table "LOAD_PL" 084ms

And Set advice window in schedule 2s 972ms

Then Check if "AAAA0000" MOT is visible in advice form 345ms

And Check if "AAAA0000" MOT cannot be selected in advice form 114ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

After Hooks.deleteModeOfTransportationAfterTest() 088ms

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

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

And Add transport by SKApi in "MGW" 172ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 36s 148ms

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

And Set advice window in schedule 2s 597ms

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

And Fill advice form 14s 384ms

And Click advice save button and wait for advice form to disappear 31s 188ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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

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

When Add transport by SKApi in "MGW" 002ms

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

And Go to "TRANSPORT_TABLE" 116ms

And Go to transport details "TRANSPORT_ORDER" 4s 433ms

Then Check are transport values equals 371ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

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

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

When Add transport by SKApi in "MGW" 002ms

Then Check is transport "CONTAINER" created in transport table and set transport id 54s 358ms

And Go to "TRANSPORT_TABLE" 120ms

And Go to transport details "CONTAINER" 4s 419ms

Then Check are transport values equals 339ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

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

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

When Add transport by SKApi in "MGW" 003ms

Then Check is transport "OWN_COLLECTION" created in transport table and set transport id 54s 442ms

And Go to "TRANSPORT_TABLE" 117ms

And Go to transport details "OWN_COLLECTION" 4s 425ms

Then Check are transport values equals 349ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

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

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

When Add transport by SKApi in "HRL" 002ms

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

And Go to "TRANSPORT_TABLE" 117ms

And Go to transport details "TRANSPORT_ORDER" 4s 404ms

Then Check are transport values equals 336ms

Hooks

After Hooks.deleteTransportAfterTest() 058ms

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

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

When Add transport by SKApi in "HRL" 003ms

Then Check is transport "CONTAINER" created in transport table and set transport id 54s 396ms

And Go to "TRANSPORT_TABLE" 126ms

And Go to transport details "CONTAINER" 4s 434ms

Then Check are transport values equals 331ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

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

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

When Add transport by SKApi in "HRL" 003ms

Then Check is transport "OWN_COLLECTION" created in transport table and set transport id 54s 415ms

And Go to "TRANSPORT_TABLE" 122ms

And Go to transport details "OWN_COLLECTION" 4s 416ms

Then Check are transport values equals 351ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

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

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

And Set another client name "Pepsi" 000ms

When Add transport by SKApi in "MGW" 002ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 54s 284ms

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

Hooks

After Hooks.deleteTransportAfterTest() 065ms

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

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

When Add transport by SKApi in "" 002ms

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

And Go to "TRANSPORT_TABLE" 119ms

And Go to transport details "TRANSPORT_ORDER" 4s 392ms

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

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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

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

And Add transport by SKApi in "MGW" 002ms

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

And Check is transport "CONTAINER" created in transport table and set transport id 54s 402ms

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

And Set advice window in schedule 2s 663ms

And Fill advice form 14s 360ms

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

And Go to "TRANSPORT_TABLE" 170ms

And Go to transport details "CONTAINER" 4s 575ms

Then Check are advice values equals 2s 279ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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

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

And Add transport by SKApi in "MGW" 002ms

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

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 339ms

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

And Set advice window in schedule 2s 676ms

And Fill advice form 14s 413ms

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

And Go to "TRANSPORT_TABLE" 184ms

And Go to transport details "OWN_COLLECTION" 4s 442ms

Then Check are advice values equals 2s 282ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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

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

And Add transport by SKApi in "MGW" 002ms

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

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 792ms

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

And Set advice window in schedule 2s 652ms

And Fill advice form 14s 450ms

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

And Go to "TRANSPORT_TABLE" 225ms

And Go to transport details "TRANSPORT_ORDER" 4s 523ms

Then Check are advice values equals 2s 263ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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

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

And Add transport by SKApi in "MGW" 002ms

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

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 6s 341ms

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

And Set advice window in schedule 2s 542ms

And Fill advice form 14s 501ms

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

And Go to "TRANSPORT_TABLE" 157ms

Then Check advice data in SK API database "OWN_COLLECTION" 2s 153ms

Hooks

After Hooks.deleteTransportAfterTest() 188ms

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

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

And Add transport by SKApi in "MGW" 023ms

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

And Check is transport "CONTAINER" created in transport table and set transport id 6s 329ms

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

And Set advice window in schedule 2s 542ms

And Fill advice form 14s 466ms

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

And Go to "TRANSPORT_TABLE" 172ms

Then Check advice data in SK API database "CONTAINER" 4s 110ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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

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

And Add transport by SKApi in "MGW" 003ms

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

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 6s 209ms

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

And Set advice window in schedule 2s 568ms

And Fill advice form 14s 424ms

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

And Go to "TRANSPORT_TABLE" 213ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 4s 052ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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

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

And Add transport by SKApi in "MGW" 002ms

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

And Check is transport "CONTAINER" created in transport table and set transport id 6s 282ms

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

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

And Fill advice form 14s 453ms

And Click advice save button to check error message 079ms

Then Check if possible advice alert is displayed 038ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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

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

And Add transport by SKApi in "MGW" 002ms

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

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 42s 956ms

And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 47s 872ms

And Go to "TRANSPORT_TABLE" 179ms

When Go to transport details "OWN_COLLECTION" 4s 483ms

And Expand advice panel 088ms

And Edit advice in transport details 13s 892ms

And Fill arrival date field 2s 279ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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

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

And Add transport by SKApi in "MGW" 004ms

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

And Check is transport "CONTAINER" created in transport table and set transport id 33s 420ms

And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 47s 825ms

And Go to "TRANSPORT_TABLE" 185ms

When Go to transport details "CONTAINER" 4s 439ms

And Expand advice panel 098ms

And Edit advice in transport details 13s 857ms

And Fill arrival date field 2s 242ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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

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

And Add transport by SKApi in "MGW" 002ms

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

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 33s 881ms

And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 47s 825ms

And Go to "TRANSPORT_TABLE" 234ms

When Go to transport details "TRANSPORT_ORDER" 4s 522ms

And Expand advice panel 093ms

And Edit advice in transport details 13s 841ms

And Fill arrival date field 2s 267ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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

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

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

When Go to "WAREHOUSE_TAB" 815ms

And Select warehouse "Twarożkarnia wyrób gotowy" 1s 913ms

And Select view "DAYS_2" 2s 059ms

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

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

And Select view "DAYS_2" 2s 041ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 156ms

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

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

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

When Go to "WAREHOUSE_TAB" 762ms

And Select warehouse "Twarożkarnia wyrób gotowy" 1s 889ms

And Select view "DAYS_2" 2s 094ms

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

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

And Select view "DAYS_2" 2s 035ms

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 156ms

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

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

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

When Go to "WAREHOUSE_TAB" 825ms

And Select warehouse "Twarożkarnia wyrób gotowy" 1s 902ms

And Select view "DAYS_2" 2s 077ms

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

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

And Select view "DAYS_2" 2s 040ms

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 131ms

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

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

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

When Go to "WAREHOUSE_TAB" 406ms

And Select warehouse "MGW" 1s 170ms

And Select view "DAYS_2" 2s 065ms

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

And Select warehouse "HRL" 1s 374ms

And Select view "DAYS_2" 2s 046ms

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 107ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 425ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 114ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 1s 496ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 538ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 102ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 098ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 269ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 108ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 245ms

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

And Confirm statuses until reach "departed" 24s 288ms

Then Check if transport has "departed" 018ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 092ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 256ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 075ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 061ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 247ms

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

And Confirm statuses until reach "process-ended" 29s 597ms

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

Hooks

After Hooks.deleteTransportAfterTest() 174ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 307ms

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

And Confirm statuses until reach "process-ended" 26s 815ms

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

Hooks

After Hooks.deleteTransportAfterTest() 082ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 271ms

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

And Confirm statuses until reach "process-ended" 26s 881ms

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

Hooks

After Hooks.deleteTransportAfterTest() 102ms

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

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

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

When Accept or reject "accept" transferred transport 17s 991ms

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

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

And Set advice window in schedule 2s 807ms

And Fill advice form 14s 361ms

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

And Check if window is "silver" 2s 029ms

And Go to "TRANSPORT_TABLE" 179ms

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

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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

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

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

When Accept or reject "accept" transferred transport 17s 984ms

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

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

And Set advice window in schedule 2s 646ms

And Fill advice form 14s 414ms

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

And Check if window is "silver" 2s 028ms

And Go to "TRANSPORT_TABLE" 194ms

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

Hooks

After Hooks.deleteTransportAfterTest() 107ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAddedActionAuthorities

Scenario Outline Check if it is not possible to edit advice after reach specific status

Steps

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 405ms

When Login as "hochland-admin" 2s 242ms

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

And Confirm statuses until reach "arrived" 3s 804ms

And Go to transport details "DELIVERY" 4s 663ms

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

Hooks

After Hooks.deleteTransportAfterTest() 098ms

After Hooks.rollbackAddedActionAuthorities() 051ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check is transport color changed after confirm status

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 305ms

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

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

And Confirm statuses until reach "arrived" 3s 794ms

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

And Confirm statuses until reach "during-unload" 3s 698ms

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

And Confirm statuses until reach "unloaded" 3s 725ms

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

And Confirm statuses until reach "process-ended" 18s 760ms

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

Hooks

After Hooks.deleteTransportAfterTest() 098ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to confirm statuses before add file to transport

Steps

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

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

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

And Show all transport types 1s 039ms

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

And Set advice window in schedule 2s 559ms

And Fill advice form 8s 304ms

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

And Go to "TRANSPORT_TABLE" 209ms

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

And Confirm statuses until reach "left-the-area" 17s 366ms

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

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to confirm statuses before add file to transport

Steps

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

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

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

And Show all transport types 1s 035ms

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

And Set advice window in schedule 2s 535ms

And Fill advice form 8s 170ms

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

And Go to "TRANSPORT_TABLE" 182ms

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

And Confirm statuses until reach "left-the-area" 17s 316ms

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

Hooks

After Hooks.deleteTransportAfterTest() 084ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if it is possible to confirm statuses after add file to transport

Steps

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

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

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

And Show all transport types 1s 040ms

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

And Set advice window in schedule 2s 620ms

And Fill advice form 8s 209ms

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

And Go to "TRANSPORT_TABLE" 245ms

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

When Add file to transport by API 600ms

And Confirm statuses until reach "process-ended" 35s 008ms

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

Hooks

After Hooks.deleteTransportAfterTest() 078ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check if it is possible to confirm statuses after add file to transport

Steps

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

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

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

And Show all transport types 1s 041ms

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

And Set advice window in schedule 2s 534ms

And Fill advice form 8s 213ms

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

And Go to "TRANSPORT_TABLE" 184ms

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

When Add file to transport by API 293ms

And Confirm statuses until reach "process-ended" 35s 008ms

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

Hooks

After Hooks.deleteTransportAfterTest() 086ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 1s 254ms

And Confirm status "REPORTING" by Public API "v1" 052ms

And Confirm status "ARRIVAL" by Public API "v1" 097ms

And Login as "swiss-krono-delivery-guard" 1s 186ms

And Go to "TRANSPORT_TABLE" 180ms

When Confirm "Departure" status in transport row 3s 088ms

Then Verify that "Departure" has been confirmed 029ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

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

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 414ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 186ms

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 709ms

And Login as "bausch-admin" 1s 187ms

And Go to "TRANSPORT_TABLE" 228ms

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

When Confirm statuses until reach "on-the-way" 9s 189ms

And Open statuses popup 066ms

And Toggle status date confirmation checkbox 265ms

And Confirm statuses until reach "process-ended" 18s 736ms

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

Hooks

After Hooks.deleteTransportAfterTest() 096ms

After Hooks.deleteModeOfTransportationAfterTest() 079ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

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

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 275ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 210ms

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 697ms

And Login as "bausch-admin" 1s 115ms

And Go to "TRANSPORT_TABLE" 219ms

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

When Confirm statuses until reach "on-the-way" 9s 191ms

And Open statuses popup 049ms

And Toggle status date confirmation checkbox 265ms

And Change status execution date to "1" days from today 2s 163ms

Then Verify that status cannot be confirmed 1s 078ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

After Hooks.deleteModeOfTransportationAfterTest() 055ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

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

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 298ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 186ms

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 688ms

And Login as "bausch-admin" 1s 051ms

And Go to "TRANSPORT_TABLE" 138ms

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

When Confirm statuses until reach "on-the-way" 9s 182ms

And Open statuses popup 053ms

And Toggle status date confirmation checkbox 268ms

And Change status execution date to "-1" days from today 2s 167ms

Then Verify that status cannot be confirmed 1s 082ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

After Hooks.deleteModeOfTransportationAfterTest() 048ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackTaskChanges

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

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 189ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 635ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 018ms

When Login as "farmacol-admin" 1s 547ms

And Go to "TRANSPORT_TABLE" 183ms

And Confirm statuses until reach "during-unload" 9s 339ms

And Set actual confirmed transport status list 1s 337ms

And Disable task by API 034ms

And Go to transport details "EXTERNAL_DELIVERY" 4s 408ms

And Edit transport hours and recalculate statuses 15s 762ms

Then Verify that all confirmed statuses are still on transport status list 175ms

Hooks

After Hooks.deleteTransportAfterTest() 137ms

After Hooks.rollbackTaskChanges() 021ms

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

And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 215ms

And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 1s 154ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 325ms

And Check if reject date is not visible 15s 053ms

When Reject status: Book of disinfection 072ms

And Check if reject date is visible 325ms

Then If user is login then logout 066ms

And Login as "lantmannen-admin" 1s 238ms

And Check if note was added to transport after status rejection 1s 226ms

And Check if history note was added to transport after status rejection - "LOAD" 5s 429ms

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nieaktualna księga mycia i dezynfekcji" 7s 460ms

And Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

After Hooks.cleanUserDetailsAfterTest() 150ms

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

And Create transport "CREATE_LOAD_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 249ms

And Check if reject date is not visible 15s 042ms

When Reject status: Book of disinfection 074ms

And Check if reject date is visible 144ms

And Get rejection date 021ms

And Wait "60" seconds 1m

And Reject status: Book of disinfection 050ms

Then Check if reject date has changed 1s 071ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 256ms

And Go to transport details "LOAD" 4s 324ms

And Check if reject date is not visible 15s 059ms

When Reject status: Book of disinfection 068ms

Then Check if reject date is visible 085ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 268ms

And Open statuses popup 100ms

And Check if reject date is not visible 15s 010ms

When Reject status: Book of disinfection 069ms

Then Open statuses popup 042ms

And Check if reject date is visible 081ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 302ms

And Confirm to the last status by API 165ms

When Find statuses for transport in table 1s 967ms

And Revoke statuses until reach "advice-added" 6s 732ms

Then Check if transport has "advice-added" 019ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 262ms

And Confirm to the last status by API 185ms

When Find statuses for transport in table 1s 661ms

And Revoke statuses until reach "planned" 6s 630ms

Then Check if transport has "planned" 021ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 178ms

When Find transport in table with status "new" 3s 192ms

And Open statuses popup 081ms

Then Check if transport has checkpoints from list "Utworzenie zlecenia,Dodanie awizacji,Potwierdzenie okna czasowego" in "0" 055ms

Hooks

After Hooks.deleteTransportAfterTest() 047ms

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

And Get inputs from database "ADVICE_EXTERNAL_DELIVERY" "super-admin-farmacol" 002ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 155ms

And Click button advice in transport table "EXTERNAL_DELIVERY" 093ms

And Set advice window in schedule 2s 649ms

And Fill advice form 11s 810ms

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

And Go to "TRANSPORT_TABLE" 234ms

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

And Open statuses popup 089ms

Then Check if transport has checkpoints from list "Zgłoszenie kierowcy,Rozpoczęcie rozładunku,Zakończenie rozładunku" in "1" 083ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

View Feature Status

@deleteTransportAfterTest @rollbackTaskChanges

Scenario Outline Check if deleted task is not in new transports' workflow @A-6875

Steps

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

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 189ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 632ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 016ms

When Login as "farmacol-admin" 1s 021ms

And Go to "TRANSPORT_TABLE" 201ms

And Confirm statuses until reach "registered-katowice-przyjęcia" 6s 619ms

And Disable task by API 028ms

And Find transport pencil button in transports table 1s 207ms

And Click pencil and move transport to next day in schedule 18s 163ms

And Go to "TRANSPORT_TABLE" 234ms

Then Verify that "START_OF_UNLOADING" is not visible 120ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

After Hooks.rollbackTaskChanges() 033ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 483ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 061ms

When Go to "WAREHOUSE_TAB" 787ms

And Select warehouse "Serownia" 1s 445ms

And Set week view 1s 116ms

And Show yesterday 1s 043ms

And Move window into the past 282ms

Then Check if window is "red" 2s 018ms

Hooks

After Hooks.deleteTransportAfterTest() 141ms

After Hooks.rollbackAddedAuthorities() 067ms

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 317ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "lantmannen-admin" 033ms

When Go to "WAREHOUSE_TAB" 637ms

And Select warehouse "Magazyn - Nowa Sól" 2s 141ms

And Set week view 1s 100ms

And Show yesterday 1s 056ms

And Move window into the past 394ms

Then Check if window is "red" 2s 026ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

After Hooks.rollbackAddedAuthorities() 024ms

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

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

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "piast-admin" 049ms

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

When Show all transport types 1s 031ms

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

And Set advice window in schedule 2s 640ms

And Fill advice form 8s 260ms

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

And Select warehouse "Magazyn Hala A" 1s 186ms

And Set week view 2s 095ms

And Show yesterday 1s 150ms

And Move window into the past 527ms

Then Check if window is "red" 2s 048ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

After Hooks.rollbackAddedAuthorities() 021ms

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

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 002ms

And Set algorithm setting for "super-admin-hochland" in "Magazyn Zimny Kaźmierz" on "Magazyn Zimny" 507ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 396ms

When Go to "WAREHOUSE_TAB" 771ms

And Select warehouse "Magazyn Zimny Kaźmierz" 1s 764ms

And Set week view 1s 096ms

And Check if time window length is correct after "CREATE" 024ms

And Change number of pallets in transport 52s 488ms

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

And Check if time window length is correct after "EDIT" 023ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackTransportTypeSettings

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

And Get "UNLOAD" settings from "keeeper" 027ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 089ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;true" 099ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 368ms

When Go to "WAREHOUSE_TAB" 287ms

And Select warehouse "Magazyn Surowców" 1s 195ms

And Set week view 1s 083ms

Then Check if time window has proper "60" 028ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

After Hooks.rollbackTransportTypeSettings() 045ms

After Hooks.clearAlgorithmSettings() 103ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackTransportTypeSettings

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

And Get "UNLOAD" settings from "keeeper" 028ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 076ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;false" 055ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 304ms

When Go to "WAREHOUSE_TAB" 284ms

And Select warehouse "Magazyn Surowców" 1s 199ms

And Set week view 1s 081ms

Then Check if time window has proper "60" 016ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

After Hooks.rollbackTransportTypeSettings() 047ms

After Hooks.clearAlgorithmSettings() 063ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackTransportTypeSettings

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

And Get "LOAD" settings from "keeeper" 025ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 072ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;false" 052ms

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

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

And Show all transport types 1s 041ms

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

And Set advice window in schedule 2s 434ms

And Fill advice form 12s 972ms

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

Then Check if time window has proper "30" 018ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

After Hooks.rollbackTransportTypeSettings() 053ms

After Hooks.clearAlgorithmSettings() 074ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackTransportTypeSettings

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

And Get "CONTAINER" settings from "keeeper" 024ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 076ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "20;false" 050ms

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

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

And Show all transport types 1s 034ms

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

And Set advice window in schedule 2s 412ms

And Fill advice form 13s 133ms

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

Then Check if time window has proper "60" 024ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

After Hooks.rollbackTransportTypeSettings() 047ms

After Hooks.clearAlgorithmSettings() 071ms

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

And Set algorithm setting for "super-admin-hochland" in "Serownia" on "Magazyn Sera" 105ms

And Set token of apiUsername "dha1-supplier-2@qa.qa-test" 107ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 15s 258ms

And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "super-admin-hochland" 2s 249ms

When Go to transport details "DELIVERY" 32s 603ms

And Change filled value in transport details "quantity" "number" "25" "0" 1s 332ms

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

And Go to "WAREHOUSE_TAB" 760ms

And Select warehouse "Serownia" 1s 419ms

And Set week view 1s 084ms

Then Check if time window has proper "60" 022ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

After Hooks.clearAlgorithmSettings() 124ms

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

And Set basic authorities "ROLE_ACCESS_TO_NUMBER_OF_WINDOWS" to user "keeeper-admin" 034ms

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

When Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 46s 161ms

And Check if time window counter value equals "1" 056ms

And Select view "DAYS_2" 2s 080ms

And Move advice window "2" 1s 365ms

And Select view "DAY" 2s 070ms

Then Check if time window counter value equals "0" 058ms

And Delete created transport by API 097ms

And Check if time window counter value equals "0" 051ms

And Click in free spot in schedule page to create gray window 170ms

And Check if time window counter value equals "0" 040ms

And Click in free spot in schedule page to create dedicated window 039ms

And Check if time window counter value equals "0" 049ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

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

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 158ms

When Go to new transport "DELIVERY" 230ms

And Fill transport form 11s 293ms

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

And Set advice window in schedule 2s 194ms

And Check is transport created in schedule and set transport id 433ms

And Go to "TRANSPORT_TABLE" 196ms

When Click on time window date 1s 314ms

And Open transport form when in schedule 1s 126ms

Then Check are transport values equals 122ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 469ms

When Go to new transport "DELIVERY" 408ms

And Fill transport form 38s 575ms

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

And Set advice window in schedule 2s 153ms

And Check is transport created in schedule and set transport id 593ms

And Go to "TRANSPORT_TABLE" 196ms

When Click on time window date 1s 245ms

And Open transport form when in schedule 1s 282ms

Then Check are transport values equals 19s 320ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

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

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 384ms

When Go to new transport "CISTERN_DELIVERY" 389ms

And Fill transport form 21s 584ms

Error message

java.lang.AssertionError: Nie można wypełnić pola warehouse, ponieważ nie udało się go znaleźć w formularzu
	at org.junit.Assert.fail(Assert.java:88)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:152)
	at CucumberTests.Transport.CreateTransport.fillTransportForm(CreateTransport.java:170)
	at ✽.Fill transport form(file:Features/Atom/TimeWindow/TransportWindow.feature:175)

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

And Set advice window in schedule 000ms

And Check is transport created in schedule and set transport id 000ms

And Go to "TRANSPORT_TABLE" 000ms

When Click on time window date 000ms

And Open transport form when in schedule 000ms

Then Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 001ms

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

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 418ms

When Go to new transport "CISTERN_COLLECTION" 309ms

And Fill transport form 28s 106ms

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

And Set advice window in schedule 2s 189ms

And Check is transport created in schedule and set transport id 453ms

And Go to "TRANSPORT_TABLE" 182ms

When Click on time window date 1s 382ms

And Open transport form when in schedule 1s 235ms

Then Check are transport values equals 21s 278ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 336ms

When Go to new transport "DELIVERY" 314ms

And Fill transport form 37s 668ms

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

And Set advice window in schedule 2s 147ms

And Check is transport created in schedule and set transport id 553ms

And Go to "TRANSPORT_TABLE" 178ms

When Click on time window date 1s 298ms

And Open transport form when in schedule 1s 148ms

Then Check are transport values equals 19s 291ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 078ms

When Go to new transport "LOAD" 303ms

And Fill transport form 37s 615ms

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

And Set advice window in schedule 2s 136ms

And Check is transport created in schedule and set transport id 522ms

And Go to "TRANSPORT_TABLE" 212ms

When Click on time window date 1s 345ms

And Open transport form when in schedule 1s 133ms

Then Check are transport values equals 19s 323ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 097ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 063ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 093ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 195ms

And Login as "farmacol-admin" 1s 503ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 45s 525ms

And Go to "TRANSPORT_TABLE" 287ms

When Go to transport details "EXTERNAL_DELIVERY" 4s 446ms

And Add step "unload" 105ms

And Change filled value in transport details "warehouse-select-step-2" "select" "Mory Przyjęcia" "0" 3s 425ms

And Change filled value in transport details "weight-step-2" "number" "23" "0" 1s 334ms

And Change filled value in transport details "number-of-pallets-step-2" "number" "23" "0" 1s 335ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 254ms

Then Click "save-transport" save button 173ms

And Set advice window in schedule in "2" days 5s 062ms

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

And Go to "TRANSPORT_TABLE" 220ms

And Check if transport has "2" time windows 014ms

Hooks

After Hooks.deleteTransportAfterTest() 165ms

After Hooks.rollbackTransportTypeSettings() 066ms

After Hooks.rollbackAddedActionAuthorities() 048ms

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

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 033ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 048ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 175ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 513ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 723ms

And Go to "TRANSPORT_TABLE" 249ms

And Get checkpoint colors for transport 004ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "true" 42s 396ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

After Hooks.rollbackTransportTypeSettings() 093ms

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

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 029ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 056ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 214ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 183ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 628ms

And Go to "TRANSPORT_TABLE" 306ms

And Get checkpoint colors for transport 003ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "false" 42s 353ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

After Hooks.rollbackTransportTypeSettings() 050ms

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

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 031ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 065ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 218ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 013ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 650ms

And Get checkpoint colors for transport 005ms

And Go to "TRANSPORT_TABLE" 270ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true" 5s 850ms

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

After Hooks.rollbackTransportTypeSettings() 139ms

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

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 027ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 058ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 15s 192ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 199ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 474ms

And Get checkpoint colors for transport 004ms

And Go to "TRANSPORT_TABLE" 293ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "false" 7s 660ms

Error message

org.openqa.selenium.StaleElementReferenceException: stale element reference: element is not attached to the page document
  (Session info: headless chrome=90.0.4430.93)
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: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.zAPrEe}, 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=90.0.4430.93, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 4d6287096dfe598f5ebe874fc309261b
	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.getCssValue(RemoteWebElement.java:165)
	at CucumberTests.TimeWindow.TimeWindowTest.checkIfWindowsHasProperColorsInSchedule(TimeWindowTest.java:177)
	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 "false"(file:Features/Atom/TimeWindow/TransportWindow.feature:247)

Hooks

After Hooks.deleteTransportAfterTest() 122ms

After Hooks.rollbackTransportTypeSettings() 054ms

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

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 199ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 709ms

And Login as "super-admin-farmacol" 1s 709ms

And Show all transport types 1s 141ms

And Click on time window date 1s 612ms

Then Open transport form when in schedule 1s 356ms

And Click create similar button 15s 192ms

And Click cancel button in transport form 085ms

And Open transport form when in schedule 1s 200ms

Then Check if transport form modal is visible 037ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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

And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 002ms

And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 029ms

And Set proper delay time to move order to archive after task timeout 033ms

When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 266ms

And Go to "WAREHOUSE_TAB" 614ms

And Change warehouse in schedule to: "Katowice" 1s 120ms

And Wait "60" seconds 1m

And Verify that transport window is grey 028ms

And Verify that transport is in archive 1s 055ms

Then Restore transport from archive 1s 094ms

And Verify that transport has been successfully restored 15s 242ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

After Hooks.rollbackSettings() 020ms

View Feature Move transport to archive

@deleteTransportAfterTest @rollbackSettings

Scenario Outline Check if confirming transport status removed it to the archive

Steps

Given Login as "dayco-admin" and set token of apiUsername "super-admin-dayco" 1s 091ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 162ms

And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 028ms

And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 000ms

Error message

java.lang.IllegalStateException: Transaction already active
	at org.hibernate.engine.transaction.internal.TransactionImpl.begin(TransactionImpl.java:75)
	at Utils.JpaUtils.Apollo.SelectService.ApolloUpdateDbService.setCompanySettingsByName(ApolloUpdateDbService.java:20)
	at CucumberTests.Settings.SettingsTest.prepareSettingWithValueWith(SettingsTest.java:55)
	at ✽.Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco"(file:Features/Atom/Transport/Archive.feature:39)

When Go to "TRANSPORT_TABLE" 000ms

And Click button advice in transport table "OWN_COLLECTION" 000ms

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 000ms

And Go to "TRANSPORT_TABLE" 000ms

And Find transport in table with status "planned-magazyn-tychy" 000ms

And Confirm statuses until reach "process-ended" 000ms

And Wait "12" seconds 000ms

Then Go to "ARCHIVE_TAB" 000ms

And Show "OWN_COLLECTION" 000ms

And Verify that created transport is "true" in transport table 000ms

Hooks

After Hooks.deleteTransportAfterTest() 053ms

After Hooks.rollbackSettings() 016ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 211ms

When Fill auction form 15s 437ms

Then Verify that the auction has been added to transport 052ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

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

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

When Fill auction form 15s 373ms

Then Verify that the auction has been added to transport 037ms

Hooks

After Hooks.deleteTransportAfterTest() 063ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 191ms

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

When If user is login then logout 098ms

And Login as "paa1-carrier@qa.qa-test" 1s 552ms

And Go to auction offer 1s 207ms

And Accept transport with minimum rate 15s 613ms

Then Check if carrier is assigned to transport 021ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 185ms

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

When If user is login then logout 281ms

And Login as "paa1-carrier@qa.qa-test" 1s 354ms

And Go to auction offer 1s 202ms

And Reject auction offer 15s 614ms

Then Verify that offer has been removed from transport 15s 018ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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

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

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

When If user is login then logout 232ms

And Login as "pskza1-carrier@qa.qa-test" 1s 069ms

And Go to auction offer 1s 240ms

And Reject auction offer 15s 618ms

Then Verify that offer has been removed from transport 15s 053ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 187ms

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

When If user is login then logout 255ms

And Login as "paa1-carrier@qa.qa-test" 1s 246ms

And Go to auction offer 1s 252ms

And Offer prize above maximum - "20000" 132ms

Then Verify that is not possible to add offer 139ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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

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

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

When If user is login then logout 111ms

And Login as "pskza1-carrier@qa.qa-test" 1s 118ms

And Go to auction offer 1s 198ms

And Offer prize above maximum - "20000" 109ms

Then Verify that is not possible to add offer 136ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 183ms

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

And Wait till auction end 1m 58s 013ms

Then Verify that is possible to add auction 045ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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

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

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

And Wait till auction end 1m 58s 014ms

Then Verify that is possible to add auction 040ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 228ms

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

And Go to auction offer 1s 184ms

When Offer "1000" 114ms

Then Verify that offer with "1000" has been added to auction 3s 030ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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

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

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

And Go to auction offer 1s 172ms

When Offer "1000" 122ms

Then Verify that offer with "1000" has been added to auction 3s 028ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

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

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

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

And Go to auction offer 1s 210ms

When Offer "1000" 111ms

And Verify that offer with "1000" has been added to auction 3s 044ms

Then Go to auction offer 1s 141ms

And Revoke current offer 558ms

And Verify that offer has been revoked 30s 613ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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

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

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

And Go to auction offer 1s 204ms

When Offer "1000" 111ms

And Verify that offer with "1000" has been added to auction 3s 034ms

Then Go to auction offer 1s 153ms

And Offer "1500" 109ms

And Verify that offer with "1500" has been added to auction 3s 023ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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

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

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

And Go to auction offer 1s 194ms

When Offer "1000" 124ms

And Verify that offer with "1000" has been added to auction 3s 035ms

Then Login as "swisskrono-admin" 999ms

And Go to auction details 1s 195ms

And Finish active auction 045ms

And Verify that the transport has no active auction 146ms

Hooks

After Hooks.deleteTransportAfterTest() 059ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 206ms

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

And Go to auction offer 1s 202ms

When Offer "1000" 118ms

Then Verify that carrier can see current place in auction depending on the "true" role 088ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

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

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

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

And Go to auction offer 1s 173ms

When Offer "1000" 113ms

Then Verify that carrier can see current place in auction depending on the "false" role 15s 039ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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

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

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

And Go to auction offer 1s 174ms

When Offer "300" 122ms

And Verify that carrier can't add offer to auction 029ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 197ms

And Show all transport "false" 011ms

When Go to auction form 1s 221ms

Then Verify carrier selection value "false" 028ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

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

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

And Show all transport "true" 070ms

When Go to auction form 1s 175ms

Then Verify carrier selection value "true" 034ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 230ms

When Open transport auction form 166ms

And Select all companies checkbox in transport auction form 043ms

And Unselect company "PAA2" in transport auction form 052ms

And Put transport on auction 15s 152ms

And Open transport auction history 087ms

And Open participants section in transport auction history 050ms

Then Check if unselected "PAA2" is in transport auction history as participant 15s 028ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

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

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

When Open transport auction form 162ms

And Select all companies checkbox in transport auction form 064ms

And Unselect company "PSKZA2" in transport auction form 051ms

And Put transport on auction 15s 170ms

And Open transport auction history 090ms

And Open participants section in transport auction history 065ms

Then Check if unselected "PSKZA2" is in transport auction history as participant 15s 044ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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

And Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 1s 039ms

When Go to new transport "UNLOAD" 15s 233ms

And Fill transport form 16s 164ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//li//span[text()='Magazyn Rozładunków'] | //li[text()='Magazyn Rozładunków' and @role='option']"}
  (Session info: headless chrome=90.0.4430.93)
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: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.zAPrEe}, 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=90.0.4430.93, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 4d6287096dfe598f5ebe874fc309261b
*** Element info: {Using=xpath, value=//li//span[text()='Magazyn Rozładunków'] | //li[text()='Magazyn Rozładunków' and @role='option']}
	at sun.reflect.GeneratedConstructorAccessor213.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.Transport.Transport.selectValue(Transport.java:229)
	at CucumberTests.Transport.Transport.fillSelectInput(Transport.java:214)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:166)
	at CucumberTests.Transport.CreateTransport.fillTransportForm(CreateTransport.java:170)
	at ✽.Fill transport form(file:Features/Atom/Transport/CrudTransport.feature:8)

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

And Set advice window in schedule 000ms

And Check is transport created in schedule and set transport id 000ms

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "UNLOAD" 000ms

Then Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

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

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 096ms

When Go to new transport "DELIVERY" 298ms

And Fill transport form 11s 290ms

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

And Set advice window in schedule 2s 155ms

And Check is transport created in schedule and set transport id 434ms

And Go to "TRANSPORT_TABLE" 237ms

And Go to transport details "DELIVERY" 4s 297ms

Then Check are transport values equals 112ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 069ms

When Go to new transport "OWN_COLLECTION" 257ms

And Fill transport form 17s 808ms

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

And Set advice window in schedule 2s 148ms

And Check is transport created in schedule and set transport id 446ms

And Go to "TRANSPORT_TABLE" 171ms

And Go to transport details "OWN_COLLECTION" 4s 379ms

Then Check are transport values equals 148ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

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

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 625ms

When Go to new transport "DELIVERY" 414ms

And Fill transport form 38s 519ms

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

And Set advice window in schedule 2s 130ms

And Check is transport created in schedule and set transport id 504ms

And Go to "TRANSPORT_TABLE" 199ms

And Go to transport details "DELIVERY" 4s 608ms

Then Check are transport values equals 19s 349ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 383ms

When Go to new transport "CISTERN_DELIVERY" 409ms

And Fill transport form 21s 520ms

Error message

java.lang.AssertionError: Nie można wypełnić pola warehouse, ponieważ nie udało się go znaleźć w formularzu
	at org.junit.Assert.fail(Assert.java:88)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:152)
	at CucumberTests.Transport.CreateTransport.fillTransportForm(CreateTransport.java:170)
	at ✽.Fill transport form(file:Features/Atom/Transport/CrudTransport.feature:8)

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

And Set advice window in schedule 000ms

And Check is transport created in schedule and set transport id 000ms

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "CISTERN_DELIVERY" 000ms

Then Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 001ms

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

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 448ms

When Go to new transport "CISTERN_COLLECTION" 364ms

And Fill transport form 28s 067ms

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

And Set advice window in schedule 2s 221ms

And Check is transport created in schedule and set transport id 538ms

And Go to "TRANSPORT_TABLE" 163ms

And Go to transport details "CISTERN_COLLECTION" 4s 392ms

Then Check are transport values equals 21s 315ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 770ms

When Go to new transport "OWN_COLLECTION" 502ms

And Fill transport form 32s 485ms

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

And Set advice window in schedule 2s 154ms

And Check is transport created in schedule and set transport id 506ms

And Go to "TRANSPORT_TABLE" 175ms

And Go to transport details "OWN_COLLECTION" 4s 510ms

Then Check are transport values equals 19s 273ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 338ms

When Go to new transport "OWN_COLLECTION_POWDER_FACTORY" 341ms

And Fill transport form 32s 529ms

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

And Set advice window in schedule 2s 127ms

And Check is transport created in schedule and set transport id 618ms

And Go to "TRANSPORT_TABLE" 174ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 451ms

Then Check are transport values equals 4s 261ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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

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

When Go to new transport "EXPORT" 426ms

And Fill transport form 40s 325ms

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

And Set advice window in schedule 2s 144ms

And Check is transport created in schedule and set transport id 579ms

And Go to "TRANSPORT_TABLE" 180ms

And Go to transport details "EXPORT" 4s 745ms

Then Check are transport values equals 4s 322ms

Hooks

After Hooks.deleteTransportAfterTest() 134ms

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

And Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 1s 067ms

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

And Fill transport form 28s 195ms

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

And Set advice window in schedule 2s 135ms

And Check is transport created in schedule and set transport id 620ms

And Go to "TRANSPORT_TABLE" 189ms

And Go to transport details "DELIVERY" 32s 328ms

Then Check are transport values equals 36s 352ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 095ms

When Go to new transport "DELIVERY" 268ms

And Fill transport form 37s 681ms

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

And Set advice window in schedule 2s 123ms

And Check is transport created in schedule and set transport id 523ms

And Go to "TRANSPORT_TABLE" 162ms

And Go to transport details "DELIVERY" 4s 252ms

Then Check are transport values equals 19s 303ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

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

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 054ms

When Go to new transport "LOAD" 309ms

And Fill transport form 37s 630ms

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

And Set advice window in schedule 2s 136ms

And Check is transport created in schedule and set transport id 442ms

And Go to "TRANSPORT_TABLE" 220ms

And Go to transport details "LOAD" 4s 282ms

Then Check are transport values equals 19s 275ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 162ms

When Go to new transport "UNLOAD" 287ms

And Fill transport form 37s 269ms

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

And Set advice window in schedule 2s 145ms

And Check is transport created in schedule and set transport id 457ms

And Go to "TRANSPORT_TABLE" 172ms

And Go to transport details "UNLOAD" 4s 338ms

Then Check are transport values equals 21s 374ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 133ms

When Go to new transport "TANKER_GRANULATE_DELIVERY" 292ms

And Fill transport form 37s 270ms

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

And Set advice window in schedule 2s 136ms

And Check is transport created in schedule and set transport id 403ms

And Go to "TRANSPORT_TABLE" 182ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 323ms

Then Check are transport values equals 21s 385ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 147ms

When Go to new transport "DELIVERY" 295ms

And Fill transport form 22s 655ms

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

And Set advice window in schedule 2s 163ms

And Check is transport created in schedule and set transport id 486ms

And Go to "TRANSPORT_TABLE" 149ms

And Go to transport details "DELIVERY" 4s 342ms

Then Check are transport values equals 17s 256ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 370ms

When Go to new transport "WEIGHING" 303ms

And Fill transport form 13s 430ms

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

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 158ms

And Go to transport details "WEIGHING" 4s 340ms

And Check are transport values equals 2s 138ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

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

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 126ms

When Go to new transport "TRANSPORT" 366ms

And Fill transport form 26s 599ms

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

And Show all transport "false" 007ms

And Go to "TRANSPORT_TABLE" 166ms

And Go to transport details "TRANSPORT" 4s 477ms

And Check are transport values equals 6s 165ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

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

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 080ms

When Go to new transport "CONTAINER" 277ms

And Fill transport form 11s 132ms

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

And Show all transport "false" 008ms

And Go to "TRANSPORT_TABLE" 124ms

And Go to transport details "CONTAINER" 4s 330ms

And Check are transport values equals 055ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 482ms

When Go to new transport "TRANSFER_BETWEEN_WAREHOUSES" 416ms

And Fill transport form 12s 847ms

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

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 135ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 637ms

And Check are transport values equals 4s 154ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

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

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 579ms

When Go to new transport "DELIVERY" 303ms

And Fill transport form 22s 384ms

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

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 114ms

And Go to transport details "DELIVERY" 4s 524ms

And Check are transport values equals 17s 172ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 256ms

When Go to new transport "LOAD" 381ms

And Fill transport form 26s 268ms

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

And Show all transport "false" 008ms

And Go to "TRANSPORT_TABLE" 124ms

And Go to transport details "LOAD" 4s 602ms

And Check are transport values equals 2s 141ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 146ms

When Go to new transport "LOAD" 281ms

And Fill transport form 24s 453ms

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

And Show all transport "false" 005ms

And Go to "TRANSPORT_TABLE" 116ms

And Go to transport details "LOAD" 4s 333ms

And Check are transport values equals 19s 198ms

Hooks

After Hooks.deleteTransportAfterTest() 063ms

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

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 139ms

When Go to new transport "CONTAINER" 277ms

And Fill transport form 24s 465ms

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

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 147ms

And Go to transport details "CONTAINER" 4s 345ms

And Check are transport values equals 19s 175ms

Hooks

After Hooks.deleteTransportAfterTest() 059ms

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

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

When Go to new transport "SMALLS_IMPORT" 379ms

And Fill transport form 36s 122ms

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

And Show all transport "false" 008ms

And Go to "TRANSPORT_TABLE" 109ms

And Go to transport details "SMALLS_IMPORT" 4s 354ms

And Check are transport values equals 10s 351ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

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

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

When Go to new transport "SMALLS_EXPORT" 393ms

And Fill transport form 36s 094ms

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

And Show all transport "false" 006ms

And Go to "TRANSPORT_TABLE" 133ms

And Go to transport details "SMALLS_EXPORT" 4s 350ms

And Check are transport values equals 10s 337ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 077ms

When Go to new transport "TRANSPORT_ORDER" 380ms

And Fill transport form 29s 882ms

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

And Show all transport "true" 079ms

And Go to "TRANSPORT_TABLE" 127ms

And Go to transport details "TRANSPORT_ORDER" 4s 366ms

And Check are transport values equals 19s 295ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

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

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 122ms

When Go to new transport "TRANSPORT" 369ms

And Fill transport form 37s 493ms

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

And Show all transport "false" 005ms

And Go to "TRANSPORT_TABLE" 130ms

And Go to transport details "TRANSPORT" 4s 396ms

And Check are transport values equals 4s 217ms

Hooks

After Hooks.deleteTransportAfterTest() 054ms

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

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 136ms

When Go to new transport "INBOUND" 368ms

And Fill transport form 40s 757ms

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

And Show all transport "true" 083ms

And Go to "TRANSPORT_TABLE" 129ms

And Go to transport details "INBOUND" 4s 387ms

And Check are transport values equals 2s 256ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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

And Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 173ms

When Go to new transport "EXTERNAL_DELIVERY" 302ms

And Fill transport form 53s 241ms

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

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 109ms

And Go to transport details "EXTERNAL_DELIVERY" 4s 389ms

And Check are transport values equals 4s 404ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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

And Login as "dfa1-supplier" and set token of apiUsername "dfa1-supplier" 1s 839ms

When Go to new transport "EXTERNAL_DELIVERY" 15s 283ms

And Fill transport form 46s 797ms

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

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 112ms

And Go to transport details "EXTERNAL_DELIVERY" 4s 389ms

And Check are transport values equals 4s 400ms

Hooks

After Hooks.deleteTransportAfterTest() 021ms

Error message

java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <401>.

	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.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy:179)
	at io.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.putResponse(RestUtil.java:163)
	at Utils.RestUtils.RestUtil.putToApolloApi(RestUtil.java:76)
	at CucumberTests.Hooks.deleteTransportAfterTest(Hooks.java:175)
	at sun.reflect.GeneratedMethodAccessor207.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

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

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 001ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 574ms

And Show all transport "false" 008ms

When Go to transport details "UNLOAD" 32s 443ms

And Fill transport form 30s 208ms

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

And Go to transport details "UNLOAD" 32s 386ms

Then Check are transport values equals 4s 266ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 002ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 199ms

And Show all transport "false" 009ms

When Go to transport details "TRANSPORT" 4s 433ms

And Fill transport form 10s 278ms

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

And Go to transport details "TRANSPORT" 4s 405ms

Then Check are transport values equals 4s 110ms

Error message

java.lang.AssertionError: Wartości w formularzu w polu adr są niepoprawne, wartość na stronie: Tak wartość poprawna: Nie
	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:261)
	at CucumberTests.Transport.CreateTransport.checkTransportValues(CreateTransport.java:225)
	at ✽.Check are transport values equals(file:Features/Atom/Transport/CrudTransport.feature:76)

Hooks

After Hooks.deleteTransportAfterTest() 070ms

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

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

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

And Show all transport "false" 007ms

When Go to transport details "CONTAINER" 4s 330ms

And Fill transport form 4s 685ms

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

And Go to transport details "CONTAINER" 4s 257ms

Then Check are transport values equals 043ms

Hooks

After Hooks.deleteTransportAfterTest() 060ms

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 262ms

And Show all transport "false" 007ms

When Go to transport details "DELIVERY" 4s 292ms

And Fill transport form 11s 470ms

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

And Go to transport details "DELIVERY" 4s 314ms

Then Check are transport values equals 133ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

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

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-adama" 001ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-adama" 1s 242ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION" 4s 363ms

And Fill transport form 21s 386ms

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

And Go to transport details "OWN_COLLECTION" 4s 294ms

Then Check are transport values equals 2s 188ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 426ms

And Show all transport "false" 008ms

When Go to transport details "DELIVERY" 4s 739ms

And Fill transport form 35s 658ms

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

And Go to transport details "DELIVERY" 4s 427ms

Then Check are transport values equals 10s 461ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-hochland" 001ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 390ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION" 4s 641ms

And Fill transport form 36s 174ms

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

And Go to transport details "OWN_COLLECTION" 4s 450ms

Then Check are transport values equals 6s 340ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 001ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 397ms

And Show all transport "false" 006ms

When Go to transport details "EXPORT" 5s 585ms

And Fill transport form 47s 546ms

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

And Go to transport details "EXPORT" 4s 395ms

Then Check are transport values equals 8s 451ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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

And Get inputs from database "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 001ms

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

And Show all transport "false" 009ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 493ms

And Fill transport form 35s 863ms

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

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 420ms

Then Check are transport values equals 12s 420ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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

And Get inputs from database "EDIT_CISTERN_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 323ms

And Show all transport "false" 009ms

When Go to transport details "CISTERN_DELIVERY" 4s 471ms

And Fill transport form 27s 204ms

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

And Go to transport details "CISTERN_DELIVERY" 4s 368ms

Then Check are transport values equals 6s 278ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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

And Get inputs from database "EDIT_CISTERN_COLLECTION" "super-admin-hochland" 001ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 1s 295ms

And Show all transport "false" 018ms

When Go to transport details "CISTERN_COLLECTION" 4s 398ms

And Fill transport form 25s 568ms

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

And Go to transport details "CISTERN_COLLECTION" 4s 351ms

Then Check are transport values equals 6s 253ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 001ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 208ms

And Show all transport "false" 008ms

When Go to transport details "WEIGHING" 4s 356ms

And Fill transport form 12s 199ms

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

And Go to transport details "WEIGHING" 4s 284ms

Then Check are transport values equals 2s 134ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

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

And Get inputs from database "EDIT_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 002ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 1s 305ms

And Show all transport "false" 007ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 530ms

And Fill transport form 34s 951ms

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

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 388ms

Then Check are transport values equals 6s 304ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 237ms

And Show all transport "false" 007ms

When Go to transport details "DELIVERY" 32s 367ms

And Fill transport form 25s 349ms

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

And Go to transport details "DELIVERY" 32s 320ms

Then Check are transport values equals 2s 162ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

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" 1s 127ms

And Get inputs from database "EDIT_LOAD" "super-admin-piast" 001ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 174ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 631ms

And Fill transport form 56s 696ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 594ms

And Go to transport details "LOAD" 4s 557ms

Then Check are transport values equals 24s 689ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

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" 1s 213ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 311ms

And Show all transport "false" 009ms

When Go to transport details "DELIVERY" 4s 327ms

And Fill transport form 16s 403ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 644ms

And Go to transport details "DELIVERY" 4s 290ms

Then Check are transport values equals 085ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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" 1s 095ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 273ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 327ms

And Fill transport form 27s 958ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 152ms

And Go to transport details "LOAD" 4s 284ms

Then Check are transport values equals 2s 206ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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" 1s 141ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 279ms

And Show all transport "false" 008ms

When Go to transport details "UNLOAD" 4s 432ms

And Fill transport form 37s 550ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 633ms

And Go to transport details "UNLOAD" 4s 397ms

Then Check are transport values equals 6s 332ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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" 1s 119ms

And Get inputs from database "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 001ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 308ms

And Show all transport "false" 010ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 364ms

And Fill transport form 35s 876ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 585ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 347ms

Then Check are transport values equals 6s 344ms

Hooks

After Hooks.deleteTransportAfterTest() 143ms

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" 1s 096ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 193ms

And Show all transport "false" 007ms

When Go to transport details "LOAD" 4s 335ms

And Fill transport form 24s 609ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 596ms

And Go to transport details "LOAD" 4s 305ms

Then Check are transport values equals 4s 163ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

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" 1s 275ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 162ms

And Show all transport "false" 010ms

When Go to transport details "CONTAINER" 4s 400ms

And Fill transport form 24s 563ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 606ms

And Go to transport details "CONTAINER" 4s 297ms

Then Check are transport values equals 4s 163ms

Hooks

After Hooks.deleteTransportAfterTest() 052ms

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" 1s 201ms

And Get inputs from database "EDIT_SMALLS_EXPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 238ms

And Show all transport "false" 012ms

When Go to transport details "SMALLS_EXPORT" 4s 473ms

And Fill transport form 32s 737ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 610ms

And Go to transport details "SMALLS_EXPORT" 4s 386ms

Then Check are transport values equals 8s 281ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

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" 1s 153ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 313ms

And Show all transport "true" 058ms

When Go to transport details "DELIVERY" 4s 280ms

And Fill transport form 19s 427ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 589ms

And Go to transport details "DELIVERY" 4s 281ms

Then Check are transport values equals 156ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

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" 1s 198ms

And Get inputs from database "EDIT_TRANSPORT_ORDER" "super-admin-alrec" 001ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 246ms

And Show all transport "true" 074ms

When Go to transport details "TRANSPORT_ORDER" 4s 475ms

And Fill transport form 26s 545ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 630ms

And Go to transport details "TRANSPORT_ORDER" 4s 350ms

Then Check are transport values equals 2s 206ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

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" 1s 788ms

And Get inputs from database "EDIT_CONTAINER_WAREHOUSEMAN_CUSTOMFIELDS" "super-admin-keeeper" 001ms

And Create transport "CREATE_CONTAINER_KEEEPER_WAIMEA" by JSON file as "super-admin-keeeper" 1s 190ms

And Show all transport "false" 010ms

When Go to transport details "CONTAINER" 4s 428ms

And Fill transport form 8s 800ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 617ms

And Go to transport details "CONTAINER" 4s 345ms

Then Check are transport values equals 4s 107ms

Hooks

After Hooks.deleteTransportAfterTest() 063ms

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" 1s 499ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 386ms

And Show all transport "false" 009ms

When Delete transport 17s 842ms

Then Transport not displayed in table of transports 15s 031ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

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" 1s 212ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 208ms

And Show all transport "false" 010ms

When Delete transport 17s 657ms

Then Transport not displayed in table of transports 15s 017ms

Hooks

After Hooks.deleteTransportAfterTest() 052ms

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" 1s 075ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 251ms

And Show all transport "false" 010ms

When Delete transport 17s 471ms

Then Transport not displayed in table of transports 15s 062ms

Hooks

After Hooks.deleteTransportAfterTest() 055ms

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" 1s 145ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 186ms

And Show all transport "false" 007ms

When Delete transport 17s 001ms

Then Transport not displayed in table of transports 15s 044ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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" 1s 325ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 249ms

And Show all transport "false" 009ms

When Delete transport 17s 617ms

Then Transport not displayed in table of transports 15s 023ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

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" 1s 610ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 227ms

And Show all transport "false" 008ms

When Delete transport 17s 645ms

Then Transport not displayed in table of transports 15s 027ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

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" 1s 154ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 275ms

And Show all transport "true" 077ms

When Delete transport 19s 107ms

Then Transport not displayed in table of transports 15s 062ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

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" 1s 150ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 239ms

And Show all transport "true" 081ms

When Delete transport 17s 087ms

Then Transport not displayed in table of transports 15s 012ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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" 1s 065ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 001ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 619ms

And Show all transport "false" 009ms

When Go to transport details "UNLOAD" 32s 534ms

And Fill transport form 30s 144ms

And Click "save-transport" save button 1s 208ms

And Click cancel button in transport form 066ms

And Go to transport details "UNLOAD" 32s 391ms

Then Check are transport values equals 4s 238ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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" 1s 139ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 001ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 216ms

And Show all transport "false" 007ms

When Go to transport details "TRANSPORT" 4s 540ms

And Fill transport form 10s 267ms

And Click "save-transport" save button 745ms

And Click cancel button in transport form 068ms

And Go to transport details "TRANSPORT" 4s 339ms

Then Check are transport values equals 4s 113ms

Hooks

After Hooks.deleteTransportAfterTest() 055ms

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" 1s 108ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 002ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 169ms

And Show all transport "false" 009ms

When Go to transport details "CONTAINER" 4s 320ms

And Fill transport form 4s 674ms

And Click "save-transport" save button 690ms

And Click cancel button in transport form 063ms

And Go to transport details "CONTAINER" 4s 223ms

Then Check are transport values equals 037ms

Hooks

After Hooks.deleteTransportAfterTest() 053ms

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" 1s 123ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 287ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 335ms

And Fill transport form 11s 447ms

And Click "save-transport" save button 692ms

And Click cancel button in transport form 075ms

And Go to transport details "DELIVERY" 4s 268ms

Then Check are transport values equals 096ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

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" 1s 106ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-adama" 001ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-adama" 1s 263ms

And Show all transport "false" 007ms

When Go to transport details "OWN_COLLECTION" 4s 306ms

And Fill transport form 21s 404ms

And Click "save-transport" save button 683ms

And Click cancel button in transport form 067ms

And Go to transport details "OWN_COLLECTION" 4s 268ms

Then Check are transport values equals 2s 167ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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" 1s 546ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 359ms

And Show all transport "false" 007ms

When Go to transport details "DELIVERY" 4s 738ms

And Fill transport form 35s 452ms

And Click "save-transport" save button 1s 258ms

And Click cancel button in transport form 080ms

And Go to transport details "DELIVERY" 4s 352ms

Then Check are transport values equals 10s 458ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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" 1s 645ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-hochland" 001ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 336ms

And Show all transport "false" 008ms

When Go to transport details "OWN_COLLECTION" 4s 682ms

And Fill transport form 36s 469ms

And Click "save-transport" save button 832ms

And Click cancel button in transport form 076ms

And Go to transport details "OWN_COLLECTION" 4s 375ms

Then Check are transport values equals 6s 332ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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" 1s 429ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 001ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 409ms

And Show all transport "false" 009ms

When Go to transport details "EXPORT" 5s 542ms

And Fill transport form 47s 669ms

And Click "save-transport" save button 855ms

And Click cancel button in transport form 083ms

And Go to transport details "EXPORT" 4s 350ms

Then Check are transport values equals 8s 424ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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" 1s 487ms

And Get inputs from database "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 001ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 162ms

And Show all transport "false" 010ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 703ms

And Fill transport form 35s 877ms

And Click "save-transport" save button 882ms

And Click cancel button in transport form 096ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 357ms

Then Check are transport values equals 12s 426ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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" 1s 651ms

And Get inputs from database "EDIT_CISTERN_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 348ms

And Show all transport "false" 009ms

When Go to transport details "CISTERN_DELIVERY" 4s 548ms

And Fill transport form 27s 128ms

And Click "save-transport" save button 755ms

And Click cancel button in transport form 081ms

And Go to transport details "CISTERN_DELIVERY" 4s 363ms

Then Check are transport values equals 6s 255ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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" 1s 507ms

And Get inputs from database "EDIT_CISTERN_COLLECTION" "super-admin-hochland" 001ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 1s 256ms

And Show all transport "false" 007ms

When Go to transport details "CISTERN_COLLECTION" 4s 439ms

And Fill transport form 25s 674ms

And Click "save-transport" save button 709ms

And Click cancel button in transport form 071ms

And Go to transport details "CISTERN_COLLECTION" 4s 357ms

Then Check are transport values equals 6s 246ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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 003ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 001ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 194ms

And Show all transport "false" 014ms

When Go to transport details "WEIGHING" 4s 371ms

And Fill transport form 12s 178ms

And Click "save-transport" save button 700ms

And Click cancel button in transport form 111ms

And Go to transport details "WEIGHING" 4s 274ms

Then Check are transport values equals 2s 134ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

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" 1s 565ms

And Get inputs from database "EDIT_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 001ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 1s 309ms

And Show all transport "false" 009ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 524ms

And Fill transport form 35s 020ms

And Click "save-transport" save button 865ms

And Click cancel button in transport form 101ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 374ms

Then Check are transport values equals 6s 303ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

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" 1s 087ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 274ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 32s 425ms

And Fill transport form 25s 400ms

And Click "save-transport" save button 692ms

And Click cancel button in transport form 070ms

And Go to transport details "DELIVERY" 32s 297ms

Then Check are transport values equals 2s 185ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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" 1s 105ms

And Get inputs from database "EDIT_LOAD" "super-admin-piast" 001ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 177ms

And Show all transport "false" 003ms

When Go to transport details "LOAD" 4s 699ms

And Fill transport form 56s 768ms

And Click "save-transport" save button 969ms

And Click cancel button in transport form 073ms

And Go to transport details "LOAD" 4s 420ms

Then Check are transport values equals 24s 643ms

Hooks

After Hooks.deleteTransportAfterTest() 064ms

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" 1s 034ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 245ms

And Show all transport "false" 005ms

When Go to transport details "DELIVERY" 4s 351ms

And Fill transport form 16s 321ms

And Click "save-transport" save button 702ms

And Click cancel button in transport form 064ms

And Go to transport details "DELIVERY" 4s 260ms

Then Check are transport values equals 052ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

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" 1s 006ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 246ms

And Show all transport "false" 005ms

When Go to transport details "LOAD" 4s 307ms

And Fill transport form 27s 991ms

And Click "save-transport" save button 1s 220ms

And Click cancel button in transport form 067ms

And Go to transport details "LOAD" 4s 270ms

Then Check are transport values equals 2s 195ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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" 1s 091ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 296ms

And Show all transport "false" 008ms

When Go to transport details "UNLOAD" 4s 385ms

And Fill transport form 37s 526ms

And Click "save-transport" save button 769ms

And Click cancel button in transport form 085ms

And Go to transport details "UNLOAD" 4s 343ms

Then Check are transport values equals 6s 317ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

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" 1s 099ms

And Get inputs from database "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 001ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 336ms

And Show all transport "false" 009ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 401ms

And Fill transport form 35s 919ms

And Click "save-transport" save button 740ms

And Click cancel button in transport form 083ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 280ms

Then Check are transport values equals 6s 317ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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" 1s 116ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 170ms

And Show all transport "false" 009ms

When Go to transport details "LOAD" 4s 386ms

And Fill transport form 24s 503ms

And Click "save-transport" save button 699ms

And Click cancel button in transport form 067ms

And Go to transport details "LOAD" 4s 292ms

Then Check are transport values equals 4s 155ms

Hooks

After Hooks.deleteTransportAfterTest() 048ms

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" 1s 147ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 180ms

And Show all transport "false" 009ms

When Go to transport details "CONTAINER" 4s 366ms

And Fill transport form 24s 546ms

And Click "save-transport" save button 705ms

And Click cancel button in transport form 099ms

And Go to transport details "CONTAINER" 4s 265ms

Then Check are transport values equals 4s 188ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

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" 1s 210ms

And Get inputs from database "EDIT_SMALLS_IMPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 202ms

And Show all transport "false" 011ms

When Go to transport details "SMALLS_IMPORT" 4s 419ms

And Fill transport form 32s 841ms

And Click "save-transport" save button 707ms

And Click cancel button in transport form 058ms

And Go to transport details "SMALLS_IMPORT" 4s 307ms

Then Check are transport values equals 8s 253ms

Error message

org.junit.ComparisonFailure: Wartości w formularzu w polu company-step-0 są niepoprawne, wartość na stronie: KSKZA1 wartość poprawna: KSKZA2 expected: 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:261)
	at CucumberTests.Transport.CreateTransport.checkTransportValues(CreateTransport.java:225)
	at ✽.Check are transport values equals(file:Features/Atom/Transport/CrudTransport.feature:138)

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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" 1s 580ms

And Get inputs from database "EDIT_SMALLS_EXPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 215ms

And Show all transport "false" 010ms

When Go to transport details "SMALLS_EXPORT" 4s 450ms

And Fill transport form 32s 709ms

And Click "save-transport" save button 708ms

And Click cancel button in transport form 061ms

And Go to transport details "SMALLS_EXPORT" 4s 294ms

Then Check are transport values equals 8s 250ms

Error message

org.junit.ComparisonFailure: Wartości w formularzu w polu company-step-1 są niepoprawne, wartość na stronie: KSKZA1 wartość poprawna: KSKZA2 expected: 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:261)
	at CucumberTests.Transport.CreateTransport.checkTransportValues(CreateTransport.java:225)
	at ✽.Check are transport values equals(file:Features/Atom/Transport/CrudTransport.feature:138)

Hooks

After Hooks.deleteTransportAfterTest() 067ms

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" 1s 193ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 268ms

And Show all transport "true" 079ms

When Go to transport details "DELIVERY" 4s 278ms

And Fill transport form 19s 378ms

And Click "save-transport" save button 706ms

And Click cancel button in transport form 057ms

And Go to transport details "DELIVERY" 4s 256ms

Then Check are transport values equals 150ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

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" 1s 090ms

And Get inputs from database "EDIT_TRANSPORT_ORDER" "super-admin-alrec" 002ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 243ms

And Show all transport "true" 061ms

When Go to transport details "TRANSPORT_ORDER" 4s 442ms

And Fill transport form 26s 483ms

And Click "save-transport" save button 723ms

And Click cancel button in transport form 056ms

And Go to transport details "TRANSPORT_ORDER" 4s 311ms

Then Check are transport values equals 2s 233ms

Hooks

After Hooks.deleteTransportAfterTest() 063ms

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" 1s 092ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 177ms

And Create gray windows "CREATE_GRAY_WINDOW_MWG" on "PRZESYŁKI DROBNICOWE" in "Magazyn Wyrobów Gotowych" as "super-admin-keeeper" 277ms

And If user is login then logout 318ms

Then Login as "dka1-supplier" 1s 947ms

And Click button advice in transport table "LOAD" 109ms

And Check if moved to first possible start date in schedule 429ms

Hooks

After Hooks.deleteTransportAfterTest() 060ms

After Hooks.deleteAllGrayWindowsAfterTest() 1m 30s 470ms

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" 106ms

And Set "transport" inputs from JSON file "CREATE_LOAD_WITH_NEW_ADDRESS" "super-admin-piast" 008ms

When Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 244ms

Then Go to new transport "LOAD" 337ms

And Fill transport form 23s 329ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 606ms

And Go to "COMPANIES_TAB" 381ms

And Go to company "Dostawca Piast Automat 1" details 214ms

And Check if new address with "Adresat" is visible in company details 098ms

And Go to "TRANSPORT_TABLE" 211ms

And Go to transport details "LOAD" 4s 647ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

After Hooks.deleteAddressAfterTest() 040ms

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" 1s 370ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 171ms

When Go to "TRANSPORT_TABLE" 120ms

And Show all transport types 1s 035ms

And Verify that transport has "0" files 037ms

Then Add file to transport by API 519ms

And Verify that transport has "1" files 467ms

Hooks

After Hooks.deleteTransportAfterTest() 057ms

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" 1s 092ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 169ms

When Go to "TRANSPORT_TABLE" 107ms

And Show all transport types 1s 029ms

And Verify that transport has "0" files 035ms

Then Add file to transport by API 267ms

And Verify that transport has "1" files 526ms

Hooks

After Hooks.deleteTransportAfterTest() 055ms

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" 1s 315ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 386ms

When Go to "TRANSPORT_TABLE" 151ms

And Show all transport types 1s 026ms

And Verify that transport has "0" files 023ms

Then Add file to transport by API 295ms

And Verify that transport has "1" files 295ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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" 984ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 164ms

When Go to "TRANSPORT_TABLE" 117ms

And Show all transport types 1s 037ms

And Verify that transport has "0" files 036ms

Then Add file to transport by API 227ms

And Verify that transport has "1" files 867ms

Hooks

After Hooks.deleteTransportAfterTest() 051ms

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" 1s 060ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 168ms

And Delete transport 17s 175ms

When Go to "ARCHIVE_TAB" 212ms

And Show "DELIVERY" 045ms

And Verify that transport has "0" files 599ms

Then Add file to transport 135ms

And Verify that transport has "1" files 314ms

Hooks

After Hooks.deleteTransportAfterTest() 049ms

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" 1s 142ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 172ms

And Delete transport 17s 301ms

When Go to "ARCHIVE_TAB" 222ms

And Show "LOAD" 253ms

And Verify that transport has "0" files 1s 048ms

Then Add file to transport 143ms

And Verify that transport has "1" files 382ms

Hooks

After Hooks.deleteTransportAfterTest() 054ms

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" 1s 310ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 320ms

And Delete transport 17s 509ms

When Go to "ARCHIVE_TAB" 224ms

And Show "DELIVERY" 054ms

And Verify that transport has "0" files 831ms

Then Add file to transport 134ms

And Verify that transport has "1" files 342ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

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" 1s 258ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 228ms

And Delete transport 17s 538ms

When Go to "ARCHIVE_TAB" 217ms

And Show "CONTAINER" 129ms

And Verify that transport has "0" files 916ms

Then Add file to transport 131ms

And Verify that transport has "1" files 307ms

Hooks

After Hooks.deleteTransportAfterTest() 064ms

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" 121ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 15s 170ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 109ms

And Accept transferred transport by Api 209ms

And Login as "paa1-carrier@qa.qa-test" 1s 281ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 16s 102ms

Hooks

After Hooks.deleteTransportAfterTest() 053ms

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" 1s 352ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 192ms

And Transfer transport to carrier by JSON file "super-admin-adama" "false" confirmation 131ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 17s 723ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

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" 109ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 205ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 153ms

And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 382ms

And Login as "paa1-carrier@qa.qa-test" 1s 186ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 15s 464ms

Hooks

After Hooks.deleteTransportAfterTest() 060ms

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" 1s 025ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 250ms

When Go to "TRANSPORT_TABLE" 140ms

And Show all transport "true" 051ms

Then Verify that transport has "1" CMR file 1s 163ms

Hooks

After Hooks.deleteTransportAfterTest() 060ms

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" 998ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 239ms

When Go to "TRANSPORT_TABLE" 100ms

And Show all transport "true" 055ms

Then Verify that transport has "2" CMR file 1s 162ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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" 1s 083ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 243ms

When Go to "TRANSPORT_TABLE" 106ms

And Show all transport "true" 061ms

Then Verify that "CMR" document can be downloaded 17s 444ms

Hooks

After Hooks.deleteTransportAfterTest() 059ms

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" 1s 129ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 231ms

And Show all transport "true" 119ms

And Delete transport 17s 077ms

When Go to "ARCHIVE_TAB" 203ms

And Show "TRANSPORT_ORDER" 047ms

Then Verify that "CMR" document can be downloaded 16s 702ms

Hooks

After Hooks.deleteTransportAfterTest() 057ms

View Feature Transport files

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline The link to the delivery document appears after confirming the respective status [A-6905]

Steps

Given Login as "pba1-carrier" and set token of apiUsername "super-admin-bausch" 1s 828ms

And Create default accepted mode of transportation by API with "pba1-carrier" 387ms

And If user is login then logout 165ms

And Login as "bausch-admin" and set token of apiUsername "super-admin-bausch" 1s 309ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 247ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 161ms

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-bausch" 009ms

And Click button advice in transport table "LOAD_PL" 1s 742ms

And Set advice window in schedule 2s 766ms

And Fill advice form 9s 122ms

And Click advice save button and wait for advice form to disappear 30s 851ms

And Find transport in table with status "advice-added" 3s 279ms

When Confirm statuses until reach "on-the-way" 9s 744ms

Then Verify that "delivery_document" document can be downloaded 16s 278ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

After Hooks.deleteModeOfTransportationAfterTest() 059ms

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" 1s 516ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 402ms

And Show all transport "false" 007ms

When Find transport pencil button in transports table 1s 223ms

And Click pencil and move transport to next day in schedule 16s 397ms

Then Check if transport is in new location in schedule 2s 108ms

And Check if dates in transport form are correct 3s 438ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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" 1s 112ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 300ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 200ms

And Click pencil and move transport to next day in schedule 16s 662ms

Then Check if transport is in new location in schedule 2s 113ms

And Check if dates in transport form are correct 3s 284ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

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" 1s 102ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 286ms

And Show all transport "false" 007ms

When Find transport pencil button in transports table 1s 214ms

And Click pencil and move transport to next day in schedule 16s 795ms

Then Check if transport is in new location in schedule 2s 112ms

And Check if dates in transport form are correct 3s 314ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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" 1s 143ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 319ms

And Show all transport "false" 008ms

When Find transport pencil button in transports table 1s 215ms

And Click pencil and move transport to next day in schedule 16s 342ms

Then Check if transport is in new location in schedule 2s 108ms

And Check if dates in transport form are correct 3s 365ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

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" 1s 218ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 323ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 246ms

And Click pencil and move transport to next day in schedule 16s 480ms

Then Check if transport is in new location in schedule 2s 100ms

And Check if dates in transport form are correct 3s 300ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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" 1s 149ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-alrec" 1s 347ms

And Show all transport "true" 087ms

When Find transport pencil button in transports table 1s 204ms

And Click pencil and move transport to next day in schedule 16s 362ms

Then Check if transport is in new location in schedule 2s 099ms

And Check if dates in transport form are correct 3s 360ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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" 1s 179ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 211ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 001ms

When Show all transport types 1s 038ms

And Click button advice in transport table "DELIVERY" 100ms

And Set advice window in schedule 2s 676ms

And Fill advice form 8s 260ms

And Click advice save button and wait for advice form to disappear 30s 715ms

And Go to "TRANSPORT_TABLE" 209ms

And Find transport pencil button in transports table 1s 217ms

And Click pencil and move transport to next day in schedule 17s 434ms

Then Check if transport is in new location in schedule 2s 101ms

And Check if dates in transport form are correct 3s 405ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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" 1s 605ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 349ms

And Show all transport "false" 009ms

When Find transport pencil button in transports table 1s 217ms

And Click pencil and move transport to next day in schedule 16s 323ms

And Move advice window "3" 1s 310ms

Then Check if advice window is in new location 022ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

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" 1s 080ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 283ms

And Show all transport "false" 009ms

When Find transport pencil button in transports table 1s 228ms

And Click pencil and move transport to next day in schedule 16s 728ms

And Move advice window "3" 1s 337ms

Then Check if advice window is in new location 022ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

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" 1s 114ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 284ms

And Show all transport "false" 009ms

When Find transport pencil button in transports table 1s 236ms

And Click pencil and move transport to next day in schedule 16s 803ms

And Move advice window "3" 1s 375ms

Then Check if advice window is in new location 029ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

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" 1s 134ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 316ms

And Show all transport "false" 006ms

When Find transport pencil button in transports table 1s 213ms

And Click pencil and move transport to next day in schedule 16s 314ms

And Move advice window "3" 1s 303ms

Then Check if advice window is in new location 053ms

Hooks

After Hooks.deleteTransportAfterTest() 064ms

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" 1s 118ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 289ms

And Show all transport "false" 009ms

When Find transport pencil button in transports table 1s 204ms

And Click pencil and move transport to next day in schedule 16s 323ms

And Move advice window "3" 1s 296ms

Then Check if advice window is in new location 017ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

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" 1s 085ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 264ms

And Show all transport "true" 052ms

When Find transport pencil button in transports table 1s 213ms

And Click pencil and move transport to next day in schedule 16s 342ms

And Move advice window "3" 1s 424ms

Then Check if advice window is in new location 014ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

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" 1s 412ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 355ms

And Go to transport details "DELIVERY" 4s 721ms

When Open section: "discrepancy-report-panel" 1s 063ms

Then Verify that no discrepancies found label is visible in discrepancy report section 055ms

And Select "NIE" in the "insp.-accord.-with-ins." 2s 412ms

And Verify that discrepancy report custom fields are visible in discrepancy report section 090ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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" 1s 282ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 346ms

And Go to transport details "DELIVERY" 4s 731ms

And Fill transport form 35s 647ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 114ms

When Go to transport details "DELIVERY" 4s 398ms

Then Select "NIE" in the "insp.-accord.-with-ins." 2s 399ms

And Click "save-transport" save button 704ms

And Wait "2" seconds 2s

And Verify that discrepancy report section is open 025ms

And Verify that discrepancy report section contains validation errors 014ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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" 1s 387ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 455ms

When Go to transport details "DELIVERY" 4s 726ms

Then Verify that discrepancy report section is available 034ms

And Open section: "discrepancy-report-panel" 1s 058ms

And Verify that generate new discrepancy report button is visible 026ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

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" 1s 270ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 319ms

When Go to transport details "OWN_COLLECTION" 4s 645ms

Then Verify that discrepancy report section is available 026ms

And Open section: "discrepancy-report-panel" 1s 054ms

And Verify that generate new discrepancy report button is visible 029ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

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" 1s 269ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 1s 326ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 464ms

Then Verify that discrepancy report section is available 033ms

And Open section: "discrepancy-report-panel" 1s 052ms

And Verify that generate new discrepancy report button is visible 025ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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" 1s 390ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 358ms

When Go to transport details "EXPORT" 5s 324ms

Then Verify that discrepancy report section is available 029ms

And Open section: "discrepancy-report-panel" 1s 055ms

And Verify that generate new discrepancy report button is visible 021ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

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" 1s 347ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 177ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 643ms

Then Verify that discrepancy report section is available 034ms

And Open section: "discrepancy-report-panel" 1s 054ms

And Verify that generate new discrepancy report button is visible 023ms

Hooks

After Hooks.deleteTransportAfterTest() 062ms

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" 1s 308ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 324ms

When Go to transport details "CISTERN_DELIVERY" 4s 477ms

Then Verify that discrepancy report section is not available 15s 020ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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" 1s 500ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 1s 258ms

When Go to transport details "CISTERN_COLLECTION" 4s 413ms

Then Verify that discrepancy report section is not available 15s 035ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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" 1s 390ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 191ms

When Go to transport details "WEIGHING" 4s 359ms

Then Verify that discrepancy report section is not available 15s 053ms

Hooks

After Hooks.deleteTransportAfterTest() 060ms

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" 1s 413ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 370ms

When Go to "TRANSPORT_TABLE" 128ms

And Go to transport details "DELIVERY" 4s 741ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 638ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 311ms

And Open section: "discrepancy-report-panel" 1s 061ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 002ms

And Fill transport form 35s 592ms

And Fill discrepancy report section without closing the form 19s 315ms

And Generate discrepancy report 16s 731ms

And Download discrepancy report 143ms

Then Verify that discrepancy report file has correct values 15s 145ms

Error message

java.nio.file.NoSuchFileException: /home/teamcity/Downloads/49_2021_1.pdf
	at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
	at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
	at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)
	at java.nio.file.Files.newOutputStream(Files.java:216)
	at java.nio.file.Files.copy(Files.java:3016)
	at Utils.FileUtil.checkIfFileExist(FileUtil.java:45)
	at Utils.FileUtil.getPdfFileText(FileUtil.java:28)
	at CucumberTests.Transport.TransportFormTest.verifyThatDiscrepancyReportFileHasCorrectValues(TransportFormTest.java:250)
	at ✽.Verify that discrepancy report file has correct values(file:Features/Atom/Transport/TransportForm/DiscrepancyReport.feature:76)

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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" 1s 421ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 308ms

When Go to "TRANSPORT_TABLE" 141ms

And Go to transport details "DELIVERY" 4s 720ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 002ms

And Fill transport form 35s 622ms

And Open section: "discrepancy-report-panel" 1s 064ms

And Fill discrepancy report section without closing the form 19s 244ms

And Generate discrepancy report 16s 166ms

And Download discrepancy report 150ms

And Verify that discrepancy report file has correct values 15s 113ms

Error message

java.nio.file.NoSuchFileException: /home/teamcity/Downloads/50_2021_1.pdf
	at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
	at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
	at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)
	at java.nio.file.Files.newOutputStream(Files.java:216)
	at java.nio.file.Files.copy(Files.java:3016)
	at Utils.FileUtil.checkIfFileExist(FileUtil.java:45)
	at Utils.FileUtil.getPdfFileText(FileUtil.java:28)
	at CucumberTests.Transport.TransportFormTest.verifyThatDiscrepancyReportFileHasCorrectValues(TransportFormTest.java:250)
	at ✽.Verify that discrepancy report file has correct values(file:Features/Atom/Transport/TransportForm/DiscrepancyReport.feature:93)

And Fill edited discrepancy report section 000ms

And Generate edited discrepancy report 000ms

And Download discrepancy report 000ms

Then Verify that discrepancy report file has correct values 000ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

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" 105ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 040ms

And Get "LOAD" settings from "piast" 030ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "false" 092ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-piast" 1s 184ms

And Login as "piast-admin" 1s 457ms

And Go to "TRANSPORT_TABLE" 182ms

When Go to transport details "LOAD" 4s 705ms

And Add step "unload" 107ms

And Change filled value in transport details "company-step-2" "autocomplete" "DPA2" "0" 6s 477ms

And Change filled value in transport details "recipient-step-2" "autocomplete" "Testowy" "0" 6s 486ms

Then Click "save-transport-and-close" save button and wait for form to disappear 15s 583ms

And Go to transport details "LOAD" 4s 525ms

And Verify that transport has "3" steps 014ms

Hooks

After Hooks.deleteTransportAfterTest() 051ms

After Hooks.rollbackTransportTypeSettings() 045ms

After Hooks.rollbackAddedActionAuthorities() 031ms

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" 1s 904ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 281ms

When Go to "TRANSPORT_TABLE" 140ms

And Go to transport details "SMALLS_IMPORT" 17s 089ms

Then Verify that user can't edit time range for load and unload 15s 014ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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" 117ms

And Create transport "CREATE_DELIVERY_TWO_LOADS" by JSON file as "super-admin-neuca" 1s 363ms

And Login as "neuca-admin" 850ms

And Go to "TRANSPORT_TABLE" 208ms

And Show all transport types 15s 027ms

When Go to transport details "DELIVERY" 32s 473ms

Then Check if sum of number of pallets in transport form in "load" steps is correct 054ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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" 101ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 15s 321ms

And Login as "hochland-admin" 1s 376ms

And Go to "TRANSPORT_TABLE" 119ms

And Show all transport types 1s 050ms

When Go to transport details "EXPORT" 5s 551ms

Then Check if sum of number of pallets in transport form in "unload" steps is correct 052ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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" 119ms

And Get "DELIVERY" settings from "neuca" 033ms

And Set transportType settings with values: "quantitySumCheckValue", "33" 090ms

And Login as "neuca-admin" 892ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 15s 313ms

When Go to "TRANSPORT_TABLE" 206ms

And Go to transport details "DELIVERY" 32s 452ms

And Set number of pallets in "load" step in transport - "32" 115ms

And Check if number of pallets check message is not visible in transport form 15s 060ms

And Set number of pallets in "load" step in transport - "34" 111ms

Then Check if number of pallets check message is visible in transport form 040ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

After Hooks.rollbackTransportTypeSettings() 077ms

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" 112ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 040ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 040ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 105ms

And Login as "farmacol-admin" 1s 351ms

And Go to new transport "EXTERNAL_DELIVERY" 366ms

And Add step "unload" 082ms

And Click "save-transport-and-close" save button 720ms

Then Verify that "time-range-from-date-2" has validation error 1s 026ms

Then Verify that "time-range-to-date-2" has validation error 1s 018ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 298ms

And Click "save-transport-and-close" save button 689ms

And Verify that "time-range-from-date-2" has no validation error 017ms

And Verify that "time-range-to-date-2" has no validation error 016ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.rollbackTransportTypeSettings() 056ms

After Hooks.rollbackAddedActionAuthorities() 030ms

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" 105ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_LOAD_STEP_FROM_UNLOAD" "ACTIVE" 040ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 228ms

When Login as "piast-admin" 1s 252ms

And Go to transport details "LOAD" 4s 830ms

And Get inputs from database "PIAST_LOAD_ADD_UNLOAD_STEP" "super-admin-piast" 001ms

And Add step "unload" 122ms

And Fill step data 14s 980ms

And Get inputs from database "PIAST_LOAD_ADD_LOAD_STEP" "super-admin-piast" 002ms

And Add step "load" 116ms

And Fill step data 5s 463ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 612ms

Then Go to transport details "LOAD" 4s 534ms

And Check if "unload" step is added as "3" step in transport form 039ms

And Check if "load" step is added as "4" step in transport form 025ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

After Hooks.rollbackAddedActionAuthorities() 033ms

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" 113ms

And Add action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_LOAD_STEPS" "UNLIMITED" 047ms

And Remove action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_UNLOAD_STEPS" "UNLIMITED" 005ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 193ms

When Login as "super-admin-skz" 2s 135ms

And Go to transport details "SMALLS_EXPORT" 4s 477ms

And Check if step is draggable "LOAD" 015ms

And Check if step is not draggable "UNLOAD" 016ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

After Hooks.rollbackAddedActionAuthorities() 030ms

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" 004ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 101ms

When Go to new transport "SMALLS_IMPORT" 318ms

And Fill transport form 19s 736ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 604ms

And Show all transport "false" 006ms

And Go to transport details "SMALLS_IMPORT" 4s 386ms

And Click create similar button 15s 130ms

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 15s 577ms

And Open similar transport details 313ms

Then Check are transport values equals 2s 098ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

After Hooks.deleteSimilarTransportAfterTest() 073ms

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_TRANSPORT_ORDER" "super-admin-alrec" 006ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 467ms

When Go to new transport "TRANSPORT_ORDER" 385ms

And Fill transport form 23s 749ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 613ms

And Show all transport "true" 072ms

And Go to transport details "TRANSPORT_ORDER" 4s 369ms

And Click create similar button 15s 175ms

And Fill "transport" form "CREATE_SIMILAR_TRANSPORT_ORDER" by "super-admin-alrec" 000ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 585ms

And Open similar transport details 242ms

Then Check are transport values equals 2s 159ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

After Hooks.deleteSimilarTransportAfterTest() 061ms

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" 008ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 1s 615ms

When Go to new transport "DELIVERY" 15s 308ms

And Fill transport form 35s 613ms

And Click "save-transport" save button and wait for form to disappear 15s 669ms

And Set advice window in schedule 2s 156ms

And Check is transport created in schedule and set transport id 780ms

And Go to "TRANSPORT_TABLE" 204ms

And Go to transport details "DELIVERY" 32s 325ms

And Click create similar button 15s 114ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 9s 289ms

And Click "save-transport" save button and wait for form to disappear 15s 577ms

And Set advice window in schedule in "2" days 4s 182ms

And Go to "TRANSPORT_TABLE" 176ms

And Open similar transport details 496ms

Then Check are transport values equals 23s 379ms

Hooks

After Hooks.deleteTransportAfterTest() 020ms

Error message

java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <401>.

	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.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy:179)
	at io.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.putResponse(RestUtil.java:163)
	at Utils.RestUtils.RestUtil.putToApolloApi(RestUtil.java:76)
	at CucumberTests.Hooks.deleteTransportAfterTest(Hooks.java:175)
	at sun.reflect.GeneratedMethodAccessor207.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

After Hooks.deleteSimilarTransportAfterTest() 013ms

Error message

java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <401>.

	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.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy:179)
	at io.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.putResponse(RestUtil.java:163)
	at Utils.RestUtils.RestUtil.putToApolloApi(RestUtil.java:76)
	at CucumberTests.Hooks.deleteSimilarTransportAfterTest(Hooks.java:188)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

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" 000ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 1s 029ms

When Go to new transport "DELIVERY" 15s 272ms

And Fill transport form 35s 513ms

And Click "save-transport" save button and wait for form to disappear 15s 649ms

And Set advice window in schedule 2s 157ms

And Check is transport created in schedule and set transport id 15s 016ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[@id='slot-114767102-2021-05-07-00-15']//div[@data-transport-id]"}
  (Session info: headless chrome=90.0.4430.93)
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: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.zAPrEe}, 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=90.0.4430.93, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 4d6287096dfe598f5ebe874fc309261b
*** Element info: {Using=xpath, value=//div[@id='slot-114767102-2021-05-07-00-15']//div[@data-transport-id]}
	at sun.reflect.GeneratedConstructorAccessor213.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 Pages.Schedule.SchedulePage.getTransportId(SchedulePage.java:161)
	at CucumberTests.Transport.AdviceTransport.checkIsTransportCreatedInScheduleAndSetTransportId(AdviceTransport.java:157)
	at ✽.Check is transport created in schedule and set transport id(file:Features/Atom/Transport/TransportForm/TransportForm.feature:56)

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "DELIVERY" 000ms

And Click create similar button 000ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 000ms

And Click "save-transport" save button and wait for form to disappear 000ms

And Set advice window in schedule in "2" days 000ms

And Go to "TRANSPORT_TABLE" 000ms

And Open similar transport details 000ms

Then Check is field "CARRIER" of type "autocomplete" equals "Przewoźnik Neuca Automat 1" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteSimilarTransportAfterTest() 000ms

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" 002ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 227ms

When Go to new transport "SMALLS_IMPORT" 378ms

And Fill transport form 32s 736ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 634ms

And Go to transport details "SMALLS_IMPORT" 4s 402ms

And Go to transport print details form 3s 096ms

Then Check are transport values equals 8s 280ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

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" 1s 534ms

And Get inputs from database "CREATE_SMALLS_IMPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 280ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 154ms

And Go to transport details "SMALLS_IMPORT" 4s 483ms

Then Verify that the transport can be edited 1s 290ms

And Close transport details 15s 138ms

And If user is login then logout 099ms

And Login as "pskza1-carrier@qa.qa-test" 1s 388ms

And Go to transport details "SMALLS_IMPORT" 4s 451ms

And Verify that the transport cannot be edited 46s 264ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

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" 1s 495ms

And Get inputs from database "CREATE_SMALLS_EXPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 226ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 084ms

And Go to transport details "SMALLS_EXPORT" 4s 406ms

Then Verify that the transport can be edited 1s 262ms

And Close transport details 15s 170ms

And If user is login then logout 104ms

And Login as "pskza1-carrier@qa.qa-test" 1s 404ms

And Go to transport details "SMALLS_EXPORT" 4s 534ms

And Verify that the transport cannot be edited 46s 217ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

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" 1s 274ms

And Get inputs from database "HIDDEN_DATA_SMALLS_IMPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 302ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 111ms

And Go to transport details "SMALLS_IMPORT" 4s 400ms

Then Verify that the hidden data in transport are not visible 1s 043ms

And Close transport details 15s 109ms

And If user is login then logout 099ms

And Login as "swisskrono-admin" 1s 460ms

And Go to transport details "SMALLS_IMPORT" 4s 489ms

And Verify that the hidden data in transport are visible 1s 218ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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" 1s 291ms

And Get inputs from database "HIDDEN_DATA_SMALLS_EXPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 378ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 108ms

And Go to transport details "SMALLS_EXPORT" 4s 392ms

Then Verify that the hidden data in transport are not visible 1s 029ms

And Close transport details 15s 089ms

And If user is login then logout 118ms

And Login as "swisskrono-admin" 1s 484ms

And Go to transport details "SMALLS_EXPORT" 4s 476ms

And Verify that the hidden data in transport are visible 1s 209ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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" 1s 314ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 373ms

When Go to transport details "DELIVERY" 4s 754ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 304ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 502ms

And Change filled value in transport details "insp.-accord.-with-ins." "select" "NIE" "1" 3s 460ms

And Fill discrepancy report section without closing the form 19s 317ms

And Click "save-transport" save button 1s 212ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 594ms

And Check if transport details form is disappeared 15s 017ms

Hooks

After Hooks.deleteTransportAfterTest() 141ms

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" 117ms

And Add action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 040ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 318ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 348ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 3s 314ms

When Go to "TRANSPORT_TABLE" 196ms

And Go to transport details "DELIVERY" 4s 696ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 301ms

Then Verify that "transport-description" in transport has value "opis" 020ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

After Hooks.rollbackAddedActionAuthorities() 034ms

After Hooks.rollbackWarehousesAccess() 125ms

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" 129ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 338ms

And Remove action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 044ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 147ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 2s 504ms

When Go to "TRANSPORT_TABLE" 189ms

And Go to transport details "DELIVERY" 4s 451ms

Then Verify that "transport-description" in transport form is disabled 034ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

After Hooks.rollbackRemovedActionAuthorities() 035ms

After Hooks.rollbackWarehousesAccess() 115ms

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" 112ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 039ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 320ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 591ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 257ms

And Go to transport details "DELIVERY" 4s 723ms

Then Verify that "CARRIER" in transport form is visible 027ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

After Hooks.rollbackAddedActionAuthorities() 026ms

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" 129ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 039ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 165ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 358ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 105ms

And Go to transport details "TRANSPORT" 4s 444ms

Then Verify that "CARRIER" in transport form is visible 026ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

After Hooks.rollbackAddedActionAuthorities() 026ms

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" 109ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 035ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 197ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 429ms

And Show all transport "true" 067ms

When Go to "TRANSPORT_TABLE" 105ms

And Go to transport details "TRANSPORT_ORDER" 4s 434ms

Then Verify that "CARRIER" in transport form is visible 028ms

Hooks

After Hooks.deleteTransportAfterTest() 064ms

After Hooks.rollbackAddedActionAuthorities() 031ms

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" 128ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 028ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 286ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 533ms

And Show all transport "false" 007ms

When Go to "TRANSPORT_TABLE" 255ms

And Go to transport details "DELIVERY" 4s 406ms

Then Verify that "CARRIER" in transport form is not visible 15s 058ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

After Hooks.rollbackRemovedActionAuthorities() 035ms

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" 100ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 030ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 170ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 538ms

And Show all transport "false" 004ms

When Go to "TRANSPORT_TABLE" 122ms

And Go to transport details "TRANSPORT" 4s 438ms

Then Verify that "CARRIER" in transport form is not visible 15s 062ms

Hooks

After Hooks.deleteTransportAfterTest() 063ms

After Hooks.rollbackRemovedActionAuthorities() 039ms

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" 106ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 035ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 207ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 463ms

And Show all transport "true" 080ms

When Go to "TRANSPORT_TABLE" 141ms

And Go to transport details "TRANSPORT_ORDER" 4s 398ms

Then Verify that "CARRIER" in transport form is not visible 15s 060ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

After Hooks.rollbackRemovedActionAuthorities() 033ms

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" 106ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 035ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 033ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 336ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 616ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 246ms

And Go to transport details "DELIVERY" 4s 744ms

Then Verify that "CARRIER" in transport form is not disabled 030ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

After Hooks.rollbackAddedActionAuthorities() 064ms

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" 106ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 036ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 040ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 176ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 422ms

And Show all transport "false" 008ms

When Go to "TRANSPORT_TABLE" 123ms

And Go to transport details "TRANSPORT" 4s 443ms

Then Verify that "CARRIER" in transport form is not disabled 019ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

After Hooks.rollbackAddedActionAuthorities() 056ms

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" 110ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 038ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 040ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 205ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 359ms

And Show all transport "true" 058ms

When Go to "TRANSPORT_TABLE" 102ms

And Go to transport details "TRANSPORT_ORDER" 4s 472ms

Then Verify that "CARRIER" in transport form is not disabled 021ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

After Hooks.rollbackAddedActionAuthorities() 060ms

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" 110ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 077ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 028ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 369ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 513ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 208ms

And Go to transport details "DELIVERY" 4s 732ms

Then Verify that "CARRIER" in transport form is disabled 026ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

After Hooks.rollbackAddedActionAuthorities() 039ms

After Hooks.rollbackRemovedActionAuthorities() 048ms

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" 109ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 042ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 007ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 160ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 413ms

And Show all transport "false" 004ms

When Go to "TRANSPORT_TABLE" 132ms

And Go to transport details "TRANSPORT" 4s 414ms

Then Verify that "CARRIER" in transport form is disabled 024ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

After Hooks.rollbackAddedActionAuthorities() 027ms

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" 108ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 041ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 004ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 193ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 328ms

And Show all transport "true" 083ms

When Go to "TRANSPORT_TABLE" 097ms

And Go to transport details "TRANSPORT_ORDER" 4s 438ms

Then Verify that "CARRIER" in transport form is disabled 024ms

Hooks

After Hooks.deleteTransportAfterTest() 060ms

After Hooks.rollbackAddedActionAuthorities() 029ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can add description to archived transport

Steps

Given Set token of apiUsername "super-admin-adama" 108ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 193ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_MAIN_DATA_SECTION" "UNLIMITED" 039ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_ADVICE" "UNLIMITED" 034ms

And Add action authority with: "adama" "adama-admin" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 049ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 253ms

When Find transport in table with status "planned" 3s 305ms

And Confirm statuses until reach "process-ended" 21s 516ms

And Wait "90" seconds 1m 30s

And Go to "ARCHIVE_TAB" 380ms

And Show "DELIVERY" 067ms

And Go to transport details "DELIVERY" 32s 407ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 305ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 638ms

And Wait "7" seconds 7s

And Go to transport details "DELIVERY" 32s 346ms

Then Verify that "transport-description" in transport has value "opis" 019ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

After Hooks.rollbackAddedActionAuthorities() 030ms

After Hooks.rollbackRemovedActionAuthorities() 072ms

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" 2s 920ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 404ms

When Go to transport details "DELIVERY" 4s 687ms

And Fill transport form 35s 977ms

And Change filled value in transport details "driver-name" "text" "XXX ZZZ" "0" 1s 354ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 099ms

And Go to new transport "DELIVERY" 294ms

Then Verify that driver "XXX ZZZ" is in list 642ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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" 1s 351ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 218ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 14s 055ms

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: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.zAPrEe}, 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=90.0.4430.93, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 4d6287096dfe598f5ebe874fc309261b
	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:198)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:278)
	at CucumberTests.Transport.TransferTransportTest.transferTransportToCarrier(TransferTransportTest.java:43)
	at ✽.Transfer transport to carrier "Przewoźnik SKZ Automat 1"(file:Features/Atom/Transport/TransportForm/TransportForm.feature:274)

And If user is login then logout 000ms

And Login as "pskza1-carrier@qa.qa-test" 000ms

Then Verify that the transport has been transferred 000ms

And Accept or reject "accept" transferred transport 000ms

And Go to transport details "SMALLS_IMPORT" 000ms

And Verify that "transaction-price" in transport form is visible 000ms

And Verify that transaction price field has correct value 000ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_IMPORT" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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" 1s 259ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 233ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 14s 092ms

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: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.zAPrEe}, 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=90.0.4430.93, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 4d6287096dfe598f5ebe874fc309261b
	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:198)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:278)
	at CucumberTests.Transport.TransferTransportTest.transferTransportToCarrier(TransferTransportTest.java:43)
	at ✽.Transfer transport to carrier "Przewoźnik SKZ Automat 1"(file:Features/Atom/Transport/TransportForm/TransportForm.feature:274)

And If user is login then logout 000ms

And Login as "pskza1-carrier@qa.qa-test" 000ms

Then Verify that the transport has been transferred 000ms

And Accept or reject "accept" transferred transport 000ms

And Go to transport details "SMALLS_EXPORT" 000ms

And Verify that "transaction-price" in transport form is visible 000ms

And Verify that transaction price field has correct value 000ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_EXPORT" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

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" 100ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 196ms

And Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 001ms

When Login as "dayco-admin" 1s 385ms

And Click button advice in transport table "OWN_COLLECTION" 252ms

And Set advice window in schedule 2s 497ms

And Fill advice form 6s 830ms

And Click advice save button and wait for advice form to disappear 30s 712ms

And Go to "TRANSPORT_TABLE" 189ms

And Find transport in table with status "planned" 3s 228ms

And Confirm statuses until reach "on-the-area" 3s 792ms

And Go to transport details "OWN_COLLECTION" 4s 390ms

And Click create similar button 15s 105ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 6s 443ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 636ms

And Open similar transport details 277ms

Then Check if transport form modal is visible 024ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

After Hooks.deleteSimilarTransportAfterTest() 052ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

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" 105ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 169ms

And Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 001ms

When Login as "dayco-admin" 933ms

And Click button advice in transport table "OWN_COLLECTION" 278ms

And Set advice window in schedule 2s 482ms

And Fill advice form 6s 878ms

And Click advice save button and wait for advice form to disappear 30s 701ms

And Go to "TRANSPORT_TABLE" 180ms

And Find transport in table with status "planned" 3s 220ms

And Confirm statuses until reach "during-load" 6s 494ms

And Go to transport details "OWN_COLLECTION" 4s 369ms

And Click create similar button 15s 159ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 6s 479ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 619ms

And Open similar transport details 274ms

Then Check if transport form modal is visible 022ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

After Hooks.deleteSimilarTransportAfterTest() 076ms

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" 1s 250ms

And Create transport "CREATE_DELIVERY_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 285ms

And Show all transport types 1s 039ms

Then Check if transport number is visible "DELIVERY" 15s 085ms

And Check if transport details is not visible 15s 043ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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" 3s 061ms

And Show all transport "false" 004ms

And Go to "TRANSPORT_TABLE" 122ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 342ms

When Click on transport row 061ms

Then Verify if transport row is selected 027ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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" 1s 674ms

And Show all transport "false" 004ms

And Go to "TRANSPORT_TABLE" 120ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 269ms

When Click on transport row 074ms

Then Verify if transport row is selected 019ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

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" 1s 253ms

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 100ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 300ms

When Click on transport row 049ms

Then Verify if transport row is selected 021ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

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" 1s 278ms

And Show all transport "false" 005ms

And Go to "TRANSPORT_TABLE" 112ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 265ms

When Click on transport row 054ms

Then Verify if transport row is selected 024ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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" 1s 569ms

And Show all transport "false" 005ms

And Go to "TRANSPORT_TABLE" 108ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 343ms

When Click on transport row 054ms

Then Verify if transport row is selected 024ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

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" 1s 394ms

And Show all transport "true" 053ms

And Go to "TRANSPORT_TABLE" 106ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 275ms

When Click on transport row 050ms

Then Verify if transport row is selected 027ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

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" 1s 723ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 307ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 096ms

When Accept or reject "accept" transferred transport 17s 739ms

Then Verify that transport is accept or reject "accept" 020ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

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" 1s 292ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 306ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 064ms

When Accept or reject "reject" transferred transport 17s 687ms

Then Verify that transport is accept or reject "reject" 15s 058ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

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 065ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 346ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 072ms

When Accept or reject "accept" transferred transport 17s 986ms

Then Verify that transport is accept or reject "accept" 017ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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" 1s 147ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 289ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 060ms

When Accept or reject "reject" transferred transport 18s 498ms

Then Verify that transport is accept or reject "reject" 15s 042ms

Hooks

After Hooks.deleteTransportAfterTest() 056ms

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" 1s 327ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 300ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 075ms

When Accept or reject "accept" transferred transport 2s 564ms

Then Verify that transport is accept or reject "accept" 011ms

Hooks

After Hooks.deleteTransportAfterTest() 056ms

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" 1s 082ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 271ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 061ms

When Accept or reject "reject" transferred transport 17s 985ms

Then Verify that transport is accept or reject "reject" 15s 038ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

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" 1s 135ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 209ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 099ms

And If user is login then logout 106ms

And Login as "paa1-carrier@qa.qa-test" 1s 464ms

Then Verify that the transport has been transferred with "true" 1s 182ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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" 967ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 191ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 19s 149ms

And If user is login then logout 104ms

And Login as "paa1-carrier@qa.qa-test" 1s 688ms

Then Verify that the transport has been transferred with "false" 1s 189ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

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" 1s 999ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 253ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 14s 002ms

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: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.zAPrEe}, 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=90.0.4430.93, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 4d6287096dfe598f5ebe874fc309261b
	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:198)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:278)
	at CucumberTests.Transport.TransferTransportTest.transferTransportToCarrier(TransferTransportTest.java:43)
	at ✽.Transfer transport to carrier "Przewoźnik SKZ Automat 1"(file:Features/Atom/Transport/TransportTransfer/TransportTransfer.feature:26)

And If user is login then logout 000ms

And Login as "pskza1-carrier@qa.qa-test" 000ms

Then Verify that the transport has been transferred 000ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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" 1s 327ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 185ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 13s 986ms

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: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.zAPrEe}, 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=90.0.4430.93, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 4d6287096dfe598f5ebe874fc309261b
	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:198)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:278)
	at CucumberTests.Transport.TransferTransportTest.transferTransportToCarrier(TransferTransportTest.java:43)
	at ✽.Transfer transport to carrier "Przewoźnik SKZ Automat 1"(file:Features/Atom/Transport/TransportTransfer/TransportTransfer.feature:26)

And If user is login then logout 000ms

And Login as "pskza1-carrier@qa.qa-test" 000ms

Then Verify that the transport has been transferred 000ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

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" 1s 205ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 381ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 164ms

And Go to auction offer 1s 226ms

When Offer "1000" 147ms

And Verify that offer with "1000" has been added to auction 3s 032ms

And If user is login then logout 081ms

And Login as "swisskrono-admin" 1s 198ms

Then Go to auction details 1s 199ms

And Pass transport to carrier from auction details 1s 254ms

And If user is login then logout 567ms

And Login as "pskza1-carrier@qa.qa-test" 1s 235ms

And Verify that the transport has been transferred 16s 098ms

Error message

java.lang.AssertionError: Nie znaleziono przycisków transakcji dla przekazanego transportu!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Transport.TransferTransportTest.checkIfTransportIsTransferred(TransferTransportTest.java:68)
	at CucumberTests.Transport.TransferTransportTest.verifyThatTheTransportHasBeenTransferred(TransferTransportTest.java:59)
	at ✽.Verify that the transport has been transferred(file:Features/Atom/Transport/TransportTransfer/TransportTransfer.feature:49)

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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" 1s 180ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 215ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 087ms

And Go to auction offer 1s 186ms

When Offer "1000" 113ms

And Verify that offer with "1000" has been added to auction 3s 032ms

And Wait till auction end 1m 54s 016ms

And If user is login then logout 489ms

Then Login as "swisskrono-admin" 1s 266ms

And Go to auction details 1s 164ms

And Pass transport to carrier from auction details 1s 240ms

And If user is login then logout 5s 519ms

And Login as "pskza1-carrier@qa.qa-test" 1s 162ms

And Verify that the transport has been transferred 16s 125ms

Error message

java.lang.AssertionError: Nie znaleziono przycisków transakcji dla przekazanego transportu!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Transport.TransferTransportTest.checkIfTransportIsTransferred(TransferTransportTest.java:68)
	at CucumberTests.Transport.TransferTransportTest.verifyThatTheTransportHasBeenTransferred(TransferTransportTest.java:59)
	at ✽.Verify that the transport has been transferred(file:Features/Atom/Transport/TransportTransfer/TransportTransfer.feature:69)

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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" 1s 441ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 213ms

And Go to "TRANSPORT_TABLE" 125ms

When Open transport transfer modal 1s 208ms

Then Verify that all enabled companies from "swisskrono" are shown in select 121ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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" 115ms

And Reject main section of a "Przewoźnik Adama Automat 1" in "adama" by API 408ms

And Login as "adama-admin" 930ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 211ms

And Go to "TRANSPORT_TABLE" 122ms

When Open transport transfer modal 1s 197ms

Then Verify that "Przewoźnik Adama Automat 1" is blocked in select 143ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

After Hooks.rollbackRejectedSections() 088ms

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" 969ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 194ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" with "120" seconds to accept transport 19s 157ms

And If user is login then logout 079ms

When Login as "paa1-carrier@qa.qa-test" 1s 877ms

And Verify that the transport has been transferred with "true" 1s 256ms

And Wait "120" seconds 2m

Then Verify if transport is not visible to carrier after expiring time to accept transport 15s 030ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

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" 1s 059ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 321ms

When Go to "TRANSPORT_TABLE" 125ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 366ms

Then Check if new assortment group is disabled in transport form 022ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

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" 1s 019ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 184ms

And Get inputs from database "CREATE_ADVICE_CONTAINER" "super-admin-adama" 002ms

When Show all transport types 1s 041ms

And Click button advice in transport table "CONTAINER" 106ms

And Set advice window in schedule 2s 492ms

And Click button cancel in advice form 15s 303ms

And Set advice window in schedule 2s 106ms

And Click button cancel in advice form 15s 220ms

And Set advice window in schedule 2s 174ms

And Fill advice form 15s 571ms

And Click advice save button and wait for advice form to disappear 30s 675ms

And Go to "TRANSPORT_TABLE" 155ms

And Go to transport details "CONTAINER" 4s 347ms

Then Check are advice values equals 2s 336ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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" 1s 132ms

And Get inputs from database "CREATE_TRANSPOSRT_ORDER" "super-admin-adama" 001ms

When Go to new transport "TRANSPORT" 325ms

And Fill transport form 26s 640ms

And Click "save-transport-and-close" save button and wait for form to disappear 10s 567ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@type='submit' and @data-field-name='save-transport-and-close'] (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: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.zAPrEe}, 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=90.0.4430.93, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 4d6287096dfe598f5ebe874fc309261b
	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:198)
	at Pages.Transport.TransportFormPage.clickSaveButtonAndWaitForFormToDisappear(TransportFormPage.java:192)
	at CucumberTests.Transport.CreateTransport.clickSaveButtonAndWaitForFormToDisappear(CreateTransport.java:188)
	at ✽.Click "save-transport-and-close" save button and wait for form to disappear(file:Features/Scenario/TransportTransfer.feature:9)

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 000ms

And Check is transport "TRANSPORT" created in transport table and set transport id 000ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 000ms

And Accept or reject "reject" transferred transport 000ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 000ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 000ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 000ms

And Accept or reject "accept" transferred transport 000ms

Then Verify that transport is accept or reject "accept" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

View Feature Transport transfer full scenario

@deleteTransportAfterTest

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" 1s 196ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-piast" 001ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 176ms

When Show all transport types 1s 030ms

And Click button advice in transport table "DELIVERY" 148ms

And Set advice window in schedule 2s 591ms

And Click button cancel in advice form 15s 367ms

And Go to "TRANSPORT_TABLE" 201ms

When Go to transport details "DELIVERY" 4s 511ms

And Fill transport form 1m 1s 913ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 635ms

And Go to transport details "DELIVERY" 4s 388ms

Then Check are transport values equals 24s 693ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@deleteTransportAfterTest	3378	45	82	0	0	3505	338	47	385	6h 10m 23s 578ms	Failed

Tag Report