Cucumber-JVM Reports - Tag: @rollbackSettings

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.127	21 sie 2021, 05:25

	Steps	Scenarios	Features
@rollbackSettings	134	1	1	0	0	136	14	1	15	6m 25s 882ms	Failed

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it is possible to create transport with different transport identifier type by Public API [A-7523]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 253ms

And Set token of apiUsername "super-admin-piast" 241ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 160ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 244ms

When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 744ms

Then Login as "super-admin-piast" 9s 199ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 559ms

After Hooks.rollbackSettings() 173ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it is possible to create transport with different transport identifier type by Public API [A-7523]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 244ms

And Set token of apiUsername "super-admin-piast" 236ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 157ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 162ms

When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 707ms

Then Login as "super-admin-piast" 2s 501ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 669ms

After Hooks.rollbackSettings() 153ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it is possible to create transport with different transport identifier type by Public API [A-7523]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 242ms

And Set token of apiUsername "super-admin-piast" 247ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 153ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 117ms

When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 743ms

Then Login as "super-admin-piast" 2s 615ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 655ms

After Hooks.rollbackSettings() 119ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 252ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 153ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 181ms

And Login by Api as "super-admin-piast" and get token and expect status "200" 246ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 665ms

When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 850ms

Then Check if response status code equals "200" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 669ms

After Hooks.rollbackSettings() 134ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 147ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 149ms

And Login by Api as "super-admin-piast" and get token and expect status "200" 252ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 615ms

When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 829ms

Then Check if response status code equals "422" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 645ms

After Hooks.rollbackSettings() 132ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 143ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 164ms

And Login by Api as "super-admin-piast" and get token and expect status "200" 239ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 628ms

When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 340ms

Then Check if response status code equals "404" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 638ms

After Hooks.rollbackSettings() 128ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 138ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 166ms

And Login by Api as "super-admin-piast" and get token and expect status "200" 245ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 626ms

When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 033ms

Then Check if response status code equals "401" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 663ms

After Hooks.rollbackSettings() 159ms

View Feature API Transport

@deleteTransportsAfterTest @rollbackSettings

Scenario Outline Check if response code contains expected status after editing transport by Api with non unique erpIdentifier [A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 151ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 132ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" with erp identifier "5345467712" 1s 587ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" with erp identifier "5345467712" 1s 628ms

When Edit transport by API-validation JSON file "EDIT_DELIVERY_WITH_FILLED_ERP_IDENTIFIER" as "super-admin-piast" for api version "v1" by identifier "5345467712" 341ms

Then Check if response status code equals "422" 000ms

Hooks

After Hooks.deleteTransportsAfterTest() 000ms

After Hooks.rollbackSettings() 091ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if custom fields map is correct after creating a transport by Public API [A-7508]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 243ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 147ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 153ms

And Login by Api as "super-admin-piast" and get token and expect status "200" 258ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 627ms

And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 303ms

Hooks

After Hooks.deleteTransportAfterApiTest() 642ms

After Hooks.rollbackSettings() 133ms

View Feature API Transport

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it possible to edit transport by API [A-4167]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 165ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 114ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 580ms

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

And Show all transport types 1s 167ms

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

And Set advice window in schedule 3s 747ms

And Fill advice form 13s 617ms

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

When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 1s 647ms

And Check if response status code equals "200" 000ms

And Go to "TRANSPORT_TABLE" 545ms

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

And Expand advice panel 15s 094ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[@id='advice-panel']"}
  (Session info: headless chrome=92.0.4515.131)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.kdJMZk}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 4d8790a524584ba4b90814192eae0275
