Cucumber-JVM Reports - Tag: @rollbackAddedAuthorities

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.68	21 sie 2021, 05:16

	Steps	Scenarios	Features
@rollbackAddedAuthorities	364	1	5	0	0	370	39	1	40	6m 27s 039ms	Failed

View Feature Company

Scenario Outline Check if it possible to create and edit company [A-6812]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Set basic authorities "ROLE_CREATE_COMPANY" to user "super-admin-skz" 125ms

And Clear all cache 1s 159ms

And Login as "super-admin-skz" 2s 545ms

And Create company "Firma automaty" 1s 907ms

And Edit company "Firma automaty" 873ms

Then Company is successfully edited 166ms

Hooks

After Hooks.deleteCompanyAfterTest() 015ms

After Hooks.rollbackAddedAuthorities() 033ms

View Feature Company

@deleteCompanyAfterTest @rollbackAddedAuthorities

Scenario Outline Check if it possible to add company patron in company details

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-pgf" 090ms

And Set basic authorities "ROLE_CREATE_COMPANY" to user "pgf-admin" 029ms

When Create company "Twój Opiekun PGF" "supplier" by JSON file as "super-admin-pgf" 104ms

And Login as "pgf-admin" 1s 324ms

And Go to "COMPANIES_TAB" 499ms

And Go to company "Twój Opiekun PGF" details 164ms

And Select company patron "PGF SUPPLY EMPLOYEE" 3s 589ms

Then Verify if "PGF SUPPLY EMPLOYEE" data is successfully added 057ms

Hooks

After Hooks.deleteCompanyAfterTest() 027ms

After Hooks.rollbackAddedAuthorities() 026ms

View Feature Company

@removeAllAddedPartnership @rollbackAddedAuthorities

Scenario Outline Check if admin can manage partnership of supplier with carrier in contractor's details - adding partnership [A-7386]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_SHOW_PARTNERSHIP_TABLE" to user "adama-admin" 028ms

And Login as "adama-admin" 1s 467ms

And Go to "COMPANIES_TAB" 365ms

And Go to company "Dostawca Adama Automat 1" details 170ms

Then Verify that user has correct partnership management permissions "adama-admin" 222ms

And Set existing partnerships 15s 036ms

When Go to form for adding a new single partnership 100ms

Then Verify that partnership form is visible 037ms

And Verify that each company suggested in partnership form is "Przewoźnik" 1s 110ms

When Fill partnership form 1s 241ms

Then Check if "single" contractor is "visible" on partnership list "connectedCompany" 575ms

When Go to "CARRIER_TAB" 337ms

And Go to details of company in partnership 319ms

Then Check if "single" contractor is "invisible" on partnership list "Dostawca Adama Automat 1" 30s 102ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 16s 355ms

View Feature Company

@removeAllAddedPartnership @rollbackAddedAuthorities

Scenario Outline Check if admin can manage partnership of supplier with carrier in contractor's details - adding partnership [A-7386]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_SHOW_PARTNERSHIP_TABLE" to user "neuca-admin" 022ms

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

And Go to "COMPANIES_TAB" 459ms

And Go to company "Przewoźnik Neuca Automat 3" details 191ms

Then Verify that user has correct partnership management permissions "neuca-admin" 165ms

And Set existing partnerships 15s 025ms

When Go to form for adding a new single partnership 109ms

Then Verify that partnership form is visible 032ms

And Verify that each company suggested in partnership form is "Dostawca" 1s 127ms

When Fill partnership form 1s 204ms

Then Check if "single" contractor is "visible" on partnership list "connectedCompany" 726ms

When Go to "COMPANIES_TAB" 369ms

And Go to details of company in partnership 186ms

Then Check if "single" contractor is "visible" on partnership list "Przewoźnik Neuca Automat 3" 120ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 16s 354ms

View Feature Company

@rollbackAddedAuthorities

Scenario Outline Check if only admins have the authority to manage partnerships in the contractor's details - admins [A-7536]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_SHOW_PARTNERSHIP_TABLE" to user "neuca-admin" 019ms

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

And Go to "COMPANIES_TAB" 318ms

