- Taschenbuch: 420 Seiten
- Verlag: Pragmatic Programmers; Auflage: 1 (22. Dezember 2010)
- Sprache: Englisch
- ISBN-10: 1934356379
- ISBN-13: 978-1934356371
- Größe und/oder Gewicht: 19 x 2,3 x 23,5 cm
- Durchschnittliche Kundenbewertung: 1 Kundenrezension
- Amazon Bestseller-Rang: Nr. 185.430 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
The RSpec Book (Facets of Ruby) (Englisch) Taschenbuch – 22. Dezember 2010
|Neu ab||Gebraucht ab|
Kunden, die diesen Artikel gekauft haben, kauften auch
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Wenn Sie dieses Produkt verkaufen, möchten Sie über Seller Support Updates vorschlagen?
""Some authors would be satisfied with just writing the definitive guide for a technology. These folks go a step further, and show you insider tips that will keep your tests clean and maintainable.""--Ian Dees, Software Engineer
""The second generation of tools for the XP generation explained by their creators and maintainers. Awesome, a must read.""--Marcus Ahvne, software developer, Valtech
""The RSpec Book teaches you much more than how to use RSpec's features; it teaches you how to write code the way the RSpec team does: patiently, and with great precision and clarity. There is something here for everyone: beginners are given plenty of gentle attention but there is some real meat for the more experienced reader to chew on, too.""--Matt Wynn, independent programmer and coach
Über den Autor und weitere Mitwirkende
David Chelimsky is the lead developer/maintainer of RSpec, and has contributed to several other open source projects including Cucumber, Aruba, and Rails. He has been developing software for over a decade, including three years training and mentoring agile teams at Object Mentor. He is currently a Senior Software Engineer at DRW Trading Group in Chicago, IL. In his spare time, David likes to play guitar, travel, and speak something resembling Portuguese.
Dave Astels is the Director of Technology at ChannelFireball.com and has been involved with software and computing for over 25 years, recently having spent several years working exclusively with Ruby and Rails. Dave wrote the article that prompted Steven Baker to start the RSpec project.
Bryan Helmkamp maintains Webrat, a Ruby library to implement acceptance tests for web applications in an expressive and maintainable way, and is an active participant in the New York City Ruby community. Bryan is the CTO of Efficiency 2.0, a startup that helps people understand and reduce their energy use.
Dan North writes software and coaches teams and organizations in agile and lean methods. He believes that most problems that teams face are about communication and understanding, which is why he puts so much emphasis on "getting the words right." In 2003-4 this led him to develop the ideas that would become Behaviour-Driven Development. He is delighted by the community that has grown up around RSpec and Cucumber, and especially the enthusiasm and dedication of their core contributors. Dan is currently a Senior Software Engineer at DRW Trading Group in London, where he gets to actually code again!
Zach Dennis is a co-founder and fellow human at Mutually Human Software, an expert custom software strategy and design consultancy in Grand Rapids, Michigan. He has been enjoying Ruby for nearly eight years and has contributed to several projects such as Ruby's standard library documentation, Ruby on Rails, and RSpec. In his spare time, Zach loves spending time with his family, continuously learning, playing music, and running continuousthinking.com.
Aslak Hellesoy is a Senior Software Engineer at DRW Trading Group in London. While contributing to this book he was the Chief Scientist of BEKK Consulting in Oslo. In 2003, after seven years of professional Java programming, he fell in love with Ruby. He has contributed to dozens of open source projects and is the founder of the Cucumberproject. Aslak likes to cook, ski, and travel.
Die hilfreichsten Kundenrezensionen auf Amazon.com
The book is divided in five parts. It feels a bit like the parts are written by different authors independently, which isn't unlikely considering the amount of authors. That's too bad as some cross-referring would have made the book better.
The first part is tutorial style where it simulates implementing a project Behavior-Driven-Development-style (BDD). The project is the traditional problem of code-breaker where you need to guess a code and get some hints on how well you did. It drives the project by first writing cucumber specs, then test-driving the implementation using RSpec. The tutorial is simple (perhaps even simplistic) and goes on for about 100 pages.
The second part of the book is the philosophy behind BDD. It is short, consisting of only 2 chapters. The first describes how traditional projects work... or actually how they do not work. Then it quickly runs over some ideas behind agile development and how that is different. The next chapter makes a case for by showing how BDD actually focuses on the communication between developers and customers.
The third part is the RSpec part of the book (where it got its name :P). It's about a 100 pages and does a pretty good job in describing RSpec. The only thing that I was missing was that it could explain a bit more about the RSpec internals... at least I would have found that interesting.
The fourth chapter is the "and more!" part of the book where is introduces cucumber (in the RSpec book :P). The Cucumber introduction isn't fantastic and is pretty short (and has quite some overlap with the tutorial). I wouldn't recommend this book for the cucumber introduction anyways but instead it would probably be better to read... the cucumber book (published about 2 years later).
The last chapter is the rails chapter where it takes rspec and cucumber and explain how to use the extensions for writing features and specs for rails apps. Here, some of the text is already a bit obsolete as the technology moves fast. Still, the concepts are about the same. It contains 3 chapters on cucumber and 3 on rspec.
All in all, I found it a pretty good read and enjoyed most of it. It could be a bit thinner and faster for me as it felt a bit repetitive at times. Partly this was because because some chapters could be integrated better together. For the RSpec part, I'd rate the book 3 stars as it does a good job in describing rspec. But the book is much more than The RSpec Book... therefore I'll give it 4 stars (yet, for Cucumber, it is better to pick up the Cucumber book)
As I read and tried many of the little tiny examples in the book, and eventually decided that I do not want to do Cucumber (I do not need to spend the extra time to generate code to translate requirements from English, RSpec is clear enough for me). Unfortunately (from my perspective), much of the book rambles on about Cucumber and integrating it with RSpec.
As I went through the book and I found a section of code that interested me, it too frequently told me that I would hear more details later on, which I found quite frustrating. I was ready for the down-low, and never seemed to find it, until I eventually jumped to Chapters 23, 24 and 25. Chapters 23, 24 and 25 are the chapters that walk you through the process of developing Test/Behavior driven View, Controllers and Models. This is what I needed to get my project going.
This book is worth it, even if you only look at the RSpec chapters.
Oh, by the way, when you are looking into the tools you want to use for integration testing, I recommend looking into Capybara, which is not talked about in the book.
I hope this helps.
Dave Taylor (tayloredwebsites.com)
Ähnliche Artikel finden