testing

A collection of 26 posts

aws

Cómo escribir código Typescript orientado a objetos para AWS Lambda

Han pasado un par de meses desde que entré en el mundo de AWS Lambda. Condensé mi pequeña experiencia en este tutorial para todos aquellos que no estén familiarizados con él.

best practices

Una guía rápida para optimizar tests con Kotlin y Spring Boot

¿Trabajas con Kotlin + Spring Boot + Gradle y tus tests son demasiado lentos? Este artículo es para vos.

elixir

Expressive design in Elixir with polymorphic protocols

In this article Emilio told us how to achieve an elegant and expressive desing in Elixir with polymorphic protocols.

kotlin

How to replace Lombok @Generated with a custom annotation for JaCoCo code coverage reports

Maybe it is Monday and you are pairing to catch up while drinking your morning coffee. When you randomly open the project dependencies file and start wondering why Lombok is there. In this post Guille tell us how to get rid of Lombok!

best practices

A quick guide to Spring Tests optimization

Are you working with Kotlin + Spring Boot + Gradle? Are your tests too slow? Then, this article is for you!

best practices

Los defaults malvados

Trabajar en un proyecto con mucho código heredado siempre es una fuente de grandes aprendizajes. En esta ocasión les presento a los "defaults malvados", como a mí me gustan llamarlos. Son partes de código que pueden hacer mucho daño en una aplicación. Veamos cómo…

refactoring Featured

Refactoring step by step: extract validation logic from a method

How to keep your code with validations clean? here’s a step-by-step example that improves an existing piece of code only using automatic refactorings!

tdd

Fears while writing code for the first time

Fear is an unpleasant feeling, a paralyzer. It doesn’t allow us to move forward. That's why we as humans need to identify when we are in fear and find ways to manage it in the best way. Believe it or not, writing code requires a lot of courage.

code quality

Contando colaboraciones en Cuis Smalltalk

¿Qué tan difícil resultaría hacer un programa que cuente colaboraciones de un método? En Smalltalk, no tan difícil.

best practices

Las 12 propiedades deseables de los tests según Kent Beck

Un análisis sobre el artículo "Test Desiderata" escrito por Kent Beck, en donde se listan 12 propiedades deseables de los tests.

refactoring

El arte de las pequeñas mejoras

Refactorizar es lindo. Pero la realidad nos presenta restricciones (tiempo, alcance, tecnológicas, políticas). Ahí es donde la creatividad toma importancia y debemos lograr un alto impacto en poco tiempo, mientras hacemos crecer nuestro software.

tdd

El primer test

Quizás la mayor dificultad al trabajar con TDD es empezar. ¿Cómo ir más allá de la hoja en blanco? TDD nos invita a aprender muy rápido, a sabiendas que nos vamos a equivocar mucho. ¡a prepararse, pues! ¿Qué características debería tener ese difícil primer test?

tdd

6 tips para una exitosa sesión de TDD

TDD es ~95% práctica. La teoría seguramente la conozcas o la hayas escuchado, el ciclo de Red-Green-Refactor te sea familiar y sepas qué es lo que se hace en cada paso. La práctica es lo difícil... esta es una simple lista de cosas que funcionaron para mí, y que quizás funcionen para vos.

aws

Writing Object-Oriented Typescript Code for AWS Lambda

It’s been a couple months since I entered the world of AWS Lambda. I condensed my little experience in this tutorial post for all of you not familiar with it.

rails

Testing Rake tasks

An essay on Rake tasks, their Rails dependency, the value of testing them and, most of all, how to do it. Testing Rake tasks is essential when you need to keep your project robust and reliable all along. Let me show you how (and why) you should definitely do it.

elixir

Fluent assertions in Elixir

Fluent assertions provide a live documentation of what the code actually does. Here's a small library I wrote in Elixir to make them.

best practices Featured

The Evil Defaults

Working on a project with a lot of legacy code always leaves good lessons. This time I’ll present you what I like to call “evil defaults”, pieces of code that can do a lot of harm in any software project.

tdd Featured

6 tips for a powerful TDD session

TDD is ~95% practice. The theory about it is really simple. Practice is harder, and it's always beneficial to have some guidance as you practice it. Here's a quick list of six tips that may work for you!

java

Java Micro benchmarks (or how to enjoy holidays)

Brief tutorial for setting up a jmh project to measure performance of java code using micro benchmarks

testing

Isolating integration tests from external HTTP services with Talkback

A good test (be it unit or integration) should be fast, isolated, repeatable and in total control of its context. If you're doing integration tests that make real HTTP calls to external services, you're instantly breaking those 4 requirements.

tdd

An Inverted Test Pyramid

Are you familiar with the concept of a "Test Pyramid"? I’ve been working on a project suffering from an inverted pyramid, and here I share the downsides that relying solely on end-to-end tests might have.

tests

Be careful with the mocks

Mocking objects is a common practice when writing tests, however it can be painful when refactoring a class tested with mocks. I will show a simple example to explain the problems that mocking can generate

ruby

Rock Your Ruby: The Value of Value

Go ahead and ask the developer sitting next to you what is the thing that loves the most about Ruby. It should come as no surprise that simplicity, flexibility and expressiveness are the main reasons Ruby junkies just can't get enough of it.

software design

Refactoring legacy code story

Is the following story familiar? A client knocks to your door, asking for help with a software developed by another vendor. He complains about developers always being late to deadlines and every time a new version is delivered there are plenty of things that are not working properly.

object design

Language’s type system and their impact in breaking dependencies

One of the things that makes TDD difficult to apply on existing code (or just “legacy code”) is the dependencies that the object subject to test may have. The more “dependencies” the object has, the more difficult it will be to test it, almost for sure. What makes things even