And Go to company "Przewoźnik Neuca Automat 1" details 181ms

Then Verify that user has correct partnership management permissions "neuca-admin" 182ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Company

@rollbackAddedAuthorities

Scenario Outline Check if only admins have the authority to manage partnerships in the contractor's details - admins [A-7536]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_SHOW_PARTNERSHIP_TABLE" to user "super-admin-neuca" 020ms

And Login as "super-admin-neuca" 1s 619ms

And Go to "COMPANIES_TAB" 296ms

And Go to company "Przewoźnik Neuca Automat 1" details 168ms

Then Verify that user has correct partnership management permissions "super-admin-neuca" 158ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Company

@removeAllAddedPartnership @rollbackAddedAuthorities

Scenario Outline Removal of partnership by admin [A-7482]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_SHOW_PARTNERSHIP_TABLE" to user "adama-admin" 019ms

And Login as "adama-admin" 982ms

When Go to "COMPANIES_TAB" 292ms

And Go to company "Dostawca Adama Automat 2" details 180ms

Then Verify that user has correct partnership management permissions "adama-admin" 191ms

And Set existing partnerships 15s 028ms

When Add all partnership 809ms

Then Check if "all" contractor is "visible" on partnership list "connectedCompany" 436ms

And Set number of partnerships 009ms

And Check if only companies from principal are visible "Adama" 039ms

When Remove partnership 627ms

Then Check that partnership has been deleted 013ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 16s 372ms

View Feature Company

@removeAllAddedPartnership @rollbackAddedAuthorities

Scenario Outline Removal of partnership by admin [A-7482]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_SHOW_PARTNERSHIP_TABLE" to user "neuca-admin" 020ms

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

When Go to "COMPANIES_TAB" 323ms

And Go to company "Przewoźnik Neuca Automat 2" details 181ms

Then Verify that user has correct partnership management permissions "neuca-admin" 194ms

And Set existing partnerships 027ms

When Add all partnership 769ms

Then Check if "all" contractor is "visible" on partnership list "connectedCompany" 477ms

And Set number of partnerships 007ms

And Check if only companies from principal are visible "Neuca" 047ms

When Remove partnership 622ms

Then Check that partnership has been deleted 019ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.removeAllPartnership() 1s 410ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 818ms

And Select warehouse "Serownia" 1s 397ms

And Set week view 1s 094ms

And Show yesterday 1s 054ms

And Move window into the past 305ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

After Hooks.cleanUserDetailsAfterTest() 326ms

After Hooks.rollbackAddedAuthorities() 018ms

View Feature Schedule

@rollbackAddedAuthorities

Scenario Outline Check if it is possible to change pallet limit in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_CAN_CREATE_MAX_PALLET" to user "pgf-admin" 070ms

And Go to "WAREHOUSE_TAB" 674ms

When Check if pallet limit counter is visible 027ms

And Set limit to "888" 334ms

Then Verify if pallet limit in schedule changed to "888" 047ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Authorities

@rollbackAddedAuthorities @TmsLink=A-7052

Scenario Outline Check if it is possible to add new basic authority to user role group [A-7052]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Go to "SETTINGS_TAB" 332ms

When Go to "PRODUCER" authorities settings 555ms

And Click add authority button 073ms

And Select "Dostęp do zakładki Ogłoszenia" in authority select 682ms

And Click save authority button 101ms

And Expand "ANNOUNCEMENT" panel 222ms

Then Check if basic authority "Dostęp do zakładki Ogłoszenia" is "visible" in "ANNOUNCEMENT" authority panel 029ms

Hooks

After Hooks.rollbackAddedAuthorities() 025ms

View Feature Authorities

@rollbackAddedAuthorities @TmsLink=A-7052

Scenario Outline Check if it is possible to add new basic authority to user role group [A-7052]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Go to "SETTINGS_TAB" 348ms

When Go to "WAREHOUSE_MANAGER" authorities settings 291ms

And Click add authority button 065ms

And Select "Dostęp do zakładki Ogłoszenia" in authority select 513ms

And Click save authority button 082ms

And Expand "ANNOUNCEMENT" panel 252ms

