Robotframework-assertion-engine v. 3.0.0 causes New Context kw of BrowserLibrary to fail

Libraries
1

Hello, I’ve encountered today an error in my pipeline with a robot setup with BrowserLibrary (v.16.0.0) and Python 3.11.2.
Error in file ‘<my_robot_suite_file>’ on line 2: Initializing library ‘Browser’ with arguments [ enable_playwright_debug=True ] failed: TypeError: Formatter() takes no arguments
Traceback (most recent call last):
File “/opt/hostedtoolcache/Python/3.11.6/x64/lib/python3.11/site-packages/Browser/browser.py”, line 817, in init
Formatter(self),

My python package versions:

Blockquote
robotframework-6.1.1
robotframework-assertion-engine-3.0.0
robotframework-browser-16.0.0
robotframework-pabot-2.1.0
robotframework-pythonlibcore-4.2.0
robotframework-requests-0.9.5
robotframework-seleniumlibrary-6.0.0
robotframework-seleniumtestability-2.1.0
robotframework-stacktrace-0.4.1
rpaframework-27.0.1
rpaframework-core-11.2.0
rpaframework-pdf-7.2.0

I digged out the robotframework-assertion-engine package where the Formatter module is from, and found out that with robotframework-assertion-engine v2.0.0 this error did not occur. I wonder if my package configuration with robotframework-browser v16.0.0 and python 3.11 should be supported at all?

1 Like
2

Here is the discussion about this. My understanding is that this won’t be fixed due to only the latest version of Browser being supported. So your options are to upgrade Browser or pin version 2.0 of assertion engine.

2 Likes
3

Thanks for the description for OP, helped a lot!
We had to set: pip install robotframework-assertion-engine==2.0.0
in to our systems to fix this