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.
About This Title
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.
Throughout, you’ll also see how to cope with common mistakes. You’ll learn how to recognize that you’re in a blind alley and recover from it. You’ll even see examples of the most common typos, so that you’ll recognize the symptoms when you see them.
Learn to automate rote tasks
Gain a detailed understanding of working, finished scripts that you can apply directly to your job
Understand programming terminology and concepts
Exploit the unpaid labor of others
Communicate more efficiently and effectively with teammates
Brian Marick graduated in 1981 with one degree in Mathematics and Computer Science and another one in English Literature. In his early career, he continued to be confused about his identity. Sometimes he was a programmer. Sometimes he was a tester. He became better at each because he understood the other.
Brian is the author of The Craft of Software Testing, a book about test design techniques for “programming-in-the-medium”. He was an author of the Manifesto for Agile Software Development and was the second chair of the Agile Alliance board of directors. Because the Agile methods encourage cross-disciplinary work, he’s once again without a fixed identity. When consulting, he sticks his nose into everything.