Project Number Date
ApolloFullRunnerReport apollo-test-2.153 10 wrz 2021, 06:23

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
SK Api - Advice transport 170 2 2 0 0 174 12 2 14 15m 43s 512ms Failed
Feature SK Api - Advice transport
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 551ms
And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 430ms
And Add transport by SKApi in "MGW" assigned to "" 022ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 947ms
When Click button advice in transport table "CONTAINER" 204ms
And Set advice window in schedule 3s 360ms
And Fill advice form 20s 408ms
And Click advice save button and wait for advice form to disappear 33s 247ms
And Go to "TRANSPORT_TABLE" 458ms
And Go to transport details "CONTAINER" 2s 939ms
Then Check are advice values equals 4s 996ms
After Hooks.cleanUserDetailsAfterTest() 2s 320ms
After Hooks.deleteTransportAfterTest() 789ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 475ms
And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 001ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 365ms
And Add transport by SKApi in "MGW" assigned to "" 019ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 091ms
When Click button advice in transport table "OWN_COLLECTION" 235ms
And Set advice window in schedule 3s 357ms
And Fill advice form 20s 364ms
And Click advice save button and wait for advice form to disappear 33s 249ms
And Go to "TRANSPORT_TABLE" 451ms
And Go to transport details "OWN_COLLECTION" 2s 904ms
Then Check are advice values equals 4s 989ms
After Hooks.cleanUserDetailsAfterTest() 2s 094ms
After Hooks.deleteTransportAfterTest() 828ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 225ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 325ms
And Add transport by SKApi in "MGW" assigned to "" 021ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 415ms
When Click button advice in transport table "TRANSPORT_ORDER" 228ms
And Set advice window in schedule 3s 342ms
And Fill advice form 20s 328ms
And Click advice save button and wait for advice form to disappear 33s 316ms
And Go to "TRANSPORT_TABLE" 419ms
And Go to transport details "TRANSPORT_ORDER" 2s 910ms
Then Check are advice values equals 4s 933ms
After Hooks.cleanUserDetailsAfterTest() 2s 304ms
After Hooks.deleteTransportAfterTest() 805ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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
Given Login as "pskza1-carrier" and set token of apiUsername "super-admin-skz" 8s 436ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "pskza1-carrier" details with all notifications and "" by JSON file 3s 396ms
And Add transport by SKApi in "MGW" assigned to "" 019ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 056ms
When Click button advice in transport table "TRANSPORT_ORDER" 213ms
And Set advice window in schedule 3s 455ms
And Fill advice form 20s 448ms
And Click advice save button and wait for advice form to disappear 18s 341ms
And Go to "TRANSPORT_TABLE" 434ms
And Go to transport details "TRANSPORT_ORDER" 2s 818ms
Then Check are advice values equals 4s 945ms
After Hooks.cleanUserDetailsAfterTest() 2s 693ms
After Hooks.deleteTransportAfterTest() 809ms
@deleteTransportAfterTest @cleanUserDetailsAfterTest
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
Given Login as "swisskrono-tradesman" and set token of apiUsername "super-admin-skz" 8s 740ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "swisskrono-tradesman" details with all notifications and "automaty@test.pl" by JSON file 2s 495ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 022ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 343ms
When Click button advice in transport table "TRANSPORT_ORDER" 211ms
And Set advice window in schedule 3s 388ms
And Fill advice form 20s 307ms
And Click advice save button and wait for advice form to disappear 33s 839ms
And Go to "TRANSPORT_TABLE" 497ms
And Go to transport details "TRANSPORT_ORDER" 2s 912ms
Then Check are advice values equals 4s 971ms
After Hooks.cleanUserDetailsAfterTest() 1s 783ms
After Hooks.deleteTransportAfterTest() 824ms
@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" 8s 079ms
And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 001ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 364ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 221ms
When Click button advice in transport table "OWN_COLLECTION" 197ms
And Set advice window in schedule 3s 343ms
And Fill advice form 20s 492ms
And Click advice save button and wait for advice form to disappear 33s 234ms
And Go to "TRANSPORT_TABLE" 490ms
Then Check advice data in SK API database "OWN_COLLECTION" 425ms
After Hooks.cleanUserDetailsAfterTest() 2s 089ms
After Hooks.deleteTransportAfterTest() 805ms
@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" 7s 281ms
And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 000ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 376ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "CONTAINER" created in transport table and set transport id 3s 921ms
When Click button advice in transport table "CONTAINER" 227ms
And Set advice window in schedule 3s 311ms
And Fill advice form 20s 389ms
And Click advice save button and wait for advice form to disappear 33s 245ms
And Go to "TRANSPORT_TABLE" 457ms
Then Check advice data in SK API database "CONTAINER" 233ms
After Hooks.cleanUserDetailsAfterTest() 2s 286ms
After Hooks.deleteTransportAfterTest() 781ms
@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" 7s 381ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 2s 320ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 361ms
When Click button advice in transport table "TRANSPORT_ORDER" 233ms
And Set advice window in schedule 3s 327ms
And Fill advice form 20s 467ms
And Click advice save button and wait for advice form to disappear 33s 367ms
And Go to "TRANSPORT_TABLE" 488ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 094ms
After Hooks.cleanUserDetailsAfterTest() 2s 077ms
After Hooks.deleteTransportAfterTest() 783ms
@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 "pskza1-carrier" and set token of apiUsername "super-admin-skz" 6s 191ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "pskza1-carrier" details with all notifications and "" by JSON file 3s 301ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 040ms
When Click button advice in transport table "TRANSPORT_ORDER" 241ms
And Set advice window in schedule 3s 339ms
And Fill advice form 20s 388ms
And Click advice save button and wait for advice form to disappear 33s 828ms
And Go to "TRANSPORT_TABLE" 479ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 101ms
After Hooks.cleanUserDetailsAfterTest() 3s 059ms
After Hooks.deleteTransportAfterTest() 826ms
@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" and set token of apiUsername "super-admin-skz" 7s 613ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Prepare user "swisskrono-tradesman" details with all notifications and "automaty@test.pl" by JSON file 1s 926ms
And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 025ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 513ms
When Click button advice in transport table "TRANSPORT_ORDER" 227ms
And Set advice window in schedule 3s 387ms
And Fill advice form 20s 376ms
And Click advice save button and wait for advice form to disappear 33s 789ms
And Go to "TRANSPORT_TABLE" 521ms
Then Check advice data in SK API database "TRANSPORT_ORDER" 255ms
After Hooks.cleanUserDetailsAfterTest() 1s 744ms
After Hooks.deleteTransportAfterTest() 836ms
@deleteTransportAfterTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 239ms
And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 967ms
When Click button advice in transport table "CONTAINER" 227ms
And Set advice window in schedule in the past 3s 319ms
And Fill advice form 20s 415ms
And Click advice save button to check error message 193ms
Then Check if possible advice alert is displayed 066ms
After Hooks.deleteTransportAfterTest() 694ms
@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" 2s 773ms
And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 001ms
And Add transport by SKApi in "MGW" assigned to "" 036ms
And Set "advice" inputs from JSON file "EDIT_ADVICE" "super-admin-skz" 001ms
And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 129ms
And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-skz" 4s 003ms
And Go to "TRANSPORT_TABLE" 373ms
When Go to transport details "OWN_COLLECTION" 2s 982ms
And Expand advice panel 254ms
And Edit advice in transport details 19s 263ms
And Fill arrival date field 2s 613ms
And Click "save-transport-and-close" save button and wait for form to disappear 30s 237ms
Then Check advice data in database after edition "OWN_COLLECTION" 106ms
After Hooks.deleteTransportAfterTest() 874ms
@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.
Before Hooks.showScenarioName(Scenario) 000ms
Steps
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 770ms
And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms
And Add transport by SKApi in "MGW" assigned to "" 024ms
And Set "advice" inputs from JSON file "EDIT_ADVICE" "super-admin-skz" 001ms
And Check is transport "CONTAINER" created in transport table and set transport id 6s 937ms
And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-skz" 4s 505ms
And Go to "TRANSPORT_TABLE" 386ms
When Go to transport details "CONTAINER" 2s 973ms
And Expand advice panel 343ms
And Edit advice in transport details 19s 289ms
And Fill arrival date field 2s 638ms
And Click "save-transport-and-close" save button and wait for form to disappear 505ms
Error message 
java.lang.AssertionError: Nie udało się zapisać zmian! Pojawił się komunikat walidacyjny w polu:
[do]
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at Pages.Transport.TransportFormPage.clickSaveButtonAndWaitForFormToDisappear(TransportFormPage.java:200)
	at CucumberTests.Transport.CreateTransport.clickSaveButtonAndWaitForFormToDisappear(CreateTransport.java:202)
	at ✽.Click "save-transport-and-close" save button and wait for form to disappear(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:80)
