Community
Participate
Working Groups
We could think about exposing additional information of CAPs e.g.: String getMethod(); String getParameter(); String getCI(); However we have to make sure to only expose stable / public information.
I think adding a method to retrieve the originally used component identifier instance: org.eclipse.jubula.tools.ComponentIdentifier<T> getIdentifier() would be useful for further CAP processing. Exposing the in the RC-context reflectively called (internal) method name does not make much sense as these information tend to change over time. And accessing the parameter information of the CAP executed should be achieved in a different way e.g. by storing the (only) relevant values within the payload of the execute method.
I believe it would be helpful to provide descriptive information about the CAPs that have been executed e.g. a verbose toString() implementation of the CAP reflecting the data / components / methods used within the execution.
A method to retrieve the originally (untyped) used component identifier: org.eclipse.jubula.tools.ComponentIdentifier getIdentifier() has been added with: http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=c09b2dd1deae0663d73cf075d24d1e297518d27e
Verified by code review and an api-test with the JavaFX Simple Adder.