Scripted GUI Testing with Ruby 2008
scripted GUI Testing with Ruby (August 15, 2008)
What readers are saying about
scripted GUI Testing with Ruby
If you care about your application, you care about testing. And if you have an application with a user interface, you should care about testing it. This book gives you what you need to start testing in an agile manner, using a modern programming language and excellent techniques. This book covers a wide range of GUI testing and should be in every developer’s bookshelf.
About This Book
As much as I love talking about GUI tests, it’s much more illustrative to show them. So, we’re going to spend the first half of this book building up a test script (“test” in the sense of “set of examples”) for a live application. I don’t mean some toy “pet store” sample project; I mean a real program people are using for something other than writing books on testing.By the halfway point, we’ll have a somewhat typical GUI test project on our hands, with the same refactoring and changing of direction you’d see in the real world. From there, we’ll branch out into a survey of GUI testing topics, leaving behind our one big example for several smaller illustrations.
Who It’s For
This book is for testers who code and for coders who test. It’s the book.
I wish I had four years ago. That’s when I faced the equally unpleasant tasks of fixing old, broken GUI tests and coaxing a rickety third-party toolkit into running new tests. I started looking for a how-to guide on GUI testing to help me down this road.Unfortunately, there were none. Plenty of people had written beautifully about testing in general but not about user interfaces specifically.What few GUI books did exist were long, dry, restricted to technologies I couldn’t use, or built on test frameworks that looked like someone’s homework assignment.Alot of folks are having the same problem I had. Some of you are testers who are sick of hearing the “testers don’t code” slander and want to use scripting in your palette of techniques. Others are QA engineers tired of the messy generated code and clunky APIs of GUI toolkits. Still others are software developers who want to test and improve their own programs.
