To test the first hypothesis (that type="email" in the AirTable web page's input tag may have caused the problem), I modified my AirTable test suite and ran another test. Could the " placeholder" text displayed in the AirTable input field be confusing Jubula into thinking that it is dealing with a label instead of an input component? The Simple Adder and Google web page input tags do not use that attribute. Second, the AirTable input tag has an HTML5 placeholder attribute, which causes the text input field to display a short text message inside the input field to give the user a hint as to what to enter in the field. Could that be the reason that Jubula does not recognize the AirTable Email field as an input tag and is treating it as a label? The Jubula application's ComponentConfiguration.xml file contains specifications for a toolkit component and a toolkit component, but there is no specification for a toolkit component. I can see two differences between the tags that might cause the problem I observed.įirst, on the Simple Adder and Google web pages, the type attribute for the input tags is set to "text", whereas the the type attribute for the AirTable input tag is set to "email". I also took a look at the HTML input tags for each of the web pages I mentioned in my OP. So Jubula is trying to handle the wrong kind of component. The object data type that should be passed to the MethodUtils.invokeMethod() method (in the stack trace) should actually be a TextImplClass. The exception that is thrown ( NoSuchMethodException) makes sense, because the LabelImplClass would obviously not have a " rcReplaceText" method, since that class is for label components. On closer inspection of the exception stack trace in my original post (OP), I noticed that the object data type listed in the error message is LabelImplClass. I think I may have discovered the root cause of the error I reported.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |