Project Number Date
ApolloFullRunnerReport 2021.AT1.43 05 sie 2021, 04:46

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
SK Api - Advice transport 164 5 5 0 0 174 9 5 14 15m 18s 675ms Failed
Feature SK Api - Advice transport
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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.
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 075ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 363ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 039ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 045ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 296ms
When Click button advice in transport table "CONTAINER" 090ms
And Set advice window in schedule 2s 518ms
And Fill advice form 16s 697ms
And Click advice save button and wait for advice form to disappear 30s 714ms
And Go to "TRANSPORT_TABLE" 154ms
And Go to transport details "CONTAINER" 2s 463ms
Then Check are advice values equals 4s 294ms
Error message 
java.lang.AssertionError: Wartości w formularzu w polu phone-number-prefix są niepoprawne, wartość na stronie: + wartość poprawna: 48
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Transport.Transport.checkAreValuesEquals(Transport.java:136)
	at CucumberTests.Transport.Transport.checkValueInTransportDetails(Transport.java:258)
	at CucumberTests.Transport.AdviceTransport.checkAdviceValues(AdviceTransport.java:145)
	at ✽.Check are advice values equals(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:18)
After Hooks.deleteTransportAfterTest() 113ms
After Hooks.cleanUserDetailsAfterTest() 302ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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.
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 818ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 350ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 037ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 6s 354ms
When Click button advice in transport table "OWN_COLLECTION" 095ms
And Set advice window in schedule 2s 525ms
And Fill advice form 16s 692ms
And Click advice save button and wait for advice form to disappear 30s 717ms
And Go to "TRANSPORT_TABLE" 185ms
And Go to transport details "OWN_COLLECTION" 2s 438ms
Then Check are advice values equals 4s 288ms
Error message 
java.lang.AssertionError: Wartości w formularzu w polu phone-number-prefix są niepoprawne, wartość na stronie: + wartość poprawna: 48
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Transport.Transport.checkAreValuesEquals(Transport.java:136)
	at CucumberTests.Transport.Transport.checkValueInTransportDetails(Transport.java:258)
	at CucumberTests.Transport.AdviceTransport.checkAdviceValues(AdviceTransport.java:145)
	at ✽.Check are advice values equals(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:18)
After Hooks.deleteTransportAfterTest() 112ms
After Hooks.cleanUserDetailsAfterTest() 292ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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.
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 798ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 306ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "" 004ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 037ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 810ms
When Click button advice in transport table "TRANSPORT_ORDER" 085ms
And Set advice window in schedule 2s 504ms
And Fill advice form 16s 680ms
And Click advice save button and wait for advice form to disappear 30s 741ms
And Go to "TRANSPORT_TABLE" 216ms
And Go to transport details "TRANSPORT_ORDER" 2s 444ms
Then Check are advice values equals 4s 282ms
Error message 
java.lang.AssertionError: Wartości w formularzu w polu phone-number-prefix są niepoprawne, wartość na stronie: + wartość poprawna: 48
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Transport.Transport.checkAreValuesEquals(Transport.java:136)
	at CucumberTests.Transport.Transport.checkValueInTransportDetails(Transport.java:258)
	at CucumberTests.Transport.AdviceTransport.checkAdviceValues(AdviceTransport.java:145)
	at ✽.Check are advice values equals(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:18)
After Hooks.deleteTransportAfterTest() 086ms
After Hooks.cleanUserDetailsAfterTest() 279ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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.
Before Hooks.showScenarioName(Scenario) 002ms
Steps
Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 032ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 521ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 036ms
And Add transport by SKApi in "MGW" assigned to "" 002ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 036ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 823ms
When Click button advice in transport table "TRANSPORT_ORDER" 090ms
And Set advice window in schedule 2s 525ms
And Fill advice form 16s 694ms
And Click advice save button and wait for advice form to disappear 30s 669ms
And Go to "TRANSPORT_TABLE" 216ms
And Go to transport details "TRANSPORT_ORDER" 2s 412ms
Then Check are advice values equals 4s 306ms
Error message 
java.lang.AssertionError: Wartości w formularzu w polu phone-number-prefix są niepoprawne, wartość na stronie: + wartość poprawna: 48
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Transport.Transport.checkAreValuesEquals(Transport.java:136)
	at CucumberTests.Transport.Transport.checkValueInTransportDetails(Transport.java:258)
	at CucumberTests.Transport.AdviceTransport.checkAdviceValues(AdviceTransport.java:145)
	at ✽.Check are advice values equals(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:18)
After Hooks.deleteTransportAfterTest() 115ms
After Hooks.cleanUserDetailsAfterTest() 360ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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.
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 785ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 247ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 036ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 884ms
When Click button advice in transport table "TRANSPORT_ORDER" 090ms
And Set advice window in schedule 30s 564ms
Error message 
org.openqa.selenium.TimeoutException: Expected condition failed: waiting for visibility of element located by By.xpath: //div[contains(@class, 'success-alert')] (tried for 30 second(s) with 500 MILLISECONDS interval)
	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.checkElementIsVisible(BasePage.java:177)
	at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:85)
	at ✽.Set advice window in schedule(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:13)
