[cumulusci.robotframework.Salesforce] Input form data keyword returns a "No form handler" error with new SalesForce API = 59.0
frankeetou opened this issue · comments
Describe the bug
We run a WebDriver test for one of our LWC (Account Creation) and it was working and populating the text fields on a prior apiVersion (58), now on newly created scratch orgs based on apiVersion 59, it's returning the following error:
The keyword implementation we are using
Fill in all required fields for the Quick Create form
${firstName} Get fake data first_name
${lastName} Get fake data last_name
Input form data
... First Name ${firstName}
... Last Name ${lastName}
... Contact Type Alumna/Alumnus. #This is a dropdown field
... Account Relationship Head of Household. #This is a dropdown field
... Legal Credit % 100
... Gift Recognition Credit % 100
That tag: 'lightning-primitive-input-simple'
was introduced within the new v 59 API
We also have the following WARN when executing the tests:
Reproduction steps
- Identify a LWC with text input or checkbox in your org
- Create a sample robot test and use the "input form data" keyword from cumulusci library
- Execute the test
Your CumulusCI and Python versions
MacOs
CumulusCI version: 3.79.0
Python version: 3.11.3
Windows 11
CumulusCI version: 3.79.0
Python version: 3.10
Operating System
MacOs Ventura 13.0 and Windows 10
Windows environment
PowerShell
CumulusCI installation method
None
Error Gist
No response
Additional information
NOTE: Multipick (dropdown) fields are working fine! with this keyword
Did anyone find a way to work around that bug? @frankeetou , what are you doing in the meantime?
Not a quick one , but the workaround would be using selenium commands or keywords with different locators (depending on the locators strategy your are using). Unfortunately this is one of the most important UI keywords from CCI Salesforce Library (in my opinion). Still waiiting to see if they are going to tackle it or not
I agree, it's definitely not trivial keyword given that pretty much any new records creation test would need to have an Name field populated. Let's hope it gets fixed quickly.
I agree, it's definitely not trivial keyword given that pretty much any new records creation test would need to have an Name field populated. Let's hope it gets fixed quickly.
@RobertoMartinez-districtm just FYI, the workaround we are doing right now is using the "Populate Form" keyword instead.. which is field specific.
Thanks! Will try it out
Has this been fixed with v3.83.0?