Test-Driven Web Development with Python

Entrega del libro con rapidez, cuidado y en buen estado, sin maltratos por parte de la paquetería dhl y en menos de 24 horas

I really appreciate the author's attention to detail. Just the right balance, so as not to lose the view from above whilst being very clear about (to me) very important disclosures about his thought process. At random: “But we won’t do them [refactoring] right away, because right now our application is in a broken state.” Again: His thinking out loud about why you’d tend to Model Layer validation rather towards a plethora of form validation. Good to think about; good to hear his reasoning.I think the author'a been very clever to combine so large a number of really important ideas and, at the same time, pay justice to them with just the right amount of detail.It’s so important, this detail. The hundreds of little micro-decisions a programmer decides during each hour of programming: what to call this variable? should I commit now? should I refactor yet? Is it worth writing a test for this? I should break this file / function into smaller pieces as I’m losing control of the idea ….So, to be able to read along with the author's thought processes as we explore new ways of doing things: making micro-decisions about new things we’re just getting to grips with and that still feel a little unfamiliar under our fingers … I very much and appreciate this book. It’s certainly been an eye-opener for me.Plus ... it's an enjoyable read!

No es simplemente un libro de TDD o Django, es un 'todo-en-uno'. Con esto me refiero a que teniendo como telón de fondo TDD te explica como realizar instalaciones tanto en entornos de staging como de producción (en Amazon o similares) para que tus aplicaciones funcionen sin problemas.En mi opinión, capítulos como el 14 (Deploying Our New Code) y el 20 (Continuous Integration) le dan un plus y lo hacen destacar respecto de otros libros que también tratan sobre Django. En dos capítulos tienes compiladas una serie de prácticas que pueden ser varios posts en diferentes blogs de Internet y que te permitirán tener tu aplicación 'up-and-running' y testeada.Esto no significa que el resto de capítulos no aporten nada. Al contrario, sin pretender ser un 'curso de Django', alguien que quiera empezar con esta tecnología puede hacerlo sin demasiados problemas. Harry explica bien los conceptos principales y allí donde es necesario da enlaces para poder profundizar más. Todo esto acompañado con las prácticas de TDD, que es de lo que finalmente trata el libro.Total, creo que si tuviese que quedarme con sólo un libro de Django, sería con este (seguido muy, pero que muy, de cerca por 'Two Scoops of Django').

Der Autor vermittelt sehr gut wie viel Spass es macht mit Hilfe von Test Driven Development Software zu entwickeln.Er fuehrt einen dabei durch alle Phasen von der ersten Idee einer Web-Applikation bis zu einer wirklich sehr gut brauchbaren Version einer To-Do Listen Applikation. Dabei werden ausschliesslich Open Source Tools / Frameworks verwendet wie zum Beispiel Django, git, Selenium, Bootstrap ... Die beschrieben Probleme die im Verlauf der Entwicklung von Software auftreten sind sehr praxisnah und es macht Spass zu lesen wie man professionell mit ihnen umgeht.Vielen Dank Harry J.W. Percival fuer dieses Buch!

This book examines Test Driven Developement (TDD) using Python and the Django framework to build a website. Knowing some Django will help a lot with this book.The site developed throughout the book is a note taking web application whereby a person can create a todo list, or any other type of list.TDD relies on writing tests first and then writing the corresponding code to satisfy the tests. Tests can usually be broken down into functional tests or unit tests, and the author is pretty good at explaining how it works.Some of the early tests start out pretty simple such as creating a test to see if the web server is running. Later as the foundation of the application is built, the tests get more complicated.For the beginning chapters the test driven approach made a lot of sense. However, later on as Javascript code was introduced I did not see as much benefits to the testing approach. Although the author mentions that TDD is something you really have to try yourself to get the full benefits.Overall the note taking app was not that complicated, and I am just not that sure how much the tests helped in the creation of the app. The author even mentioned he could create the app without the tests. In this case, I missed some point along the way of why all the tests were needed.The author has a nice approach of using Git to checkin and commit often. Refactoring is done as well often; both on the tests and the code. It seemed a lot of the lessons of the book were to check in often and refactor often. I could not really tell whether the benefits came from using git well, or from using the tests well.A nice aspect of this book is that it starts building the website from the bottom up, and goes piece by piece. It makes it easier to follow along, and the author is engaging albeit informal. I got a pretty good impression of how TDD works although I was not totally sold on it. This book is worth exploring if you want to learn more about TDD.