Open jstockwin opened 8 years ago
@jstockwin not sure I fully understand but if this is just an option that the field should know about then use the options property of the test config spec. For example, this is how the password field test uses options:
browser.adminUIItemScreen.assertFieldUIVisible({
fields: [
{ name: 'fieldA', options: { passwordShown: false }, },
{ name: 'fieldB', options: { passwordShown: false }, }
],
});
I guess in your case you can do something like:
browser.adminUIItemScreen.assertFieldUIVisible({
fields: [
{ name: 'fieldA', options: { wysiwyg: true }, },
{ name: 'fieldB', options: { wysiwyg: false }, }
],
});
Currently, our
html
fieldTestObject is not smart enough to deal withwysiwyg
fields. We should add a config option to cope with this, as it's a very common use case.My old PR is very stale and out of date, so I'll try to look at this again. @webteckie Can you think of any better ways of doing this other than passing in a
wysiwyg: true
in the modelTestConfig, and that triggers the fieldTestObject to use different selectors?