Caused by: org.openqa.selenium.NoSuchElementException: Cannot locate an element using By.xpath: //div[contains(@class, 'success-alert')]
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: driver.version: unknown
	at org.openqa.selenium.support.ui.ExpectedConditions.lambda$findElement$0(ExpectedConditions.java:882)
	at java.util.Optional.orElseThrow(Optional.java:290)
	at org.openqa.selenium.support.ui.ExpectedConditions.findElement(ExpectedConditions.java:881)
	at org.openqa.selenium.support.ui.ExpectedConditions.access$000(ExpectedConditions.java:43)
	at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:205)
	at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:201)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208)
	at Pages.BasePage.checkElementIsVisible(BasePage.java:177)
	at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:85)
	at sun.reflect.GeneratedMethodAccessor254.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.JavaStepDefinition.execute(JavaStepDefinition.java:57)
	at cucumber.runner.PickleStepDefinitionMatch.runStep(PickleStepDefinitionMatch.java:50)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.PickleStepTestStep.run(PickleStepTestStep.java:43)
	at cucumber.runner.TestCase.run(TestCase.java:45)
	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)
And Fill advice form 000ms
And Click advice save button and wait for advice form to disappear 000ms
And Go to "TRANSPORT_TABLE" 000ms
And Go to transport details "TRANSPORT_ORDER" 000ms
Then Check are advice values equals 000ms
After Hooks.deleteTransportAfterTest() 090ms
After Hooks.cleanUserDetailsAfterTest() 233ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 744ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 342ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 037ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 6s 381ms
When Click button advice in transport table "OWN_COLLECTION" 081ms
And Set advice window in schedule 2s 537ms
And Fill advice form 16s 684ms
And Click advice save button and wait for advice form to disappear 30s 716ms
And Go to "TRANSPORT_TABLE" 153ms
Then Check advice data in SK API database "OWN_COLLECTION" 142ms
After Hooks.deleteTransportAfterTest() 104ms
After Hooks.cleanUserDetailsAfterTest() 259ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 788ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 340ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "" 004ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 037ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 317ms
When Click button advice in transport table "CONTAINER" 096ms
And Set advice window in schedule 2s 533ms
And Fill advice form 16s 610ms
And Click advice save button and wait for advice form to disappear 30s 681ms
And Go to "TRANSPORT_TABLE" 179ms
Then Check advice data in SK API database "CONTAINER" 084ms
After Hooks.deleteTransportAfterTest() 119ms
After Hooks.cleanUserDetailsAfterTest() 302ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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.
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 802ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 362ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 039ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 038ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 778ms
When Click button advice in transport table "TRANSPORT_ORDER" 085ms
And Set advice window in schedule 2s 532ms
And Fill advice form 16s 702ms
And Click advice save button and wait for advice form to disappear 30s 759ms
And Go to "TRANSPORT_TABLE" 210ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 040ms
After Hooks.deleteTransportAfterTest() 091ms
After Hooks.cleanUserDetailsAfterTest() 265ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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.
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 640ms
And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 460ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 038ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 037ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 1s 143ms
When Click button advice in transport table "TRANSPORT_ORDER" 099ms
And Set advice window in schedule 2s 514ms
And Fill advice form 16s 596ms
And Click advice save button and wait for advice form to disappear 30s 746ms
And Go to "TRANSPORT_TABLE" 215ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 037ms
After Hooks.deleteTransportAfterTest() 105ms
After Hooks.cleanUserDetailsAfterTest() 363ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 937ms
And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 255ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 036ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 002ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 036ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 2s 903ms
When Click button advice in transport table "TRANSPORT_ORDER" 097ms
And Set advice window in schedule 2s 532ms
And Fill advice form 16s 598ms
And Click advice save button and wait for advice form to disappear 30s 698ms
And Go to "TRANSPORT_TABLE" 178ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 091ms
After Hooks.deleteTransportAfterTest() 115ms
After Hooks.cleanUserDetailsAfterTest() 222ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 777ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 036ms
And Add transport by SKApi in "MGW" assigned to "" 004ms
And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 036ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 315ms
When Click button advice in transport table "CONTAINER" 095ms
And Set advice window in schedule in the past 2s 520ms
And Fill advice form 16s 721ms
And Click advice save button to check error message 095ms
Then Check if possible advice alert is displayed 017ms
After Hooks.deleteTransportAfterTest() 105ms
@deleteTransportAfterTest
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.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 112ms
And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 044ms
And Add transport by SKApi in "MGW" assigned to "" 002ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 042ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 390ms
And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 49s 981ms
And Go to "TRANSPORT_TABLE" 193ms
When Go to transport details "OWN_COLLECTION" 2s 445ms
And Expand advice panel 081ms
And Edit advice in transport details 16s 045ms
And Fill arrival date field 2s 241ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 121ms
Then Check advice data in database after edition "OWN_COLLECTION" 025ms
After Hooks.deleteTransportAfterTest() 102ms
@deleteTransportAfterTest
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.
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 190ms
And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 039ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 037ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 308ms
And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 49s 984ms
And Go to "TRANSPORT_TABLE" 172ms
When Go to transport details "CONTAINER" 2s 456ms
And Expand advice panel 098ms
And Edit advice in transport details 16s 026ms
And Fill arrival date field 2s 266ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 077ms
Then Check advice data in database after edition "CONTAINER" 036ms
After Hooks.deleteTransportAfterTest() 129ms
@deleteTransportAfterTest
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.
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 141ms
And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 037ms
And Add transport by SKApi in "MGW" assigned to "" 003ms
And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 036ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 1s 129ms
And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 49s 958ms
And Go to "TRANSPORT_TABLE" 211ms
When Go to transport details "TRANSPORT_ORDER" 2s 467ms
And Expand advice panel 089ms
And Edit advice in transport details 16s 048ms
And Fill arrival date field 2s 277ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 095ms
Then Check advice data in database after edition "TRANSPORT_ORDER" 027ms
After Hooks.deleteTransportAfterTest() 096ms