Last year we confirmed initial operation of eValid with the first Beta releases of Microsoft's IE9.
Microsoft has made the IE9 RC (Release Candidate) version available and we have retested eValid on that version.
We're pleased to report that all eValid features work 100% normally. There is, of course, some improvement in performand that that is due to the major upgrades Microsoft as made in the IE9 engine.
We'll keep our users posted in case any glitches with eValid operating on the IE9 base show up.
Monday, February 28, 2011
Tuesday, February 15, 2011
Selected User Forum Posts
Beginning in mid-2010 we have directed all technical support questions to the eValid User Forum. We have learned that when one user has an issue, all users can profit from the answer.
Here is an additional selection of some of the posts that we think would be of general interest.
Here is an additional selection of some of the posts that we think would be of general interest.
- 1,000 BU Load -- Details on launching 1,000 BUs in parallel.
- Bug while playing back -- Explanation of apparently curious DWindowSet command behavior.
- How do I look at the entire field in a "Script" element? -- Grabbing the complete contents of an attriute.
- How does eValid do on YUI-built systems? -- How well does eValid handle the YUI libraries?
- eValid IndexFind vs. Xpath -- Performance comparison and operational details explained.
Saturday, February 12, 2011
Geometric Testing Example
Here is a fully worked example that illustrates this basic idea: Oracle CRM On Demand -- Example #1. In this example a "from life" recording of with over 100 commands is converted into a 100% geometric test by adding just 7 new commands to replace some which rely on objects for which the ID tags change continually.
Thursday, February 10, 2011
Selected User Forum Posts
Beginning in mid-2010 we have directed all technical support questions to the eValid User Forum. We have learned that when one user has an issue, all users can profit from the answer.
Here is an additional selection of some of the posts that we think would be of general interest.
Here is an additional selection of some of the posts that we think would be of general interest.
- How long does a section in the middle of my script take? -- Methods for using the built-in timer and related special commands.
- Capturing Runtime Obj Property -- How to read and write specific page element properties.
- What can you guys do about cross-browser testing? -- Using SetUserAgent to "spoof" non-IE browsers.
- Using multiple Object Properties -- IndexFindElementEX can match on multiple object/value pairs.
- DWindowSet Command -- Explanation of special properties of the DWindowSet command.
Monday, February 7, 2011
Geometric Testing Explained
We had a question asked on the forum today about our use of the term "geometric testing"
Yes, you are correct, and we're pleased to explain.
In testing some AJAX based web applications the "recorded from life" script may only work part of the time, due to the dynamic nature of AJAX. So the procedure used to prevent playback de-synchronization is to script extra commands into the script that synchronize the playbak, even in spite of AJAX asynchronous operation. At the same time, we often alter the "from life" commands so that they use DOM-dependent searching and checking, drawing from the rich set of structural testing commands that eValid supports.
We generally call this second level of script a "structural" test because it operates based on structural properties of the page.
When the application is built in a way that the usual structural cues are no longer constant -- most commonly seen when the ID tags in a page all change values between runs -- then something more is needed.
From the structural test we then generate a third variation of it that only uses references to fixed objects on the page -- objects that we know by experimentation don't change value from run to run or when the application is updated.
This extension of a structural test to one that does not rely on specific DOM values is then called a "geometric test" because it relies only on the properties of the geometry of the page...and not on any specific contents.
The sequence of eValid scripts then is natural --> structural --> geometric, in increasing order of independence of page specific facts and properties.
Here is a fully worked example that illustrates this basic idea: Oracle CRM On Demand -- Example #1. In this example a "from life" recording of with over 100 commands is converted into a 100% geometric test by adding just 7 new commands to replace some which rely on objects for which the ID tags change continually.
Look on our website for additional examples of pure-geometric web application tests.
There's been talk about eValid offering another kind of testing based on using the eValid automated browser called "geometric testing". Could you kindly let everyone know what that is all about?
Yes, you are correct, and we're pleased to explain.
In testing some AJAX based web applications the "recorded from life" script may only work part of the time, due to the dynamic nature of AJAX. So the procedure used to prevent playback de-synchronization is to script extra commands into the script that synchronize the playbak, even in spite of AJAX asynchronous operation. At the same time, we often alter the "from life" commands so that they use DOM-dependent searching and checking, drawing from the rich set of structural testing commands that eValid supports.
We generally call this second level of script a "structural" test because it operates based on structural properties of the page.
When the application is built in a way that the usual structural cues are no longer constant -- most commonly seen when the ID tags in a page all change values between runs -- then something more is needed.
From the structural test we then generate a third variation of it that only uses references to fixed objects on the page -- objects that we know by experimentation don't change value from run to run or when the application is updated.
This extension of a structural test to one that does not rely on specific DOM values is then called a "geometric test" because it relies only on the properties of the geometry of the page...and not on any specific contents.
The sequence of eValid scripts then is natural --> structural --> geometric, in increasing order of independence of page specific facts and properties.
Here is a fully worked example that illustrates this basic idea: Oracle CRM On Demand -- Example #1. In this example a "from life" recording of with over 100 commands is converted into a 100% geometric test by adding just 7 new commands to replace some which rely on objects for which the ID tags change continually.
Look on our website for additional examples of pure-geometric web application tests.
Thursday, February 3, 2011
Selected User Forum Posts
Here is an additional selection of some of the posts that we think would be of general interest.
- How do you think eValid fits into applications development? -- Where the fit is best.
- eValid Lowers The Total Cost Of Testing -- ROI and TCO.
- Do my ID tags have to be constant for eValid to work? -- Overcoming dynamic ID-tag value assignments.
- eValid vs. TruClient -- External validation of eValid Technology and Approach.
- Customized Error Report -- How to generate conditional error reports.
Subscribe to:
Posts (Atom)