Then Check if basic authority "Dostęp do zakładki Ogłoszenia" is "visible" in "ANNOUNCEMENT" authority panel 022ms

Hooks

After Hooks.rollbackAddedAuthorities() 025ms

View Feature Authorities

@rollbackAddedAuthorities @TmsLink=A-7052

Scenario Outline Check if it is possible to add new basic authority to user role group [A-7052]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 1s 529ms

And Go to "SETTINGS_TAB" 302ms

When Go to "SALES_EMPLOYEE" authorities settings 251ms

And Click add authority button 074ms

And Select "Dostęp do zakładki Ogłoszenia" in authority select 511ms

And Click save authority button 090ms

And Expand "ANNOUNCEMENT" panel 197ms

Then Check if basic authority "Dostęp do zakładki Ogłoszenia" is "visible" in "ANNOUNCEMENT" authority panel 027ms

Hooks

After Hooks.rollbackAddedAuthorities() 026ms

View Feature Authorities

@rollbackAddedAuthorities @TmsLink=A-7052

Scenario Outline Check if it is possible to add new basic authority to user role group [A-7052]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-farmacol" and set token of apiUsername "super-admin-farmacol" 1s 688ms

And Go to "SETTINGS_TAB" 303ms

When Go to "ANALYST" authorities settings 213ms

And Click add authority button 071ms

And Select "Dostęp do zakładki Ogłoszenia" in authority select 524ms

And Click save authority button 079ms

And Expand "ANNOUNCEMENT" panel 190ms

Then Check if basic authority "Dostęp do zakładki Ogłoszenia" is "visible" in "ANNOUNCEMENT" authority panel 022ms

Hooks

After Hooks.rollbackAddedAuthorities() 020ms

View Feature Authorities

@rollbackAddedAuthorities @TmsLink=A-7052

Scenario Outline Check if it is possible to add new basic authority to user role group [A-7052]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Go to "SETTINGS_TAB" 320ms

When Go to "BUYER" authorities settings 243ms

And Click add authority button 072ms

And Select "Dostęp do zakładki Ogłoszenia" in authority select 524ms

And Click save authority button 077ms

And Expand "ANNOUNCEMENT" panel 189ms

Then Check if basic authority "Dostęp do zakładki Ogłoszenia" is "visible" in "ANNOUNCEMENT" authority panel 023ms

Hooks

After Hooks.rollbackAddedAuthorities() 018ms

View Feature Authorities

@rollbackAddedAuthorities @TmsLink=A-7052

Scenario Outline Check if it is possible to add new basic authority to user role group [A-7052]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 1s 485ms

And Go to "SETTINGS_TAB" 291ms

When Go to "FORWARDING_AGENT" authorities settings 234ms

And Click add authority button 066ms

And Select "Dostęp do zakładki Ogłoszenia" in authority select 539ms

And Click save authority button 091ms

And Expand "ANNOUNCEMENT" panel 233ms

Then Check if basic authority "Dostęp do zakładki Ogłoszenia" is "visible" in "ANNOUNCEMENT" authority panel 025ms

Hooks

After Hooks.rollbackAddedAuthorities() 025ms

View Feature Sorting

@rollbackAddedAuthorities

Scenario Outline Check if icons change correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "sempertrans-admin" and set token of apiUsername "super-admin-sempertrans" 989ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "sempertrans-admin" 022ms

When Go to "TRANSPORT_TABLE" 135ms

And Click button "UNLOAD_TIME_WINDOW" "0" times 3s 018ms

Then Verify that "UNLOAD_TIME_WINDOW" icon is "fa-sort" 015ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities

Scenario Outline Check if icons change correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "sempertrans-admin" and set token of apiUsername "super-admin-sempertrans" 982ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "sempertrans-admin" 026ms

When Go to "TRANSPORT_TABLE" 119ms

And Click button "UNLOAD_TIME_WINDOW" "1" times 3s 061ms

Then Verify that "UNLOAD_TIME_WINDOW" icon is "fa-sort-up" 017ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities

Scenario Outline Check if icons change correctly

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "sempertrans-admin" and set token of apiUsername "super-admin-sempertrans" 964ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "sempertrans-admin" 020ms

When Go to "TRANSPORT_TABLE" 116ms

