Remove Microservices Remove Software Review Remove TDD
article thumbnail

TDD: primitive obsession ( part 3 )

Apiumhub

Last month we talked about TDD example in software development ( part 1 ) and TDD first cycle ( part 2 ). In this new TDD and primitive obsession article, we will focus on removing duplication and reinforcing the constructors of our entities, something key to have a robust system. TDD: primitive obsession.

article thumbnail

TDD First Cycle ( part 2)

Apiumhub

Let’s continue with our series of TDD articles, in the first part we looked at the theory behind the TDD and Unit Testing. In this second part, TDD First Cycle , we begin to develop our application, an application of notes where a user can write notes and everything that comes to our mind. TDD First Cycle.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Microservices Done Right, Part 2: More Antipatterns to Avoid

Accenture

Microservices architecture has become popular over the last several years. Many organizations have seen significant improvements in critical metrics such as time to market, quality, and productivity as a result of implementing microservices. Recently, however, there has been a noticeable backlash against microservices.

article thumbnail

TDD example in software development (Part I)

Apiumhub

After a while thinking about what type of TDD article to write about and, since there are many of them and very good theoretical ones (written by influencers in the world of software development), I have chosen to develop a mini-project while explaining the key points of the development of the application, basically giving you a TDD example.

article thumbnail

Testing Microservices: How to Share Staging Environments without Tripping Over Each Other

Daniel Bryant

In the previous two parts of this series on Testing Microservices, you have learned about the concept of request isolation and explored how this enables multiple developers to “share” a single staging environment and still get the fast development/testing feedback loops. The first is smart routing.

article thumbnail

AoAD2 Practice: Fast, Reliable Tests

James Shore

With TDD, you run the tests as often as one or two times every minute. If they don’t, you won’t be able to get feedback within 1-5 seconds, and that’s crucial for the TDD loop to work effectively. A narrow test is focused on a small amount of code. The more tests you have, the more important speed and reliability become.

article thumbnail

Interesting facts about software development: statistics 2018

Apiumhub

To get the full report with Interesting facts about software development, click here. Sneak peek: interesting facts about software development. As we all know, software development is a fast-changing field. Almost every year we see new languages, software architectures, containers, methodologies, etc. Ok, let’s start!