Net Objectives

MARCH 25, 2019

Often a given behavior will change due to a certain condition: sometimes the system will behave one way, sometimes another. We call this kind of behavioral change a “boundary” and it should be specified as such in TDD.

Systems Review 40

Systems Review TDD Examples System 40

Net Objectives

MAY 7, 2019

TDD depends on a strong connection between the automation of the test suite and the system itself. The suite should record the specification that is implemented in the system, and the connection allows this to be confirmed at any point. So, if errors creep into the test … Continue reading "Sustainable TDD: Part 3".

Systems Review 40

Systems Review TDD Sustainability Testing 40

Net Objectives

MARCH 20, 2019

Because TDD is “test” driven development, people tend to think of TDD as “writing tests first.” In fact, TDD is not a testing activity per se. It is the creation of an executable specification prior to the creation of each system element. Because of this … Continue reading "Commonly Missing Tests in TDD".

Systems Review 40

Systems Review TDD Testing Test-Driven Development 40

Net Objectives

APRIL 17, 2019

In TDD, tests take actions such as Setup, Trigger, and Verify. Each of these pieces must successfully execute in order for the specification to be verified as accurate to the current behavior of the system. For example, If … Continue reading "TDD and Guard Assertions".

Systems Review 40

Systems Review TDD Testing Examples 40

Net Objectives

MARCH 26, 2019

Recently I wrote about the necessity in TDD of specifying both sides of a behavioral boundary, and its epsilon. This is important because we want a complete, detailed record of the critical business rules and other values in the system. It has to do with the … Continue reading "Specifying Boundaries in TDD: Part 2".

Systems Review 40

Systems Review TDD System 40

Net Objectives

FEBRUARY 25, 2019

I mentioned earlier that TDD offers qualitative measurements about production code, namely that a large average fixture size can be used to measure relative coupling in a system. The Single Responsibility Principle states that every class in … Continue reading "TDD and the Single Responsibility Principle".

Software Review 40

Software Review Systems Review TDD Testing 40

Net Objectives

MARCH 1, 2019

This means that a “good” design will allow for a new behavior to be added to a system without having to change the existing code, or at least to minimize … Continue reading "TDD and the OCP".

Software Review 40

Software Review Systems Review TDD Software 40

Net Objectives

MARCH 27, 2019

The term “workflow” in this sense is meant to indicate the way two system elements interact when performing a task. Often these interactions themselves are not exposed outside the system, and so only their resulting behavior should be tested. This is as true in TDD as it is in traditional testing.

Systems Review 40

Systems Review TDD Testing System 40

Net Objectives

MAY 21, 2019

It is important that the system behaviors we create as developers are both accurate and precise. The level of precision required … Continue reading "TDD and Accuracy vs. Precision". These are not the same. One can be: Accurate, but not precise: “Pi is a little over three.” Precise, but not accurate: “Pi is 5.393858303895.”

Systems Review 40

Systems Review TDD System Development 40

Net Objectives

MARCH 5, 2019

One aspect of strong design is that separation is created between the various concerns of the system. This is one area where … Continue reading "TDD and the Separation of Concerns". This adds clarity, promotes re-use, improves cohesion, and in general adds value to the work.

Systems Review 40

Systems Review TDD System 40

Net Objectives

APRIL 11, 2019

Tests often establish example values used to compare the behavior of the system with the actual behavior indicated in the requirements.

Systems Review 40

Systems Review TDD Testing Examples 40

Net Objectives

FEBRUARY 19, 2019

Project Managers and Product Owners are sometimes dubious about the development team doing TDD. They are concerned that the team will slow down because they’ve been burdened with additional work, and that developers might “game” the system with bogus tests to satisfy the process.

Systems Review 40

Systems Review TDD Development Project Management 40

James Shore

MARCH 29, 2021

To share your thoughts, join the AoAD2 open review mailing list. Test-driven development, , or TDD, is a rapid cycle of testing, coding, and refactoring. Done well, TDD eliminates an entire class of programming errors. TDD isn’t perfect, of course. TDD is difficult to add to legacy codebases. Why TDD Works.

Test-Driven Development 80

Test-Driven Development Software Review Systems Review Technical Review 80

James Shore

MARCH 17, 2022

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. Because external systems can change or fail at any time, the real answer is “monitoring.” (See Simulate Nonlocal Dependencies.

Software Review 114

Software Review Testing Systems Review Technical Review 114

Gorilla Logic

MARCH 17, 2023

It enhances your existing Agile approach , synthesizing Test-Driven Development (TDD) and Acceptance Test-Driven Development (ATDD). You start by defining the desired behavior of the software in terms of concrete examples or scenarios that describe the behavior of the system in a clear, concise way. Net), or Behave (Python).

Weak Development Team 95

Weak Development Team Technical Review Software Review Systems Review 95

Agile Engine

JUNE 19, 2024