And Click button "UNLOAD_TIME_WINDOW" "2" times 3s 093ms

Then Verify that "UNLOAD_TIME_WINDOW" icon is "fa-sort-down" 019ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities

Scenario Outline Check if icons change correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "sempertrans-admin" and set token of apiUsername "super-admin-sempertrans" 1s 007ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "sempertrans-admin" 017ms

When Go to "TRANSPORT_TABLE" 128ms

And Click button "UNLOAD_TIME_WINDOW" "3" times 3s 135ms

Then Verify that "UNLOAD_TIME_WINDOW" icon is "fa-sort" 017ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports time window dates sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-sempertrans" 095ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "sempertrans-admin" 019ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" in "0" days 1s 226ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" 1s 158ms

And Login as "sempertrans-admin" 938ms

When Go to "TRANSPORT_TABLE" 217ms

And Click button "UNLOAD_TIME_WINDOW" "1" times 3s 057ms

Then Verify that values in "UNLOAD_TIME_WINDOW" are sorted "asc" in "sempertrans" "DELIVERY" 048ms

Hooks

After Hooks.deleteTransportsAfterTest() 160ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports time window dates sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-sempertrans" 099ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "sempertrans-admin" 022ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" in "0" days 1s 209ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" 1s 157ms

And Login as "sempertrans-admin" 949ms

When Go to "TRANSPORT_TABLE" 222ms

And Click button "UNLOAD_TIME_WINDOW" "2" times 3s 088ms

Then Verify that values in "UNLOAD_TIME_WINDOW" are sorted "desc" in "sempertrans" "DELIVERY" 046ms

Hooks

After Hooks.deleteTransportsAfterTest() 134ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports time window dates sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-sempertrans" 095ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "sempertrans-admin" 019ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" in "0" days 1s 194ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" 1s 159ms

And Login as "sempertrans-admin" 929ms

When Go to "TRANSPORT_TABLE" 217ms

And Click button "UNLOAD_TIME_WINDOW" "4" times 3s 173ms

Then Verify that values in "UNLOAD_TIME_WINDOW" are sorted "asc" in "sempertrans" "DELIVERY" 047ms

Hooks

After Hooks.deleteTransportsAfterTest() 174ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports time window dates sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-sempertrans" 095ms

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "sempertrans-admin" 019ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" in "0" days 1s 205ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-sempertrans" 1s 164ms

And Login as "sempertrans-admin" 898ms

When Go to "TRANSPORT_TABLE" 234ms

And Click button "UNLOAD_TIME_WINDOW" "5" times 3s 219ms

Then Verify that values in "UNLOAD_TIME_WINDOW" are sorted "desc" in "sempertrans" "DELIVERY" 050ms

Hooks

After Hooks.deleteTransportsAfterTest() 128ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports statuses sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "neuca-admin" 019ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days 1s 383ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 1s 346ms

When Confirm status "ARRIVE" by Public API "v1" 164ms

And Login as "neuca-admin" 913ms

When Go to "TRANSPORT_TABLE" 210ms

And Click button "STATUS" "1" times 3s 089ms

Then Verify that values in "STATUS" are sorted "asc" in "neuca" "DELIVERY" 064ms

Hooks

After Hooks.deleteTransportsAfterTest() 192ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports statuses sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "neuca-admin" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days 1s 392ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 1s 349ms

When Confirm status "ARRIVE" by Public API "v1" 070ms

And Login as "neuca-admin" 848ms

When Go to "TRANSPORT_TABLE" 216ms

And Click button "STATUS" "2" times 3s 113ms

Then Verify that values in "STATUS" are sorted "desc" in "neuca" "DELIVERY" 060ms

Hooks

After Hooks.deleteTransportsAfterTest() 207ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports statuses sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "neuca-admin" 022ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days 1s 335ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 1s 343ms

When Confirm status "ARRIVE" by Public API "v1" 101ms

And Login as "neuca-admin" 895ms

When Go to "TRANSPORT_TABLE" 199ms

And Click button "STATUS" "3" times 3s 145ms

Then Verify that values in "STATUS" are sorted "asc" in "neuca" "DELIVERY" 058ms

Hooks

