Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.162	18 wrz 2021, 06:45

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	457	3	12	0	0	472	45	3	48	52m 38s 488ms	Failed

View Feature Invitation

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if rejected invitation is visible in rejected tab

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

Then Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 1s 433ms

And Prepare user "piast-admin" details with all notifications and "automaty31415@test.pl" by JSON file 1s 352ms

When Login as "piast-admin" 5s 114ms

Then Go to "INVITATIONS_TAB" 678ms

And Go to invitation details 143ms

Then Reject invitation by button as user 281ms

When If user is login then logout 626ms

Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 4s 821ms

And Go to "INVITATIONS_TAB" 532ms

And Go to "REJECTED_TAB" invitation status tab 318ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 167ms

After Hooks.cleanUserDetailsAfterTest() 1s 306ms

View Feature Invitation

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it is possible to invite existing user in order to associate him with principal company [A-7315]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-alrec" 279ms

And Prepare user "dha1-supplier-2" details with all notifications and "automatyy3333@test.pl" by JSON file 1s 660ms

When Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 2s 459ms

And Go to "INVITATIONS_TAB" 507ms

And Create invitation for "existing" user "SUPPLIER" "SUPPLIER" "automatyy3333@test.pl" "PL" 2s 978ms

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 123ms

Hooks

After Hooks.deleteInvitationAfterTest() 189ms

After Hooks.cleanUserDetailsAfterTest() 1s 332ms

View Feature Login feature

@rollbackParameters @unlockUsers @cleanUserDetailsAfterTest @clearUserPasswordDataAfterTest

Scenario Outline Verify that password reset cancel login blockade [A-7286]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skd" 296ms

And Prepare parameter "NUMBER_OF_FAILED_LOGIN_ATTEMPTS" with value: "1" 103ms

Given Failed login as "swiss-krono-delivery-admin-2" 1s 396ms

Then Verify that login error reason is "auth.invalidLoginOrPassword" 594ms

Given Try login as "swiss-krono-delivery-admin-2" 1s 549ms

Then Verify that login error reason is "auth.accountLocked" 314ms

Given Click remind password button 259ms

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

And Send remind password form with email "apolloautomattest@gmail.com" 511ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!" 32s 416ms

And Extract password reset link from mailgun mail 4s 028ms

And Reset password from link 1s 335ms

Then Login as "swiss-krono-delivery-admin-2" with new password 5s 187ms

And User is successfully logged 029ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 006ms

After Hooks.clearUserPasswordDataAfterTest() 490ms

After Hooks.rollbackParameters() 095ms

After Hooks.unlockUsers() 104ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after creating advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-adama" 001ms

And Show all transport types 1s 195ms

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

And Set advice window in schedule 3s 238ms

And Fill advice form 17s 290ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 5s 554ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 295ms

After Hooks.deleteTransportAfterTest() 825ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after creating advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Show all transport types 1s 164ms

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

And Set advice window in schedule 3s 388ms

And Fill advice form 13s 126ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 11s 772ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 066ms

After Hooks.deleteTransportAfterTest() 787ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after creating advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 3s 032ms

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

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

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper" 001ms

And Show all transport types 1s 158ms

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

And Set advice window in schedule 3s 289ms

And Fill advice form 18s 933ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 514ms

After Hooks.deleteTransportAfterTest() 762ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after editing advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 951ms

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

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

And Show all transport types 1s 158ms

And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-adama" 3s 519ms

And Go to "TRANSPORT_TABLE" 396ms

And Go to transport details "CONTAINER" 3s 116ms

And Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-adama" 001ms

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

And Fill transport form 5s 198ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_CONTAINER" "super-admin-adama" 001ms

And Expand advice panel 256ms

And Edit advice in transport details 17s 684ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 26s 766ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 406ms

After Hooks.deleteTransportAfterTest() 853ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after editing advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 5s 519ms

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

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

And Show all transport types 1s 142ms

And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 3s 620ms

And Go to "TRANSPORT_TABLE" 398ms

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

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-piast" 001ms

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

And Fill transport form 1m 8s 905ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_DELIVERY" "super-admin-piast" 000ms

And Expand advice panel 247ms

And Edit advice in transport details 8s 125ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 11s 305ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 119ms

After Hooks.deleteTransportAfterTest() 965ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after editing advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 5s 993ms

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

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

And Show all transport types 1s 167ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper" 3s 721ms

