liveBook · Manning

Edit-test-analyze loop

As explained in Microservices Patterns, Second Edition

The edit-test-analyze loop is an iterative development cycle in which a developer changes code, runs tests, and examines the results.

The edit-test-analyze loop is a developer’s implementation cycle: change code, run tests, and examine the results. It sits inside the broader change-deploy-analyze loop, which carries changes through deployment and feedback. section 5.1

Keep each iteration fast and straightforward by supporting:

  • Code that is easy to understand and change, including changes to the technology stack. section 5.1.1
  • Tests that are easy to write, run quickly, and execute locally. section 5.1.1
  • Limited dependence on other teams; integrate work into the trunk at appropriate intervals for timely feedback. section 5.1.1

Orders business-rule change

A developer changes an Orders business rule and runs its tests in IntelliJ IDEA; they complete within two seconds. Separating web and persistence build projects can also prevent unrelated tests from rerunning when either area changes. section 5.4.1 section 6.3.4

Figure 5.1 The iterative workflow for designing and developing a flow item. It consists of two loops, one nested inside the other. The outer change-deploy-analyze deploys changes into production and analyzes feedback. The change step of the outer loop consists of making a design decisions and the inner edit-test-analyze loop, which is the developer’s workflow for implementing a change.
fast workflow

Use the workflow diagram to distinguish this implementation cycle from the surrounding deployment-and-feedback loop. section 5.1

How Microservices Patterns, Second Edition covers it

How deep it goes
Details the three iteration steps, enabling quality attributes, and test-speed scenarios.
Examples
Uses an Orders business-rule change, two-second local tests, and separated build projects to illustrate faster feedback.
What you can do after
Apply the cycle by changing code, running tests locally, and analyzing results before integrating work into the trunk.
How it connects
Connects the cycle to testability, modifiability, evolvability, trunk integration, and deployment pipelines.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.