JohnKo wrote:Afternoon.
Been doing some checking.
You've been involved in testing web browser applications for, well, it looks like over ten years?
Do you think that this is still and important problem and do you think you have it solved?
Where do you see automated web testing going in the future?
Thanks
Thanks for asking JohnKo.
Indeed, we have concentrated our efforts on what may seem like a very narrow area, web application testing, but it turns out that it is very broad.
In addition to "conventional web applications" or what you sometimes hear described as Web 1.0 app, we now see a landscape of AJAX (or Web 2.0) applications, mashups, web services, support for mobile devices, social networking applications, geomapping and geolocation, ...and the list seems to grow and grow.
What times them all together is that they are all concerned with the interaction between a application view (the browser) and a complex of software running on servers everywhere.
This is really not the forum to preach too much, but if you think about it this is clearly the wave of the future.
And as you may appreciate, a LOT can go wrong with such applications, particularly as they become more and more complex. The bigger the bug, the bigger the costs are likely to be, and the more people will want to avoid failures.
The key idea of capturing (or, if not actually capturing, scripting) and automatically synthesizing a test playback is central to identifying web application behavior -- and that is central to assuring the quality of that kind of application.
To us it appears very much to be an important growing industry.
-- eValid Support
