Net Objectives

APRIL 3, 2019

When first adopting TDD, developers can run into some roadblocks that seem to indicate that TDD is a difficult process. In truth, some of these problems actually indicate faults in the system architecture.

Systems Review 40

Systems Review System Architecture TDD Architecture 40

Xebia

JANUARY 27, 2024

This toolset (working title: Truffleswine) allows us to retrieve relevant data from systems quickly, which in turn helps us ask the right questions sooner and clarify business cases for improvement using actual data. Commitment Once we are confident, we consider how we can integrate the feature into the system.

Software Review 130

Software Review Systems Review Tools Development 130

Apiumhub

SEPTEMBER 19, 2018

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.

Software Review 67

Software Review Systems Review TDD Testing 67

Net Objectives

APRIL 4, 2019

This feels like redundancy and makes them wonder if TDD is promoting bad practices. Example: A system that converts Fahrenheit to Celsius. The code would contain something like this: return (F - 32) * 5/9; The test might contain … Continue reading "TDD Replicating Algorithms".

Software Review 40

Software Review Systems Review TDD Testing 40

Net Objectives

FEBRUARY 28, 2019

The type and nature of the tests that you write in TDD helps you to understand how strongly your system is encapsulated. Everything the system must do, and yet might not, needs a test. The more your tests are about … Continue reading "TDD and Encapsulation".

Systems Review 40

Systems Review TDD Testing System 40

Net Objectives

APRIL 5, 2019

TDD, when conducted as a specifying activity, is an aspect of Behavior-Driven Development (BDD). Behavior is what we specify and is what we “drive” into the system using tests. Therefore, when structuring the tests in TDD we can be guided by the language of BDD: Given, When, Then.

Systems Review 40

Systems Review TDD Testing System 40

Net Objectives

MAY 1, 2019

TDD is typically part of an agile process. This means that we embrace change, that new requirements flow into the team’s work either on a time-boxed pulse, or through some kind of pull system (like Kanban). In TDD, a new requirement always starts out as a new, failing test or “specification.”

Systems Review 40

Systems Review TDD Sustainability Agile 40

Net Objectives

APRIL 23, 2019

TDD often uses unit tests to drive behavior into the system. When these are automated, this can give us clues as to how to make our work in TDD more reusable. Tools like Fit, Specflow, and Cucumber are all designed to parse some non-technical artifact (such … Continue reading "TDD and Test Invariance".

Technical Review 40

Technical Review Systems Review TDD Testing 40

Net Objectives

MARCH 12, 2019

As consultants, we are often asked to review the work of others. One of the things we review is the quality of the design of some part of the system. Often the developers understand and agree that these qualities are important, but they are not … Continue reading "“Good” Tests in TDD".

Systems Review 40

Systems Review TDD Testing System 40

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

Henrik Warne

JUNE 19, 2022

I have used randomly generated tests to very good effect before, but always on complete systems (like generating random calls between phones), never as property based tests. This chapter uses the example of converting Roman numerals to integers to show how TDD works. Not all situations benefit from TDD. Test doubles and mocks.

Software Review 223

Software Review Testing Systems Review Technical Review 223

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

Xebia

APRIL 5, 2022

Test automation is not a project or a one-off—it is part of the development lifecycle and should be seen as its own system that needs to evolve over time as the requirements and system under test change and mature. Delivery pipelines and source code management systems help—for example, you can gate pull requests on a failing test.

Testing 130

Testing Software Review Systems Review Technical Review 130

Honeycomb

JUNE 21, 2023

The biggest is Test-Driven Development (TDD) , thanks to Kent Beck and his Xtreme Programming crew. TDD says you write tests before writing any code, because this pushes you to design the code in ways that are testable, with APIs that are usable. TDD is a great design practice. But which should drive our development?

Software Review 93

Software Review Systems Review TDD Development 93

Xoriant

JUNE 9, 2015

TDD is an Agile Development technique in which developers write test cases before writing the corresponding code for the user story assigned to him. TDD focuses on writing the necessary code to pass the test thus making the process simple and clear. What is the primary goal of Test Driven Development (TDD)? Role of QA in TDD.

Test-Driven Development 40

Test-Driven Development Software Review Systems Review TDD 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

Honeycomb

JUNE 23, 2020

The most successful software development movement of my lifetime is probably test-driven development or TDD. With TDD, requirements are turned into very specific test cases, then the code is improved so the tests pass. But it’s time to take a step beyond TDD in order to write better software that actually runs well in production.

Test-Driven Development 98

Test-Driven Development Software Review Systems Review Technical Review 98

Marcusoft

MARCH 11, 2024

For example; An audit log statement for every action in the system - is too big and will not deliver any value in a long time. An audit log statement for logging into the system - this has value, is small, and holds many of the benefits of using smaller batches. But when it does it sure is valuable.

Software Review 52

Software Review Systems Review TDD Weak Development Team 52

Honeycomb

AUGUST 12, 2022

After all, observability is about understanding systems, which means more than just production. TDD goes platinum. We’ve been living in a “shift-left” or “shift testing left” world for a while with test-driven development (TDD). TDD is considered the gold standard of shift-left testing for a reason. But nothing’s perfect.

Software Review 52

Software Review Systems Review Technical Review TDD 52

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

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

James Shore

FEBRUARY 1, 2019

Non-functional attributes emerge from the system as a whole, so even a codebase with 100% coverage can have problems. Here's the thing about TDD. The definition of TDD is that you don't write code without a failing test, and you do so in a tight loop that covers one branch at a time.

Software Review 110

Software Review Systems Review Testing TDD 110

O'Reilly Media - Ideas

MAY 11, 2020

System Programming Book — CS241 “Intro to Systems Programming” textbook that was created in a wiki by University of Illinois students over 5 years. Subjectively, the teams experienced a 15–35% increase in initial development time after adopting TDD.

Systems Review 54

Systems Review TDD Test-Driven Development Case Study 54

Apiumhub

MARCH 30, 2023

Containerization If you want to seamlessly automate developer support responsibilities like testing and system configuration, containerization is the best solution for you. TDD Test-driven development (TDD) is a software development process that relies on the repetition of a very short development cycle.

Software Review 70

Software Review Software Development Software Technical Review 70

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

Xebia

MARCH 10, 2022

This is basically assuming the system is correct until proven otherwise. Deciding what strategy to use depends on your risk appetite for a specific system or functionality and on how much certainty you already have. When the risk profile of a system , or the certainty on it changes, the best quality strategy might also change.

Software Review 130

Software Review Quality Assurance Systems Review Technical Review 130

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. Instead, ML teams typically build evaluation systems to evaluate the effectiveness of the model or prompt. Users will do things you can’t possibly predict.

Weak Development Team 137

Weak Development Team Software Review Development Artificial Inteligence 137