And Go to "TRANSPORT_TABLE" 391ms

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

And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper" 001ms

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

And Fill transport form 28s 826ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_LOAD" "super-admin-keeeper" 001ms

And Expand advice panel 276ms

And Edit advice in transport details 24s 018ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 5s 881ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 475ms

After Hooks.deleteTransportAfterTest() 830ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackWarehousesAccess

Scenario Outline Check if mail was sent to creator after status confirmation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skd" 284ms

And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" and access to "Towary sypkie" warehouse by JSON file 1s 230ms

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

And Confirm status "REPORTING" by Public API "v1" 562ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu" 10s 656ms

Then Check if user got a mail 000ms

And Assign Queue to classification resource: "super-admin-skd" "trociny" "CLASSIFICATION" 1s 064ms

And Assign Place to classification resource: "super-admin-skd" "trociny" "Rozładunek" "UNLOAD" 1s 134ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wyjazd" 10s 871ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 005ms

After Hooks.deleteTransportAfterTest() 887ms

After Hooks.rollbackWarehousesAccess() 1s 669ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackVerificationEmailSettingAfterTest

Scenario Outline Check if verification mail was sent to transport creator

Hooks

Before Hooks.showScenarioName(Scenario) 003ms

Steps

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

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

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

And Login as "dha1-supplier-2" and set token of apiUsername "dha1-supplier-2" 9s 024ms

And Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2" 17s 021ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Weryfikacja danych awizacji" 1m 40s 496ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 718ms

After Hooks.deleteTransportAfterTest() 767ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 478ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @enableDisabledUserAfterTest

Scenario Outline Check if mail was not sent to creator if user is not enabled

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skd" 306ms

And Create transport "CREATE_DELIVERY" by JSON file as "swiss-krono-delivery-producer" 16s 677ms

And Prepare user "swiss-krono-delivery-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 506ms

When Login as "swiss-krono-delivery-producer" 4s 958ms

And Go to "TRANSPORT_TABLE" 511ms

And Show all transport types 15s 063ms

And Check if transport is "visible" in table of transports 080ms

And Disable user "swiss-krono-delivery-producer" 866ms

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

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu" 2m 47s 374ms

Then Check if user did not get an mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 905ms

After Hooks.deleteTransportAfterTest() 905ms

After Hooks.enableDisabledUserAfterTest() 771ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating a new auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 198ms

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowa aukcja" 5s 325ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 254ms

After Hooks.deleteTransportAfterTest() 723ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Add a bid "1500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama" 1s 427ms

And Add a bid "500" to an auction by JSON file as "paa2-carrier" for "super-admin-adama" 2s 188ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 10s 660ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 083ms

After Hooks.deleteTransportAfterTest() 629ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after bid has been added to auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-producer" and set token of apiUsername "super-admin-skz" 10s 940ms

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

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

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

And Add a bid "1500" to an auction by JSON file as "pskza1-carrier" for "pskza1-carrier" 1s 058ms

And Wait till auction end 1m 56s 018ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Dodano nową ofertę" 2m 47s 599ms

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:49)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/AuctionMail.feature:39)

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 421ms

After Hooks.deleteTransportAfterTest() 684ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after auction without bids

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Wait till auction end 1m 57s 016ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Aukcja zakończona bez ofert" 5s 681ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 404ms

After Hooks.deleteTransportAfterTest() 628ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing first place in auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 151ms

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

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

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

And Add a bid "1500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama" 1s 135ms

And Add a bid "500" to an auction by JSON file as "paa2-carrier" for "super-admin-adama" 1s 913ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Oferta przelicytowana" 31s 402ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 095ms

After Hooks.deleteTransportAfterTest() 599ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after winning an auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Add a bid "1500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama" 1s 078ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 1m 39s 702ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 296ms

After Hooks.deleteTransportAfterTest() 574ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after accepting minimal price

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Add a bid "500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama" 1s 889ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 5s 185ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 076ms

After Hooks.deleteTransportAfterTest() 603ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail two hours before auction ends

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "paa1-carrier" and set token of apiUsername "super-admin-adama" 5s 064ms

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji" 1m 2s 390ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 056ms

After Hooks.deleteTransportAfterTest() 662ms

View Feature Discrepancy Report Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after discrepancy report generation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 286ms

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

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

And Go to "TRANSPORT_TABLE" 371ms

And Go to transport details "DELIVERY" 3s 014ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 006ms

