Recursos de programación de bdd
Software development is heavily influenced by many of the most common cognitive biases: technical choices are made following hypes (pro-innovation bias) or gurus (bandwagon bias); we create homemade tools instead of using de-facto standards (not-invented-here syndrome) and fix bugs without a full understanding of the problems (placebo bias) or even we pretend that there isn't any problem at all (ostrich bias). The first step to bring software development closer to an engineering discipline is recognizing this biases and admitting that we all suffer of them.
¿Quieres saber más? Índice interactivo aquí debajo: 01:14 Presentación 01:36 Índice 01:51 1. Introducción 01:55 Quién soy yo 02:18 ¿Qué voy a contar? 03:17 2. Desarrollo 03:20 BDD 07:31 Feature 10:20 Spring Boot 14:55 Código fuente 17:04 Git Flow 20:31 Git 21:53 Automatización 24:42 3. Dockerizado 25:00 Dockerfile 26:29 4. Desplegado 26:49 EC2 Container 28:31 Imagen Docker 30:30 Cloudformation 31:54 CloudFormation Stack 34:52 Demo 1:00:14 5. Preguntas
Le moderne applicazioni web ormai spostano la logica di interfaccia lato client, rendendo JavaScript assoluto protagonista dello sviluppo. Si rende quindi necessario poter testare in maniera automatica questa componente e in questa sessione vedremo, con un approccio molto pratico, tools e tecniche per farlo in maniera sostenibile. Partiremo dai principali framework di testing confrontando l'approccio TDD e BDD; analizzeremo framework e tecniche di mocking; vedremo come rendere testabile codice già scritto e come AngularJS semplifichi notevolmente gli scenari di test.
Aunque lo escribo con retraso, este post corresponde al cuarto día (jueves) de esta edición de la piweek.En el proyecto eventsview avanzamos hasta dejar una versión usable con búsqueda y los filtros activados. Estoy bastante contento, por que aunque no es nada vistoso nos va a valer como base para desarrollos que tenemos que hacer en Alea y que poco a poco voy cogiendo flujo en javascript y en la parte web. Hay que tener en cuenta que en mi día a día no suelo tocar para nada web, por l...
Greach 2015, The Groovy Spanish Conf April 10th-11th, Madrid, Spain Follow us on twitter Slides in #/ Scala is the other Great Force in the realm of alternative JVM languages. It has it’s strengths, as well as it’s weaknesses. This talk will look at Scala as a supplement to Groovy, showing that it can help us tremendously given specific circumstances. We will begin by looking at how Groovy and Scala differ philosophically, followed by a comparison of syntax used in the two languages. We will then dive into the most important part, dealing with their application and how they can coexist side by side. This talk aims to dismantle the wall that prevails between the Groovy and Scala communities, attempting to show that both are highly capable in their own way. It does so by showing that there is no right or wrong, but rather that they are flipsides of the same coin. Marco Vermeulen Marco Vermeulen is a South African Software Developer who lives and works in London. He is passionate about writing well crafted code, driven and guided by tests. As proponent of BDD, he has successfully applied this technique in the Enterprise as well as on Open Source Projects. When he gets a spare moment, he contributes to OSS and is the creator of GVM (the Groovy enVironment Manager).
Además, muchas de las herramientas de su ecosistema han revolucionado prácticas y técnicas que aplicamos a diario. Un buen ejemplo de ello son RSpec y Cucumber: software que abrió brecha en una técnica tan extendida hoy en día como BDD (Behaviour Driven Development). En esta sesión comenzaremos por introducir Ruby, prestando especial atención a las características que lo hacen único.
http , ddd , bdd
I've just watched this great talk by Dave Marshall: Silex: An implementation detailIt's about DDD, BDD, Ports and Adapters and the Entity-Control-Boundary Pattern (EBC). You can find the source code of the examples in this GitHub repository. - por Garajeando
I'm reading Growing Object-Oriented Software Guided by Tests along with several friends from the Aprendices community. In the next months I will be posting here resources to complement the book that are mentioned during our conversations about each chapter of the book. These are the ones mentioned in this week's conversation about the preface and the first chapter: Talks Better is better by Steve FreemanDesign How Your Objects Talk Through Mocking by Konstantin KudryashovBDD con Javascript by C...
Cuando desarrollamos tenemos muchas formas de hacerlo. Desde no hacer nada en especial a dejarnos guiar por determinadas metodologías hasta en la última línea de nuestro código. Revisaremos que opciones (entre muchas más) tenemos y nos centraremos en TDD, DDD y BDD, sus conceptos básicos y que herramientas/librerías existen en PHP para ayudarnos con la que elijamos.
Greach 2014, The Groovy Spanish Conf 28/March, Madrid, Spain Follow us on twitter Slides & source code: Behaviour Driven Development (BDD) is the next step to writing applications that hit the mark! What makes this technique different is that it engages Stakeholders from start to finish of a project. This is done by writing Specifications by Example in collaboration with all Stakeholders. This presentation will use Cucumber combined with the power of Groovy to demonstrate how you can apply BDD to your next project. We will look at using Cucumber in context of both Groovy and Grails applications. We will demonstrate how to use Cucumber's Gherkin syntax to write clear Scenarios, then progress to writing Step Definitions in Groovy, then using Geb to interact with a browser. We will implement the new feature in our Grails application using Spock to test drive our finer grained components. Lastly, we will demonstrate our Cucumber Feature running end-to-end. The purpose of this presentation is to encourage others in the Groovy community to embrace BDD, and to write relevant useful applications Marco Vermeulen Private Contractor Marco Vermeulen is a South African Software Developer who works and lives in London. He spent the past 11 years working with Enterprise Java, having experienced both the benefits and frustrations of the technology. He has survived EJB 2.1, did time with Struts and enjoyed using frameworks like Spring and Hibernate. Having worked with Groovy for the past 5 years and using Grails for the past 2, he has engineered solutions for Shazam, MailOnline and Burberry. He is also the author of GVM, the Groovy enVironment Manager.