Everyday Scripting With Ruby
For Teams, Testers, and YouBook - 2006
Provides information on the basics of the Ruby scripting language and how to create scripts using test-driven design.
Ingram Book Company
Readers will be introduced to the Ruby scripting language and the overall craft of scripting in this reference. Common typos, finished scripts ready to use and deploy for testing and other common rote tasks are included.
Marick draws on his experience as a programmer and tester in creating a hands-on text for testers, business analysts, and programmers. Coverage includes an overview of the basics of Ruby and basics of scripting; how to write scripts in a steady, controlled way using test-driven design; how to leverage existing scripts and save time with application frameworks in your job; how to handle common mistakes and typos; and how to communicate more efficiently and effectively with teammates. The text includes a glossary and solutions to the exercises. Marick has authored and co-authored two previous texts on software testing and software development. Distributed in the U.S. by O'Reilly Media. Annotation ©2007 Book News, Inc., Portland, OR (booknews.com)
Ingram Publishing Services
Are you a tester who spends more time manually creating complex test data than using it? A business analyst who seemingly went to college all those years so you can spend your days copying data from reports into spreadsheets? A programmer who can't finish each day's task without having to scan through version control system output, looking for the file you want?
If so, you're wasting that computer on your desk. Offload the drudgery to where it belongs, and free yourself to do what you should be doing: thinking. All you need is a scripting language (free!), this book (cheap!), and the dedication to work through the examples and exercises.
Everyday Scripting with Ruby is divided into four parts. In the first, you'll learn the basics of the Ruby scripting language. In the second, you'll see how to create scripts in a steady, controlled way using test-driven design. The third part is about finding, understanding, and using the work of others--and about preparing your scripts for others to use. The fourth part, more advanced, is about saving even more time by using application frameworks.