And Fill transport form 32s 207ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for visibility of element located by By.xpath: //div[@aria-expanded='true'] (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:179)
	at CucumberTests.Transport.Transport.selectValue(Transport.java:228)
	at CucumberTests.Transport.Transport.fillSelectInput(Transport.java:216)
	at CucumberTests.Transport.Transport.fillFields(Transport.java:172)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:150)
	at CucumberTests.Transport.CreateTransport.fillTransportForm(CreateTransport.java:184)
	at ✽.Fill transport form(file:Features/Atom/Mail/DiscrepancyReportMail.feature:11)
Caused by: org.openqa.selenium.NoSuchElementException: Cannot locate an element using By.xpath: //div[@aria-expanded='true']
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: 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:179)
	at CucumberTests.Transport.Transport.selectValue(Transport.java:228)
	at CucumberTests.Transport.Transport.fillSelectInput(Transport.java:216)
	at CucumberTests.Transport.Transport.fillFields(Transport.java:172)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:150)
	at CucumberTests.Transport.CreateTransport.fillTransportForm(CreateTransport.java:184)
	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.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 Open section: "discrepancy-report-panel" 000ms

And Fill discrepancy report section 000ms

And Go to transport details "DELIVERY" 000ms

And Change filled value in details "rodo-acceptance" "checkbox" "true" "0" 000ms

And Generate discrepancy report 000ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Utworzono protokół niezgodności" 000ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 310ms

After Hooks.deleteTransportAfterTest() 801ms

View Feature Mode of transportation mail

@deleteModeOfTransportationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent after updating mode of transportation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-bausch" 284ms

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

When Create default mode of transportation by API with "pba1-carrier" 674ms

Then Update mode of transportation by API with "pba1-carrier": "BBBB0000" "Model2" "Marka2" "CCCC0000" 378ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Środek transportu BBBB0000 został zaktualizowany" 10s 673ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 591ms

After Hooks.deleteModeOfTransportationAfterTest() 352ms

View Feature Mode of transportation mail

@deleteModeOfTransportationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent after creating mode of transportation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-bausch" 305ms

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

When Create default mode of transportation by API with "pba1-carrier" 616ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowy środek transportu" 5s 184ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 450ms

After Hooks.deleteModeOfTransportationAfterTest() 304ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackAddedAuthorities

Scenario Outline Check if mail was sent to after transport delay

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 799ms

And Prepare user "pha2-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 2s 045ms

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

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

And Go to "WAREHOUSE_TAB" 1s 415ms

And Select warehouse "Serownia" 1s 716ms

And Set week view 1s 229ms

And Show yesterday 1s 149ms

And Move window into the past 540ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na" 1m 1s 701ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 624ms

After Hooks.deleteTransportAfterTest() 830ms

After Hooks.rollbackAddedAuthorities() 165ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackWarehousesAccess

Scenario Outline Check if mail was sent to after transport creation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" and access to "MGW" warehouse by JSON file 1s 821ms

And Wait "60" seconds 1m

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica import" 38s 327ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 160ms

After Hooks.deleteTransportAfterTest() 570ms

After Hooks.rollbackWarehousesAccess() 1s 697ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackWarehousesAccess

Scenario Outline Check if mail was sent to after transport creation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" and access to "MGW" warehouse by JSON file 2s 849ms

And Wait "60" seconds 1m

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica eksport" 42s 723ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 237ms

After Hooks.deleteTransportAfterTest() 578ms

After Hooks.rollbackWarehousesAccess() 1s 665ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację" 5s 894ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 057ms

After Hooks.deleteTransportAfterTest() 840ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to carrier after transport transfer with no confirmation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zostało przekazane nowe zlecenie" 5s 842ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 058ms

After Hooks.deleteTransportAfterTest() 545ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Transfer transport to carrier "Przewoźnik SKZ Automat 1" 34s 784ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację" 5s 497ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 736ms

After Hooks.deleteTransportAfterTest() 849ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing inquiry

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "pskza1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 3s 197ms

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

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

And Add a bid "1500" to an auction by JSON file as "pskza1-carrier" for "pskza1-carrier" 1s 103ms

And Add a bid "500" to an auction by JSON file as "pskza2-carrier-2" for "pskza2-carrier-2" 1s 239ms

Then If user is login then logout 278ms

And Login as "swisskrono-admin" 2s 864ms