While this holds true for complete system rewrites, most modernization projects are much more incremental in nature, and their success often depends on how well companies can manage technical debt. Eventually, these optimizations allowed us to clear away more than 60% of logs in a cloud system processing 140 million events.

Technical Review 52

Technical Review UI/UX Software Review Systems Review 52

Honeycomb

JULY 26, 2022

Is the system working? First, let’s talk about what makes a system “work.” If we don’t know that our system is running, then it’s not done. If we can’t find out how healthy our system is, we can’t give our stakeholders confidence that the system will continue functioning. What is instrumentation?

Software Review 52

Software Review Systems Review TDD Load Balancer 52

Honeycomb

SEPTEMBER 20, 2023

Many software engineers are encountering LLMs for the very first time, while many ML engineers are being exposed directly to production systems for the very first time. Neural nets are also inherently stochastic, because GPU calculations around floating point operations are inherently nondeterministic. Latency is often unpredictable.

Weak Development Team 136

Weak Development Team Software Review Development Artificial Inteligence 136

Net Objectives

MARCH 18, 2019

First, the interfaces TDD drives into the system are always client-focused. When a test precedes development, it essentially becomes the first “client” for the behavior being developed. This fact is helpful in several ways. They are not implementation-focused because at the moment they are created there is no implementation yet.

Systems Review 40

Systems Review Testing TDD System 40

James Shore

APRIL 26, 2023

Net Promoter Score: 60. Net Developers I recommend this workshop because it gives you a new perspective on how to deal with side effects in your unit tests. Testing Without Mocks will allow me to fully utilize TDD in my work and solve many of the pains my clients and I experience. It has certainly done it for me. Cristóbal G.,

Course 59

Course Software Review Testing Exercises 59

James Shore

APRIL 26, 2021

To share your thoughts, join the AoAD2 open review mailing list. Next, review the design and make improvements. Again, review the design, simplify, and clarify. As “A TDD Example” on p.XX Refactorings occur every few minutes, during the “Refactoring” step of the TDD cycle. Your feedback is appreciated!

Software Review 83

Software Review Technical Review Systems Review Weak Development Team 83

Mobilunity

DECEMBER 2, 2022

The business landscape of the twenty-first century is undergoing a fast, ongoing transformation due to the stunning rate of technological breakthroughs. Systemizing tons of technical documentation. In this article, you’ll find out the benefits of hiring freelance business analysts and how to find the best specialist for your project.

Analysis 52

Analysis Technical Review Systems Review Software Review 52

Apiumhub

OCTOBER 18, 2022

We are proud to have had a lineup of speakers from different nationalities, including: Mark Richards is an experienced, hands-on software architect involved in the architecture, design, and implementation of microservices architectures, service-oriented architectures, and distributed systems. He’s currently a software engineer at Google.

Software Review 52

Software Review Architecture Technical Review Software 52

James Shore

JUNE 2, 2021

To share your thoughts, join the AoAD2 open review mailing list. How about a real-time embedded system? It turns out to be a net gain, resulting in higher quality results for less cost and time. Confirm that the software does what it needs to do with frequent customer reviews and stakeholder demos.

Software Review 80

Software Review Systems Review Technical Review Test-Driven Development 80

Apiumhub

MAY 26, 2022

Alexander von Zitzewitz is a serial entrepreneur in the software business and one of the founders of hello2morrow, an ISV specializing in static analysis tools that can enforce architecture and quality rules during development and maintenance of software systems. She has been developing high-quality software systems with her teams since 1998.

Technical Review 52

Technical Review Software Review Technical Advisors Architecture 52

James Shore

FEBRUARY 16, 2023

Infrastructure is code that involves external systems or state.) JavaScript and Node.js) TDD Lunch & Learn Screencast. Although broad integration tests can be added as a safety net, their failure indicates a gap in the main test suite. Narrow tests check a specific function or behavior, not the system as a whole.

Testing 138

Testing Software Review Infrastructure Examples 138

James Shore

APRIL 27, 2018

When programmers use test-driven development (TDD), the code they test interacts with other parts of the system that aren't being tested. However, this approach requires additional integration tests to ensure the system works as a whole, and it can make structural refactorings difficult. No broad tests required.

Testing 88

Testing Software Review Infrastructure Systems Review 88

LaunchDarkly

MAY 28, 2020

Sometimes people get that confused because when people think about end to end flow, sometimes they think about not just all the systems, the back end, the front end, the servers, everything up and running, but they sometimes think about, oh, I want to do a user story from start to end. So some people call that end to end as well.

Artificial Inteligence 59

Artificial Inteligence Machine Learning Testing Software Review 59

James Shore

APRIL 27, 2018

When programmers use test-driven development (TDD), the code they test interacts with other parts of the system that aren't being tested. However, this approach requires additional integration tests to ensure the system works as a whole, and it can make structural refactorings difficult. No broad tests required.

Testing 40

Testing Software Review Infrastructure Systems Review 40