Then Check advice data in database after edition "CONTAINER" 000ms
After Hooks.deleteTransportAfterTest() 827ms
@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.
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 754ms
And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms
And Add transport by SKApi in "MGW" assigned to "" 020ms
And Set "advice" inputs from JSON file "EDIT_ADVICE" "super-admin-skz" 001ms
And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 709ms
And Create advice by JSON file "CREATE_ADVICE_FOR_TRANSPORT_ORDER" as "super-admin-skz" 4s 857ms
And Go to "TRANSPORT_TABLE" 360ms
When Go to transport details "TRANSPORT_ORDER" 2s 898ms
And Expand advice panel 333ms
And Edit advice in transport details 19s 084ms
And Fill arrival date field 2s 579ms
And Click "save-transport-and-close" save button and wait for form to disappear 481ms
Error message 
java.lang.AssertionError: Nie udało się zapisać zmian! Pojawił się komunikat walidacyjny w polu:
[do]
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at Pages.Transport.TransportFormPage.clickSaveButtonAndWaitForFormToDisappear(TransportFormPage.java:200)
	at CucumberTests.Transport.CreateTransport.clickSaveButtonAndWaitForFormToDisappear(CreateTransport.java:202)
	at ✽.Click "save-transport-and-close" save button and wait for form to disappear(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:80)
Then Check advice data in database after edition "TRANSPORT_ORDER" 000ms
After Hooks.deleteTransportAfterTest() 866ms