And Go to auction details 1s 876ms

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

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 10s 452ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 857ms

After Hooks.deleteTransportAfterTest() 868ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating new inquiry

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "pskza1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 3s 271ms

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

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

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowe zapytanie ofertowe" 5s 268ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 849ms

After Hooks.deleteTransportAfterTest() 707ms

View Feature Remind password

@cleanUserDetailsAfterTest

Scenario Outline Check if remind password http status is ok

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 274ms

And Prepare user "adama-admin" details with all notifications and "automaty10@o2.pl" by JSON file 1s 733ms

Then Send password remind email "automaty10@o2.pl" and check if status is ok 245ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 295ms

View 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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Add transport by SKApi in "MGW" assigned to "" 023ms

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

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

And Set advice window in schedule 3s 306ms

And Fill advice form 20s 452ms

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

And Go to "TRANSPORT_TABLE" 431ms

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

Then Check are advice values equals 4s 954ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 313ms

After Hooks.deleteTransportAfterTest() 809ms

View 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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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 "OWN_COLLECTION" created in transport table and set transport id 4s 111ms

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

And Set advice window in schedule 3s 365ms

And Fill advice form 20s 502ms

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

And Go to "TRANSPORT_TABLE" 433ms

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

Then Check are advice values equals 4s 976ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 166ms

After Hooks.deleteTransportAfterTest() 833ms

View 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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Add transport by SKApi in "MGW" assigned to "" 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 7s 496ms

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

And Set advice window in schedule 3s 350ms

And Fill advice form 20s 385ms

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

And Go to "TRANSPORT_TABLE" 464ms

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

Then Check are advice values equals 4s 996ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 307ms

After Hooks.deleteTransportAfterTest() 823ms

View 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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pskza1-carrier" and set token of apiUsername "super-admin-skz" 8s 424ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms

And Prepare user "pskza1-carrier" details with all notifications and "" by JSON file 3s 354ms

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 3s 967ms

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

And Set advice window in schedule 3s 333ms

And Fill advice form 20s 412ms

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

And Go to "TRANSPORT_TABLE" 452ms

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

Then Check are advice values equals 4s 927ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 737ms

After Hooks.deleteTransportAfterTest() 839ms

View 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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-tradesman" and set token of apiUsername "super-admin-skz" 7s 375ms

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

And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 021ms

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 7s 594ms

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

