with updating to chrome 70 we have issue with running tests open browser action contains driver.maximizewindow() which worked until chrome 69 and still works on every other browser

but after the update to 70 we are getting this error

WebDriverException: Message: unknown error: failed to change window state to maximized, current state is normal (Session info: chrome=70.0.3538.77) (Driver info: chromedriver=2.43.600229 (3fae4d0cda5334b4f533bede5a4787f7b832d052),platform=Mac OS X 10.13.6 x86_64)

@lucianopuccio I don't see any option to set an enhancement label for this issue via the regular issue input from github, so that is why I used [enhancement] in the title.

Looking at the great Zalenium grid container (https://zalando.github.io/zalenium/) and some other remote browser environments, it would be great if Golem would support the following features:

• Setting up a browser instance with dynamically set "desired capabilities" per test case, enabling: -- Custom browser versions / platforms for remote browser tests. -- Naming of recorded test video's within Zalenium in case the testcase name is set via 'desired capabilities'(see referenced website -test name- section).

• Set dynamic cookies during tests. -- In case of Zalenium this would enable referenced test steps in the recorded Video's (see referenced website -Referencing test steps in the recorded video- section-)

In case user needs to pass data in more complex data structures like lists,dictionary,tuples etc, how can it be defined & passed as parameters inside functions(actions)?

Example: List of standard common labels across application pages , to be verified so the list of those labels/objects can be passed around as arguments to functions to verify .

Proposed new, renamed and removed actions

New Actions

• assert
• assert_*
• go_back
• set_search_timeout
• get_search_timeout
• double_click
• drag_and_drop
• focus_element
• close_all_browsers
• set_trace
• error
• execute_javascript
• fail
• javascript_click
• deselect_option_by_text
• deselect_option_by_value
• deselect_option_by_index
• verify_selected_option_by_text
• verify_selected_option_by_value
• get_alert_text
• send_text_to_alert
• submit_prompt_alert
• verify_alert_present
• verify_alert_not_present
• verify_alert_text
• verify_alert_text_is_not
• wait_for_alert_present
• verify_element_has_attribute
• verify_element_has_not_attribute
• verify_page_not_contains_text
• verify_element_text_contains
• verify_element_text_is_not
• verify_element_text_not_contains
• verify_title
• verify_title_contains
• verify_title_is_not
• verify_title_not_contains
• verify_url
• verify_url_contains
• verify_url_is_not
• verify_url_not_contains
• wait_for_element_present
• wait_for_element_not_enabled
• wait_for_page_contains_text
• wait_for_page_not_contains_text
• wait_for_element_text
• wait_for_element_text_is_not
• wait_for_element_contains_text
• wait_for_element_not_contains_text
• wait_for_element_has_attribute
• wait_for_element_has_not_attribute
• wait_for_alert_present
• wait_for_alert_not_present
• wait_for_title
• wait_for_title_is_not
• wait_for_title_contains
• wait_for_title_not_contains
• verify_element_attribute
• verify_element_attribute_is_not
• go_forward
• check_element
• uncheck_element
• submit_form
• switch_to_default_content
• switch_to_frame
• switch_to_parent_frame
• get_window_titles
• get_window_handle
• get_window_handles
• get_window_index
• switch_to_first_window
• switch_to_last_window
• switch_to_window_by_index
• switch_to_window_by_title
• switch_to_window_by_partial_title
• switch_to_window_by_url
• switch_to_window_by_partial_url
• switch_to_next_window
• switch_to_previous_window
• close_window
• close_window_by_index
• close_window_by_title
• close_window_by_url
• close_window_by_partial_title
• close_window_by_partial_url
• verify_window_present_by_title
• verify_window_present_by_partial_title
• verify_window_present_by_url
• verify_window_present_by_partial_url
• verify_amount_of_windows
• wait_for_window_present_by_title
• wait_for_window_present_by_partial_title
• wait_for_window_present_by_url
• wait_for_window_present_by_partial_url
• wait_for_window_not_present_title
• wait_for_window_not_present_url
• wait_for_window_not_present_partial_title
• wait_for_window_not_present_partial_url
• wait_for_amount_of_windows
• maximize_window
• get_element_text
• get_element_value
• verify_element_has_focus
• verify_element_has_not_focus
• get_element_attribute

Renamed Actions

• capture -> take_screenshot
• clear -> clear_element
• close -> close_browser
• debug -> interactive_mode
• mouse_hover -> mouse_over
• select_by_index -> select_option_by_index
• select_by_text -> select_option_by_text
• select_by_value -> select_option_by_value
• verify_alert_is_present -> verify_alert_present
• verify_alert_is_not_present -> verify_alert_not_present
• verify_cookie_exists -> verify_cookie_present
• verify_is_enabled -> verify_element_enabled
• verify_is_not_enabled -> verify_element_not_enabled
• verify_is_selected -> verify_element_checked
• verify_is_not_selected -> verify_element_not_checked
• verify_is_visible -> verify_element_displayed
• verify_is_not_visible -> verify_element_not_displayed
• verify_exists -> verify_element_present
• verify_not_exists -> verify_element_not_present
• verify_text -> verify_page_contains_text
• verify_text_in_element -> verify_element_text
• wait_for_element_not_exist -> wait_for_element_not_present
• wait_for_element_visible -> wait_for_element_displayed
• wait_for_element_not_visible -> wait_for_element_not_displayed

Removed Actions

• assert_contains
• assert_equals
• assert_false
• assert_true
• verify_selected_option

With the current latest source of (22-10-2017) I am experiencing the following GUI bug.

The field indicators when adding a test step that requires multiple arguments is displayed in the incorrect order within the gui. This results in a issue where once calling the test step the function is called with the wrong order of arguments.

Example: The following test step function:

end up being presented as (TOP: correct order for function call, BOTTOM: incorrect initial suggestions, the bug)

The result of the above:

I would like to announce that I will be moving this and some related repos to @golemhq org.

I'm pleased with the feedback the project has got so far and thankful for all the contributions. I want to see it grow to its full potential. This change will help keep things more organized.

Also, I'll be renaming my username shortly after.

How framework supports hard vs. soft assertions inside an test.

Terminology Hard Assertions:Test execution stops as soon as assertion failure found. Soft Assertions:Test execution continues even if assertion failure found.

Environment: OS:Win7 Python: 3.6.3

Steps: 1).Installed Python 3.6.3 in Windows 7 2).Installed Golem by pip install golem-framework. 3).Created the test directory : golem-admin C:\Golem 4).Downloaded Chrome Browser Driver 2.33 and placed inside Drivers folder. 5).Started the web Module: cd C:\Golem python golem.py gui 6).Got the error on command prompt as attached screenshot.