After Hooks.deleteTransportsAfterTest() 184ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports statuses sorts correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "neuca-admin" 018ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days 1s 366ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 1s 314ms

When Confirm status "ARRIVE" by Public API "v1" 082ms

And Login as "neuca-admin" 860ms

When Go to "TRANSPORT_TABLE" 209ms

And Click button "STATUS" "2" times 3s 119ms

Then Verify that values in "STATUS" are sorted "desc" in "neuca" "DELIVERY" 056ms

Hooks

After Hooks.deleteTransportsAfterTest() 173ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports are correctly sorted after switching tabs

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "neuca-admin" 019ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days 1s 395ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 1s 365ms

When Confirm status "ARRIVE" by Public API "v1" 080ms

And Login as "neuca-admin" 875ms

When Go to "TRANSPORT_TABLE" 201ms

And Click button "STATUS" "1" times 3s 065ms

And Verify that values in "STATUS" are sorted "asc" in "neuca" "DELIVERY" 051ms

Then Go to "WAREHOUSE_TAB" 588ms

And Go to "TRANSPORT_TABLE" 181ms

And Verify that values in "STATUS" are sorted "asc" in "neuca" "DELIVERY" 089ms

Hooks

After Hooks.deleteTransportsAfterTest() 177ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports are correctly sorted after switching tabs

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "neuca-admin" 020ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days 1s 376ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 1s 347ms

When Confirm status "ARRIVE" by Public API "v1" 084ms

And Login as "neuca-admin" 882ms

When Go to "TRANSPORT_TABLE" 202ms

And Click button "STATUS" "2" times 3s 112ms

And Verify that values in "STATUS" are sorted "desc" in "neuca" "DELIVERY" 062ms

Then Go to "WAREHOUSE_TAB" 595ms

And Go to "TRANSPORT_TABLE" 174ms

And Verify that values in "STATUS" are sorted "desc" in "neuca" "DELIVERY" 135ms

Hooks

After Hooks.deleteTransportsAfterTest() 191ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports are correctly sorted after logging in again

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "neuca-admin" 021ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days 1s 361ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 1s 343ms

When Confirm status "ARRIVE" by Public API "v1" 084ms

And Login as "neuca-admin" 872ms

When Go to "TRANSPORT_TABLE" 254ms

And Click button "STATUS" "1" times 3s 061ms

And Verify that values in "STATUS" are sorted "asc" in "neuca" "DELIVERY" 063ms

Then If user is login then logout 140ms

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

And Go to "TRANSPORT_TABLE" 202ms

And Verify that values in "STATUS" are sorted "asc" in "neuca" "DELIVERY" 180ms

Hooks

After Hooks.deleteTransportsAfterTest() 186ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature Sorting

@rollbackAddedAuthorities @deleteTransportsAfterTest

Scenario Outline Check if transports are correctly sorted after logging in again

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Set basic authorities "ROLE_SORT_TRANSPORT_TABLE" to user "neuca-admin" 018ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "0" days 1s 329ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 1s 324ms

When Confirm status "ARRIVE" by Public API "v1" 081ms

And Login as "neuca-admin" 949ms

When Go to "TRANSPORT_TABLE" 208ms

And Click button "STATUS" "2" times 3s 105ms

And Verify that values in "STATUS" are sorted "desc" in "neuca" "DELIVERY" 058ms

Then If user is login then logout 118ms

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

And Go to "TRANSPORT_TABLE" 237ms

And Verify that values in "STATUS" are sorted "desc" in "neuca" "DELIVERY" 206ms

Hooks

After Hooks.deleteTransportsAfterTest() 148ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When Go to "WAREHOUSE_TAB" 843ms

And Select warehouse "Serownia" 1s 495ms

And Set week view 1s 098ms

And Show yesterday 1s 069ms

And Move window into the past 298ms

Then Check if window is "red" 4s 029ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

After Hooks.rollbackAddedAuthorities() 051ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 978ms

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

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "lantmannen-admin" 030ms

When Go to "WAREHOUSE_TAB" 841ms

And Select warehouse "Magazyn - Nowa Sól" 2s 452ms

And Set week view 1s 105ms

And Show yesterday 1s 073ms