*** Element info: {Using=xpath, value=//div[@id='advice-panel']}
	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.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.BasePage.getWebElementByXpath(BasePage.java:325)
	at CucumberTests.Transport.AdviceTransport.expandAdvicePanel(AdviceTransport.java:142)
	at ✽.Expand advice panel(file:Features/Api/Transport.feature:170)

Then Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 538ms

After Hooks.rollbackSettings() 138ms

View Feature Filters

@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings

Scenario Outline Check if sorting by "Finished" status is working correctly [A-7517]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get custom field settings for "DELIVERY" transport type and "neuca" company 108ms

And Mark custom fields as not obligatory 007ms

And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 148ms

And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 119ms

When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 7s 028ms

Then Login as "neuca-admin" 2s 347ms

And Go to "TRANSPORT_TABLE" 532ms

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

Then Check if sorting by 'Finished' status is working correctly 329ms

Hooks

After Hooks.deleteTransportsAfterTest() 4s 467ms

After Hooks.rollbackAllCustomFieldsSettings() 359ms

After Hooks.rollbackSettings() 094ms

View Feature Invitation

@rollbackSettings @deleteInvitationAfterTest

Scenario Outline Check if expired invitation is visible in expired tab

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Delete invitations with email "automaty31415@test.pl" 101ms

And If user is login then logout 298ms

Given Set token of apiUsername "super-admin-piast" 259ms

And Get setting "INVITATION_EXPIRATION_INTERVAL" for "piast" 143ms

Then Prepare setting: "INVITATION_EXPIRATION_INTERVAL" with value: "-1d" with "super-admin-piast" by API 228ms

And Create invitation by JSON file "super-admin-piast" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 465ms

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

Then Go to "INVITATIONS_TAB" 510ms

And Go to "EXPIRED_TAB" invitation status tab 271ms

Then Invitation is displayed on list "automaty31415@test.pl" 421ms

Hooks

After Hooks.deleteInvitationAfterTest() 161ms

After Hooks.rollbackSettings() 119ms

View Feature DedicatedWindow

@rollbackSettings

Scenario Outline Check if dedicated window is automatically deleted from schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get setting "AUTOMATIC_DELETING_UNUSED_DEDICATED_WINDOWS_INTERVAL" for "swisskrono" 129ms

And Create "CREATE_DEDICATED_WINDOW" window by JSON file for test as "super-admin-skz" 324ms

And Prepare setting for automatic time window delete with "super-admin-skz" 238ms

When Login as "swisskrono-admin" 7s 881ms

And Go to "WAREHOUSE_TAB" 954ms

Then Check if dedicated window is deleted from schedule 48s 427ms

Hooks

After Hooks.rollbackSettings() 185ms

View Feature Move transport to archive

@rollbackSettings @deleteTransportAfterTest

Scenario Outline Check if delayed transport is moved to archived and can be restored

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 8s 871ms

And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 016ms

And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 146ms

And Set proper delay time to move order to archive after task timeout 135ms

When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 2s 020ms

And Go to "WAREHOUSE_TAB" 984ms

And Change warehouse in schedule to: "Katowice" 1s 765ms

And Wait "60" seconds 1m

And Verify that transport window is grey 078ms

And Verify that transport is in archive 6s 860ms

Then Restore transport from archive 2s 672ms

And Verify that transport has been successfully restored 1s 734ms

Hooks

After Hooks.deleteTransportAfterTest() 767ms

After Hooks.rollbackSettings() 121ms

View Feature Move transport to archive

@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings

Scenario Outline Check if confirming transport status removed it to the archive

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-dayco" 219ms

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 123ms

And Mark custom fields as not obligatory 007ms

And Login as "dayco-admin" 2s 291ms

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

And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 141ms

And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 197ms

When Go to "TRANSPORT_TABLE" 350ms

And Click button advice in transport table "OWN_COLLECTION" 1s 365ms

And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 3s 541ms

And Go to "TRANSPORT_TABLE" 361ms

And Find transport in table with status "planned-magazyn-tychy" 3s 692ms

And Confirm statuses until reach "process-ended" 16s 746ms

And Wait until transport disappear from transport table 22s 565ms

Then Go to "ARCHIVE_TAB" 565ms

And Show "OWN_COLLECTION" 181ms

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

Hooks

After Hooks.deleteTransportAfterTest() 730ms

After Hooks.rollbackAllCustomFieldsSettings() 512ms

After Hooks.rollbackSettings() 122ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackSettings	134	1	1	0	0	136	14	1	15	6m 25s 882ms	Failed

Tag Report