[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [cdt-dev] Question on testing CDT and Eclipse in general
|
Hi
Lars,
At
QNX, we have been using WinRunner to automate some debug testing for our IDE
product based on Eclipse. Works fine in most of cases. But it's only good for
Windows platform.
Meanwhile, I am looking for volunteers for CDT 3.0 M5 testing, maybe you
want to get some hands-on experience on CDT testing? The test
schedule is attached. Pls let me know if you are interested.
Thanks,
Cheers,
James
CDT
Tester
QNX
Hi,
at
EclipseCon my line manager (Antony Edwards) had a chat with some of you as to
how Symbian could contribute to the CDT effort. One area which was initially
discussed is that Symbian could contribute doing some testing and developing
test harnesses. Before we can commit to anything, we would like to understand
better what is involved in detail and what test strategies other CDT
contributors use.
As far as I can
see there are several areas of testing which can be done:
(1) Junit tests, mostly for back-end (i.e. core
functionality) and unit testing. This seems straightforward as long as no
user-interaction is involved and I guess that is the level at which most test
suites work right now. Please correct me if I am wrong. It also seems that
Junit can be used to do some limited UI testing, but that seems to be quite a
cumbersome approach - particularly when you want to test whether a
dialog/property page behaves currectly when a certain button has been pressed,
etc.
(2) Integration testing and
testing of UI elements: Because Eclipse/CDT does not support scripting the
only way of automatically testing higher level functionality and interactions
is to use a test tool that works based on emitting mouse and keyboard events
and capturing screenshots. We only really know testQuest; and testQuest is not
really suitable for desktop applications. An initial sweep on the web has
shown that there does not seem to be a SWT test framework available. Is
anybody using any such tools and what experiences have you made?
Any feedback would be
welcome.
Best Regards
Lars Kurth
Technology Architect, Core Toolchain
Symbian Software Ltd
**********************************************************************
Symbian Software Ltd is a company registered in England and Wales with
registered number 4190020 and registered office at 2-6 Boundary Row,
Southwark, London, SE1 8HP, UK. This message is intended only for use by the
named addressee and may contain privileged and/or confidential information. If
you are not the named addressee you should not disseminate, copy or take any
action in reliance on it. If you have received this message in error please
notify postmaster@xxxxxxxxxxx and delete the message and any attachments
accompanying it immediately. Neither Symbian nor any of its subsidiaries
accepts liability for any corruption, interception, amendment, tampering or
viruses occurring to this message in transit or for any message sent by its
employees which is not in compliance with Symbian corporate policy.
**********************************************************************
--- Begin Message ---
Title: [cdt-test-dev] Looking for volunteers for CDT3.0 M5 sanity and feature testing
Hello,
I am looking for volunteers as my backup for CDT3.0 M5 testing, since I am
expecting a baby due on March 14th, which is also planned M5 date. Speaking
of the coincidence :-)
The areas I need backups are:
Sanity test level 1
Sanity test level 2
feature testing: Memory View
feature testing: Module View
The proposed M5 test process would be (Thanks Brent for providing this):
------------------------------------------------------------
March 14:
1.Download the M5 Eclipse build and the morning CDT build.
2. Run a quick sanity tests (level 1 and level2, testplans are online) and
report any findings to cdt-test-dev and cdt-dev, summarized by a
SanityThumbsUp (so others can know it's good for testing) or
SanityThumbsDown (so that others can fix the showstoppers and rebuild).
3. If the build is sanitized, alert cdt-test-dev that you are starting a day
or so of Milestone testing specifically in say Memory View testing and
Module view testing
March 15 (assuming the build is OK):
4. Run Memory view and Module view testing (testplans are online)
5. Summarize your test results to cdt-test-dev with a ContributorThumbsUp
(or a ContributorThumbsDown).
6. Once all test contributors have given their ComponentThumbsUp, you can
summarize to cdt-dev and cdt-test-dev with a MilestoneThumbsUp. This is
dev's cue, to officially declare M5 and to start checking-in code for M6.
All the docs will be available by end of this week on the website:
http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/cdt-home/testingDocs/tes
tPlans/CDT_test_plans.html?cvsroot=Tools_Project
Thanks very much...
James
CDT Tester
QNX
_______________________________________________
cdt-test-dev mailing list
cdt-test-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-test-dev
--- End Message ---