Community
Participate
Working Groups
I've found that a common feature that users ask for is to have support in recording and playing back test cases in an RCP application. The general dependence of the test framework on the IDE environment has to be investigated. Based on this investigation, further enhancements may need to be opened to eliminate some of the test components dependence on the IDE environment. Users may not get the full advantage of the test framework in an IDE environment but they should generally be given a fairly consistent user interface to record and playback test cases.
Declaring a dependency on 109880
Description Document: http://www.eclipse.org/tptp/groups/Architecture/documents/features/hf_114159.html
Both RCP and stand-alone SWT applications would be beneficial.
Could this technology be used for general record/playback ("macros") in Eclipse, like in bug 8519?
(In reply to comment #4) > Could this technology be used for general record/playback ("macros") in > Eclipse, like in bug 8519? Hi,I don't think this new feature can only be used in Eclipse frameword.We really hope this feature can support us in not only Eclipse,but also some other Application Framework such as IE and Mozela.Thanks ! I really hope more people will vote for it!
proposed to be planned for 4.2 but no resources are available (helpwanted keyword added)
Target set to 4.2
Hi My company has a RCP application that would benefit greatly from this product enhancement. The tool looks good and I can't wait to use and have my developers use verification hooks to test new UI features. Thanks, Ricardo Garcia
helpwanted for 4.3
At the moment, we are using WindowTester where I work: http://www.instantiations.com/rcpdeveloper/index.html Would fixing this bug result in functionnality similar to that commercial product? We have had some amount of success but it is a bit painful and does not track every event at the moment. We also don't just record entire "acceptance tests" for the application but unit test each dialog which is more useful because there is too much setup otherwise - the test becomes too complicated.
Since JFace apps are mostly based on actions, adding a recording API to Action might already get some way where we need to be. I mean, there is no need to actually click the buttons (determining their position, sending mouse events, etc). I'm thinking about something like the Java logging API or maybe even (ab-)using the logging API to record events. But we would need to spread Action everywhere (for example, into Dialog und subclasses). The next step would be to add this API to all the SWT classes like Text, StyledText, Tree, etc, so they could record events.
Based on feedback from our EclipseWorld 2006 TPTP Automated Services Framework talk -- RCP support was stressed as very important from our students.
As part of this bug I would like a way of simulating mouse and keyboard events within test cases. Both as part of automated acceptance tests but also part of rolling some GUI testing into my unit tests.
Can I expect this feature in next release of TPTP
Whether the Scirpt recorded for GUI test case can be integrated with the URL test script,that is to say, we can test the URL command and IE interface(GUI object) in the same test case. Not sure whether the execution mechanisms of GUI test and URL test,can anyone help to explain it to me? Thanks.
(In reply to comment #15) > Not sure whether the execution mechanisms of GUI > test and URL test This sentence makes no sense. What are you talking about? :-)
(In reply to comment #15) In TPTP, you currently cannot mix test types (https://bugs.eclipse.org/bugs/show_bug.cgi?id=123277).
(In reply to comment #14) We are still working through the TPTP 4.4 planning cycle (http://dev.eclipse.org/mhonarc/lists/tptp-pmc/msg02658.html) but this feature is one of the higher priority features for 4.4 since TPTP needs to automated our RCP Log Analyzer and RCP Symptom Database Editor. However, including this feature is a question of resources which we are still in the process of planning. Would you or CA be interested in contributing resources for this feature?
Hi Paul, I have discussed your query with the management team over here. I am unhappy to say at this point of time me or CA will not be able to contribute towards this feature.
Updating target to future as requested by the PMC. Enhancements are targeted to future if not in plan for the current release.
Reassigning to current component lead.
Correcting priority since not a 4.5 candidate enhancement (see http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html).
In TPTP 4.5, the AGR was moved from a Technology Preview component to an As-Is component. As-Is components are primarily provided for prior users but imply no support (for example, defects, news group, and mailing lists) or commitment to triage or resolve opened defects. For this defect to be considered, please re-open with an attached patch including code to resolve the symptom and test cases to test the fix.
Closing by default since not closed by the originator in the 7+ months since being resolved. Please reopen if the issue is still present in the latest TPTP release or the resolution is not correct.
