Wednesday, July 30, 2008
Sunday, July 27, 2008
This example shows that eValid handles YUI-built applications and also illustrates use of eValid's IndexMotion commands and internal timer commands to create a script that could serve well in functional testing, regression test, and monitoring test roles.
Monday, July 21, 2008
There was a post on the Google Testing Blog (Motto: If it ain't broke, you're not trying hard enough!) that seems to be pleading for two things we've already developed.
In response in part to the Google Blog's notion of "layer of abstraction" as a way to characterize a solution we pointedout that we had already prepared a simple description of eValid in terms of its command language. We are also working on additional "abstract models for other aspects of the eValid solution Here's the item: eValid As An Abstract Model: An Initial Analysis.
Meanwhile, the Google Blog item also alluded to issues surrounding testing Google Web Toolkit applications. Testing GWT is straightforward for eValid, as our example showing tests of the GWT Kitchen Sink widgets illustrates. Here's the link: eValid Operation with GWT "Kitchen Sink"Confirmed.
Saturday, July 19, 2008
But not every test command (test action) requires extrinsic synchronization, and in many cases the extra step of having to figure out how to add in a synchronization step isn't even necessary because the intrinsic synchronization is good enough. This table summarizes all of eValid's Synchronization Modes. As you can see there are many different ways that playback synchronization can be maintained.
For tough AJAX applications you usually need to rely on one of the DOM-based synchronization modes, e.g. SyncOnElementProperty or SyncOnText. Those commands need to have their parameters filled in manually through use of the PageMap facility to find the right element properties (attributes) and their values. Our worked example that shows how we test the Google Gmail Example is a good illustration of how this works out in practice
Thursday, July 17, 2008
Here's the list of scheduled presentations (in alphabetic order by paper title):
- Advances in Automated Software Testing Technologies, by Elfriede Dustin
- Atom Publishing Protocol, Testing a Server Implementation, by David Calavera
- Automated Model-Based Testing of Web Applications, by Oluwaseun Akinmade and Prof. Atif M Memon
- Boosting Your Testing Productivity with Groovy, by Andres Almiray
- Deployment and Test Automation: Extending the Notion of 'Done' to 'System Tested on a Production Deployment', by Marc-Elian Begin
- JInjector: a Coverage and End-To-End Testing Framework for J2ME and RIM, by Julian Harty, Olivier Gaillard, and Michael Sama
- Practicing Testability in the Real World, by Vishal Chowdhary
- Taming the Beast: How to test an AJAX Application, by Markus Clermont and John Thomas
- The New Genomics: Software Development at Petabyte Scale, by Matt Wood
- The Value of Small Tests, by Christopher Semturs
Tuesday, July 15, 2008
After several go-arounds, her response was, basically, that it would be great to have an simple, fully-automated way to find out if a particular search string produced a valid clickable link in the first page of search results, and do this across multiple search engines. That second part of the request was the sticky one: just showing a text item was there on the results page was not enough. You really had to know there was a real live link that someone could click that would take you to a specific URL. Making one script for multiple search engines was going to be tricky, too.
The resulting SEO Demonstration Script is a parametric script, expressed in terms of the name of the search engine, the locations of the search-string entry field, the location and properties of the "go get it" action field, and of course the input search string and required URL fragment. To make the script 100% reliable -- we don't want to have to rewrite this script if the search engine pages change -- we worked out the Search Engine Parameters for a number of different search engines.
We ran the parametric script using one of eValid's methods for multiple-script playbacks (e.g. DataSynthesis mode among several options) with very interesting results. Natural enough we searched for "eValid" and discovered lots of references in places we didn't think we'd be referenced. Interesting indeed, the differences we found.
Friday, July 11, 2008
Monday, July 7, 2008
We've been developing already-worked examples of eValid tests of difficult websites or hard-to-test web applications for some time now, and there are quite a few of them completed. We thought it would be interesting to organize these in a way that shows off how example illustrates one or more features of the eValid test engine:
- Analysis of the DOM of the page for particular properties.
- Explicit playback synchronization based on page properties.
- Use of eValid page-position-independent "index motion" commands.
- Support for AJAX operations, including synchronization.
- Use of eValid's ability handle Regular-Expression matches.
- Use of one of eValid's many page-based validation modes.
The result is our Application Support Coverage Matrix, which describes what we have done so far.
Thursday, July 3, 2008
The movie illustrates eValid's ability to do page tuning, functional testing, and server loading, all from the same base. The new 3WAY Movie [shows in a new window, duration 05:39] illustrates how simple this can be.