And Move window into the past 422ms

Then Check if window is "red" 4s 033ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

After Hooks.rollbackAddedAuthorities() 024ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past after add advice by advice button in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 148ms

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

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "piast-admin" 033ms

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

When Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 591ms

And Fill advice form 10s 580ms

And Click advice save button and wait for advice form to disappear 10s 178ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='save'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: 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-2/temp/buildTmp/.com.google.Chrome.2KxY4c}, 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: 27f8686fbbe216e38127d63861020cbd
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:217)
	at Pages.Transport.AdviceFormPage.confirm(AdviceFormPage.java:27)
	at CucumberTests.Transport.AdviceTransport.clickAdviceSaveButtonAndWaitForAdviceFormToDisappear(AdviceTransport.java:179)
	at ✽.Click advice save button and wait for advice form to disappear(file:Features/Atom/TimeWindow/TransportWindow.feature:30)

And Select warehouse "Magazyn Hala A" 000ms

And Set week view 000ms

And Show yesterday 000ms

And Move window into the past 000ms

Then Check if window is "red" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

After Hooks.rollbackAddedAuthorities() 021ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if window counter value in schedule changes

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_ACCESS_TO_NUMBER_OF_WINDOWS" to user "keeeper-admin" 057ms

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper" 547ms

And Go to "WAREHOUSE_TAB" 285ms

And Select warehouse "Magazyn Wyrobów Gotowych" 2s 114ms

And Go to next day in schedule 1s 083ms

And Check if time window counter value equals "1" 079ms

And Select view "DAYS_2" 2s 081ms

And Move advice window "2" 1s 332ms

And Select view "DAY" 2s 067ms

Then Check if time window counter value equals "0" 065ms

And Delete created transport by API 097ms

And Check if time window counter value equals "0" 039ms

And Click in free spot in schedule page to create gray window 179ms

And Check if time window counter value equals "0" 043ms

And Click in free spot in schedule page to create dedicated window 2s 045ms

And Check if time window counter value equals "0" 042ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

After Hooks.rollbackAddedAuthorities() 000ms

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

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2@qa.qa-test" 093ms

When Login as "oaa1-receiver-2@qa.qa-test" 1s 313ms

And Go to user "oaa1-receiver@qa.qa-test" details edition by prepared link 023ms

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

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

Then Save user details 236ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 095ms

After Hooks.rollbackAddedAuthorities() 045ms

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

And Set basic authorities "ROLE_USERS_TAB;EDIT_USERS_NOTIFICATION" to user "pskza1-carrier-2@qa.qa-test" 027ms

When Login as "pskza1-carrier-2@qa.qa-test" 1s 963ms

And Go to user "pskza1-carrier@qa.qa-test" details edition by prepared link 018ms

And Expand "other" notification section 574ms

And Select all notifications in "other" section 101ms

Then Save user details 377ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 147ms

After Hooks.rollbackAddedAuthorities() 024ms

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

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;ROLE_EDIT_USERS_MAIN_DATA" to user "adama-buyer@qa.qa-test" 069ms

And Set user details json of user "oaa1-receiver@qa.qa-test" 001ms

When Login as "adama-buyer@qa.qa-test" 1s 394ms

And Go to "USERS_TAB" 742ms

And Find user "oaa1-receiver@qa.qa-test" 2s 262ms

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

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

Then Save user details 240ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 104ms

After Hooks.rollbackAddedAuthorities() 041ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

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

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;EDIT_USERS_NOTIFICATION" to user "swisskrono-tradesman@qa.qa-test" 053ms

And Set user details json of user "pskza1-carrier@qa.qa-test" 000ms

When Login as "swisskrono-tradesman@qa.qa-test" 1s 913ms

And Go to "USERS_TAB" 817ms

And Find user "pskza1-carrier@qa.qa-test" 2s 235ms

And Expand "GLUE_FACTORY" notification section 233ms

And Select all notifications in "GLUE_FACTORY" section 482ms

Then Save user details 459ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 147ms

After Hooks.rollbackAddedAuthorities() 041ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackAddedAuthorities	364	1	5	0	0	370	39	1	40	6m 27s 039ms	Failed

Tag Report