Download
Getting Started
Members
Projects
Community
Marketplace
Events
Planet Eclipse
Newsletter
Videos
Participate
Report a Bug
Forums
Mailing Lists
Wiki
IRC
How to Contribute
Working Groups
Automotive
Internet of Things
LocationTech
Long-Term Support
PolarSys
Science
OpenMDM
More
Community
Marketplace
Events
Planet Eclipse
Newsletter
Videos
Participate
Report a Bug
Forums
Mailing Lists
Wiki
IRC
How to Contribute
Working Groups
Automotive
Internet of Things
LocationTech
Long-Term Support
PolarSys
Science
OpenMDM
Toggle navigation
Bugzilla – Attachment 63657 Details for
Bug 151249
EclipseCorner Article on Functional Test Automation using TPTP
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Requests
|
Help
|
Log In
[x]
|
Terms of Use
|
Copyright Agent
Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read
this important communication.
Some article change before publishing
AGRArticleChanges_20070412_1453.txt (text/plain), 4.88 KB, created by
Govin Varadarajan
on 2007-04-12 15:25:21 EDT
(
hide
)
Description:
Some article change before publishing
Filename:
MIME Type:
Creator:
Govin Varadarajan
Created:
2007-04-12 15:25:21 EDT
Size:
4.88 KB
patch
obsolete
>[Change 1] In the section entitled "Technology" replace paragraph that begins with "The automation project was turned on its head with......" by the following two paragraphs > >The automation project was turned on its head with the arrival of the Automated GUI Recorder (AGR) from the Test and Performance Tools Platform (TPTP) open source project. This is a very easy-to-use test case recording system that creates simple XML scripts into which verification hooks can easily be inserted and tracked by the test automation framework. Stylistically, it uses the very familiar junit framework and is fully extensible. Work is underway to complete the missing features (drag and drop and GEF figure and palette support) in order to have a complete test automation solution that is not sensitive to minor GUI changes for test case verification. > >It is important to clarify what minor GUI changes means in this context. An example is a difference in the layout of a diagram between two runs of a test case. When bitmap positions are remembered for the entire diagram, even tiny changes in position can cause false positives. During GUI development cycles, layout algorithms are subject to change, which can render the location of an item on the diagram surface differently by a few pixels in a subsequent execution. This makes any bitmap comparison between the full diagrams brittle. Another source of false differences is the slight change in colors that can occur throughout the refinement stages of GUI development. Bitmap comparisons are brittle by definition, and get more and more complex as attempts are made to become color independent, and to create fuzzy location matching. > > >=================================================================== > > >[Change 2] Add the following paragraph as the last paragraph in the section entitled "Technology". Note: whole paragraph is in Italics. > >Note that, as of March 2007, a solution was found that provides a stable and reliable method for recording and playing back diagram and palette events. The basic method was to extend the event stream to include mouse events from diagram and palette controls. The mouse events are anchored to the smallest window possible, which removes the brittleness of location as an issue (i.e. location of a figure on a diagram is not relevant, only location of the mouse event within the figure a much less brittle method.) The events are played back after obtaining the figures edit part. This technique requires that a unique identifier be generated for each figure and that the figure be retrieved just before playing events destined for it. The details are too complex for any further explanation and will require another article. The key point is that we feel that the AGR solution is now complete to the level needed to fully test our application. > > >=================================================================== > > >[Change 3] In the section entitled "Known Problems with AGR 4.2.1 and 4.3", change the line "As an aside, it has been seen in the authors experience, some test case developers, instead of creating test cases from scratch; tend to copy XML script from another similar test case in order to save time." to the following: > >As an aside, it is in the authors experience that some test case developers tend to copy XML script from another similar test case in order to save time instead of creating test cases from scratch. > > >=================================================================== > > >[Change 4] In the section entitled "Concluding Remarks", change the line "Work is underway to provide GEF support in order to provide a complete automated testing environment." to the following. > >Work is underway to provide GEF support in open source in order to provide a complete automated testing environment. > >=================================================================== > > >[Change 5] The title for Figure 3 should appear below the figure. > > >=================================================================== > > >[Change 6] The line spacing between various items in the section entitled "Known Problems with AGR 4.2.1 and 4.3" seems inconsistent. > >=================================================================== > > >[Change 7] The font size of some paragraphs in the section entitled "Known Problems with AGR 4.2.1 and 4.3" seems inconsistent with the rest. > >=================================================================== > > >[Change 8 ] The links to Bugzillas in the section entitled "AGR Feature Enhancements" is inconsistent with the links to Bugzillas in the section entitled "Known Problems with AGR 4.2.1 and 4.3" and else where in the article. > >Example: (Bug 133099 ) appears instead of (https://bugs.eclipse.org/bugs/show_bug.cgi?id=133099). > >Perhaps we could just use the latter format to be consistent with the rest of the article ? > >=================================================================== > >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 151249
:
59682
|
61468
|
61474
|
61544
|
62019
|
62414
| 63657 |
65476
|
67387