|Re: New to Extending Rootkits [message #1782344 is a reply to message #1782292]
||Thu, 22 February 2018 08:27
| Maximilian Reiß
Registered: February 2018
What do you mean by "creating a new Teststep and finding my own component". I thought, if I add a new action, it is added to the list in the lower left corner where the Testcases are, after I open my own Toolkit wich includes the rcpToolkitPlugin. Do I missunderstand something here ?|
Also another thing. The Component in the Application is currently recognized with a supported Type of canvas, even its a table. How can I tell jubula to treat it like the new component I add by the extension. I mean it seems to me that the recognized "Supported Type" is what Jubula thinks the component type is.
It is like I understand single parts, but don't understand the whole prozess of the integration of a new Toolkit and new Components and actions. What does Jubula need from the Extension to recognize the Component as the one added by the Extension plugin ?
Also the recognition depends on diffrent factors for the heuristic match. A strong one is the Path and the name if I understood that right. So how can I use that in the development of the extension, wich path/name is it Jubula is using to search for componenttypes ?
[Updated on: Thu, 22 February 2018 12:19]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01584 seconds