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.