And Set advice window in schedule 30s 129ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//button[@data-button-name='SHIFT_RIGHT_DAY']"}
  (Session info: headless chrome=93.0.4577.63)
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=93.0.4577.63 (ff5c0da2ec0adeaed5550e6c7e98417dac77d98a-refs/branch-heads/4577@{#1135}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.D4viLm}, 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=93.0.4577.63, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 1a0924b5cf70a34fbe6c4f76f33173e5
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	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.setAdviceWindowInSchedule(AdviceTransport.java:83)
	at ✽.Set advice window in schedule(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:13)

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 762ms

After Hooks.deleteTransportAfterTest() 553ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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.

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

And Add transport by SKApi in "MGW" assigned to "" 021ms

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

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

And Set advice window in schedule 3s 362ms

And Fill advice form 20s 619ms

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

And Go to "TRANSPORT_TABLE" 440ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 311ms

After Hooks.deleteTransportAfterTest() 843ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Add transport by SKApi in "MGW" assigned to "" 021ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

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

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

And Set advice window in schedule 3s 368ms

And Fill advice form 20s 486ms

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

And Go to "TRANSPORT_TABLE" 412ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 309ms

After Hooks.deleteTransportAfterTest() 828ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Add transport by SKApi in "MGW" assigned to "" 034ms

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

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

And Set advice window in schedule 3s 460ms

And Fill advice form 20s 481ms

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

And Go to "TRANSPORT_TABLE" 454ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 265ms

After Hooks.deleteTransportAfterTest() 836ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pskza1-carrier" and set token of apiUsername "super-admin-skz" 6s 461ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms

And Prepare user "pskza1-carrier" details with all notifications and "" by JSON file 3s 636ms

And Add transport by SKApi in "MGW" assigned to "" 024ms

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 3s 689ms

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

And Set advice window in schedule 3s 351ms

And Fill advice form 20s 614ms

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

And Go to "TRANSPORT_TABLE" 478ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 023ms

After Hooks.deleteTransportAfterTest() 819ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-tradesman" and set token of apiUsername "super-admin-skz" 8s 509ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms

And Prepare user "swisskrono-tradesman" details with all notifications and "automaty@test.pl" by JSON file 1s 891ms

And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 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 7s 518ms

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

And Set advice window in schedule 3s 320ms

And Fill advice form 20s 401ms

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

And Go to "TRANSPORT_TABLE" 495ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 686ms

After Hooks.deleteTransportAfterTest() 832ms

View Feature Status rejection

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackWarehousesAccess

Scenario Outline Check if it is possible to reject status by guard in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 4s 528ms

And Prepare user "lantmannen-guard" details with all notifications and "apolloautomattest@gmail.com" by JSON file 822ms

And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 1s 069ms

And Add access to the warehouse "Magazyn - Nowa Sól" to the user "lantmannen-guard" by JSON file 733ms

And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 4s 565ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 815ms

And Check if reject date is not visible 15s 041ms

When Reject status: Book of disinfection 230ms

And Check if reject date is visible 972ms

Then If user is login then logout 263ms

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

And Check if note was added to transport after status rejection 1s 727ms

And Check if history note was added to transport after status rejection - "LOAD" 7s 271ms

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Odrzucenie etapu Księga dezynfekcji" 5s 857ms

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 140ms

After Hooks.deleteTransportAfterTest() 788ms

After Hooks.rollbackWarehousesAccess() 1s 772ms

View Feature User

@cleanUserDetailsAfterTest @TmsLink=A-8005.1

Scenario Outline Check if it is not possible to use the previous password when editing it - remind password [A-8005]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skd" 265ms

And Prepare login page 476ms

And Click remind password button 259ms

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

And Send remind password form with email "apolloautomattest@gmail.com" 560ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!" 33s 177ms

And Extract password reset link from mailgun mail 4s 557ms

And Reset password from link with the same password 1s 564ms

Then Check if alert is displayed "Hasło nie może być takie samo jak aktualne hasło użytkownika." in remind password page 233ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 947ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7965

Scenario Outline Permission - Edit user main data [A-7965]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 280ms

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2" 407ms

When Login as "oaa1-receiver-2" 4s 162ms

And Go to user "oaa1-receiver" details edition by prepared link 107ms

And Change user details "email" to "newEmailAddress@newEmail.com" 1s 042ms

And Change user details "phone" to "123456789" 532ms

Then Save user details 1s 013ms

And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 162ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 673ms

After Hooks.rollbackAddedAuthorities() 245ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

Scenario Outline Permission - Edit user notifications [A-7887]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_USERS_TAB;EDIT_USERS_NOTIFICATION" to user "pskza1-carrier-2" 217ms

When Login as "pskza1-carrier-2" 7s 020ms

And Go to user "pskza1-carrier" details edition by prepared link 093ms

And Expand "other" notification section 2s 387ms

And Select all notifications in "other" section 273ms

Then Save user details 1s 526ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 962ms

After Hooks.rollbackAddedAuthorities() 182ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

Scenario Outline Permission - Edit user main data from other company [A-7887]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 284ms

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;ROLE_EDIT_USERS_MAIN_DATA" to user "adama-buyer" 520ms

And Set user details json of user "oaa1-receiver" 016ms

When Login as "adama-buyer" 4s 855ms

And Go to "USERS_TAB" 1s 509ms

And Find user "oaa1-receiver" 3s 587ms

And Change user details "email" to "newEmailAddress@newEmail.com" 799ms

And Change user details "phone" to "123456789" 454ms

Then Save user details 1s 068ms

And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 163ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 654ms

After Hooks.rollbackAddedAuthorities() 253ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

Scenario Outline Permission - Edit user notifications from other company [A-7887]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;EDIT_USERS_NOTIFICATION" to user "swisskrono-tradesman" 391ms

And Set user details json of user "pskza1-carrier" 009ms

When Login as "swisskrono-tradesman" 9s 257ms

And Go to "USERS_TAB" 1s 544ms

And Find user "pskza1-carrier" 3s 552ms

And Expand "GLUE_FACTORY" notification section 540ms

And Select all notifications in "GLUE_FACTORY" section 1s 380ms

Then Save user details 1s 803ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 089ms

After Hooks.rollbackAddedAuthorities() 225ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@cleanUserDetailsAfterTest	457	3	12	0	0	472	45	3	48	52m 38s 488ms	Failed

Tag Report