However this is working fine in Python 3.4.4 version.

Starting with the project Error 1 The test run fails due to chromdriver is not properly set. H The chromedriver is in the directory ./drivers/chromedriver*' and its set in the settings on the same path

Error 2: the exception block fails because the variable "msg" is undefined. For which I'm willing to raise Pull Request, does it work?

Stacktrace

13:08:20.951 INFO Test execution started: image_push
13:08:20.951 INFO Browser: chrome
13:08:20.967 ERROR Could not start chrome driver using the path './drivers/chromedriver*', check the settings file.
13:08:20.971 INFO Traceback (most recent call last):
File "/Users/pooja/venv/python3/lib/python3.6/site-packages/selenium/webdriver/common/service.py", line 76, in start
stdin=PIPE)
File "/usr/local/Cellar/python/3.6.5/Frameworks/Python.framework/Versions/3.6/lib/python3.6/subprocess.py", line 709, in __init__
restore_signals, start_new_session)
File "/usr/local/Cellar/python/3.6.5/Frameworks/Python.framework/Versions/3.6/lib/python3.6/subprocess.py", line 1344, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
PermissionError: [Errno 13] Permission denied: '/Users/pooja/venv/python3/golem_fw/drivers/chromedriver_2.38'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/pooja/venv/python3/lib/python3.6/site-packages/golem/browser.py", line 268, in open_browser
chrome_options=chrome_options)
File "/Users/pooja/venv/python3/lib/python3.6/site-packages/selenium/webdriver/chrome/webdriver.py", line 68, in __init__
self.service.start()
File "/Users/pooja/venv/python3/lib/python3.6/site-packages/selenium/webdriver/common/service.py", line 88, in start
os.path.basename(self.path), self.start_error_message)
selenium.common.exceptions.WebDriverException: Message: 'chromedriver_2.38' executable may have wrong permissions. Please see https://sites.google.com/a/chromium.org/chromedriver/home
13:08:20.973 ERROR An error ocurred:
File "/Users/pooja/venv/python3/lib/python3.6/site-packages/golem/test_runner/test_runner.py", line 122, in run_test
test_module.test(execution.data)
File "/Users/pooja/venv/python3/golem_fw/projects/flash/tests/image_push.py", line 10, in test
navigate("https://www.google.com")
File "/Users/pooja/venv/python3/lib/python3.6/site-packages/golem/actions.py", line 337, in navigate
driver = browser.get_browser()
File "/Users/pooja/venv/python3/lib/python3.6/site-packages/golem/browser.py", line 343, in get_browser
open_browser()
File "/Users/pooja/venv/python3/lib/python3.6/site-packages/golem/browser.py", line 273, in open_browser
raise Exception(msg)
NameError: name 'msg' is not defined
Result: fail 
Error: NameError: name 'msg' is not defined 
Elapsed Time: 0.02
Browser: chrome
Steps:

golem run -i works correctly with #97

adding debug() or a import pdb; pdb.set_trace() to a test no longer works, it enters then exits the debugger without stopping.

dbug() log: INFO:golem:Click Login Button Entering interactive debug mode Type exit() to stop

now exiting InteractiveConsole...

pdb log: 13:17:24 INFO Click Login Button INFO:golem:Click Login Button

/home/daniel/Development/golem/FunctionalTests/projects/OSC/tests/forgot_password.py(19)test() -> click(forgot_password.forgot_link) (Pdb) 13:17:27 ERROR An error ocurred: Traceback (most recent call last): File "/home/daniel/Development/golem-dm/env/lib/python3.6/site-packages/golem_framework-0.4.5-py3.6.egg/golem/test_runner/test_runner.py", line 122, in run_test test_module.test(execution.data) File "/home/daniel/Development/golem/FunctionalTests/projects/OSC/tests/forgot_password.py", line 19, in test click(forgot_password.forgot_link) File "/home/daniel/Development/golem/FunctionalTests/projects/OSC/tests/forgot_password.py", line 19, in test click(forgot_password.forgot_link) File "/usr/lib/python3.6/bdb.py", line 48, in trace_dispatch return self.dispatch_line(frame) File "/usr/lib/python3.6/bdb.py", line 67, in dispatch_line if self.quitting: raise BdbQuit bdb.BdbQuit

OS name and version - Win 10 (x64)
Python version - Python 3.6.3 (v3.6.3:2c5fed8, Oct  3 2017, 17:26:49) [MSC v.1900 32 bit (Intel)] on win32
Golem version - I don't know where I can check it (latest installed with pip)

I faced with the following problem: For unknown for me reasons golem doesn't save elements in page objects (without showing any tips or message) or doesn't show objects if I fill it in mode. Sometimes it erased objects if saved it before. More details please see on attached videos: http://recordit.co/by6VOYYFXk http://recordit.co/yzWWx4bUxC