Last updated on 2024年7月16日

How do you choose the right level and scope of testing for each feature or functionality?

由人工智能和领英社区提供技术支持

Test Driven Development (TDD) is a software development approach that involves writing tests before writing code. The idea is to specify the expected behavior and functionality of the code, and then write the code that passes the tests. TDD can help improve the quality, reliability, and maintainability of the software, as well as the productivity and confidence of the developers. However, TDD also poses some performance challenges that need to be addressed. In this article, we will discuss how to choose the right level and scope of testing for each feature or functionality, and how to balance the benefits and costs of TDD.

本文章的要点总结

Adopt a mixed approach:

Combining Test-Driven Development (TDD) with Behavior-Driven Development (BDD) can enhance both the technical quality and user-relevance of your software. It encourages collaboration between engineers and product teams, ensuring a comprehensive testing strategy.
Clarify test types:

Distinguish between unit, integration, and end-to-end tests. Unit tests focus on business rules and logic; integration tests check how different parts of the system work together; end-to-end tests examine the overall system behavior. This clarity ensures targeted and efficient testing.

本摘要由 AI 和以下专家提供支持

??Micha?l Azerhad

??Formateur et Coach réputé TDD /…
Mukesh Shinkar

Engineering Leader @ Chase Travel

1 Unit, integration, and end-to-end tests

The first challenge is to decide what kind of tests to write for each feature or functionality. There are three main types of tests: unit, integration, and end-to-end. Unit tests verify the behavior of individual components or functions in isolation. Integration tests verify the interaction and communication between different components or functions. End-to-end tests verify the functionality and user experience of the whole system or application. Each type of test has its advantages and disadvantages. Unit tests are fast, easy to write, and good for finding bugs in the code logic. Integration tests are more realistic, complex, and good for finding bugs in the code interfaces. End-to-end tests are the most realistic, comprehensive, and good for finding bugs in the user requirements. However, unit tests are also limited, brittle, and may not reflect the actual behavior of the system. Integration tests are also slower, harder to write, and may depend on external factors. End-to-end tests are also the slowest, most difficult to write, and may be affected by many variables.

添加您的观点

??Micha?l Azerhad

??Formateur et Coach réputé TDD / CleanArchi / DDD / CQRS (En live visio ou présentiel !) | Je dev vos projets les plus complexes avec obligation de résultat ! | Admin du Slack WealCome - mentoring Craft 4000 devs
(已编辑)
举报内容
Above description is absolutely wrong. Unit test = business rules, focus on the intents, no infra. Can/Should traverse as many classes as they want. Often starts at the hexagon entry point - aka Application Service / Use Case but you will find them too within some secondary adapters zone that denotes some logic. Integration test = Test secondary adapters exclusively, without any business rule involved. End-to-End test = Test primary adapters including components up to the bottom of the chain (infra). Should not exerce all business rules, only those that influence the primary adapter behaviours and system configuration. Some secondary ports might be substitutes (stubs/fakes) to avoid implicit dependencies often not deterministic.

已翻译

赞
Nik Sumeiko

React, TDD, Clean Architecture made simple
举报内容
In the context of React app development, here's how we decide what type of test to pick: - When the feature contains a Critical User Journey, we write an acceptance E2E/M test. It guarantees software behavior that is critical for our business to run, works. - When a feature contains a trivial user journey or edge cases, we employ integration tests to assert an outcome of a customer's interaction occurring on a single page: cy.mount( ? ? <TestProvider> ? ? ? ? <CreatePaymentPage /> ? ? </TestProvider> ); - For all the business logic within our React app, we use unit tests. These drive us to design logic separately from the rest of the app. Most of the times, the feature is developed using a combination of all these test types.

已翻译

赞
Namankumar Kalola

Automation Testing Lead
举报内容
This is still a backbone of any app development. Despite of n number of strategies available in market for testing, we are still following this approach by starting with unit test, integration test and end to end testing. Yes, the way to narrate the cycle will be different based on stakeholder and application and budgets.

已翻译

赞
Mateusz Sochalski

Software Engineer @ BT Group | Platform Engineering
举报内容
When choosing the right level and scope of testing for each feature or functionality, it's important to consider the complexity of the feature, the potential impact of a failure, and the cost of testing. For simple features that don't really integrate with other functions, unit testing may be sufficient to ensure that the code is working correctly. For more complex features, integration testing may be necessary to ensure that the different units of code are working together correctly. And for critical features, end-to-end testing may be necessary to ensure that the entire system is working correctly to avoid outages for your project.

已翻译

赞
Tim Bezhashvyly

Computer Systems MD | Software Craftsman | Fellow Aspen UK
举报内容
Please note that End-to-End (E2E) tests are also named acceptance or functional tests. They all mean the same - automation on the user level where subject under test (SUT) is an entire system. This, however, is not limited to just UI testing. For we development for instance sending HTTP request with various parameters and evaluating the response is a classic example of E2E test.

已翻译

赞

2 The testing pyramid

The second challenge is to decide how many tests to write for each type of test. There is no definitive answer, but a common guideline is to follow the testing pyramid. The testing pyramid is a model that suggests that the number of tests should decrease as the level of testing increases. In other words, there should be more unit tests than integration tests, and more integration tests than end-to-end tests. The rationale is that lower-level tests are cheaper, faster, and easier to maintain, while higher-level tests are more expensive, slower, and harder to maintain. The testing pyramid also implies that lower-level tests should cover more details and edge cases, while higher-level tests should cover more scenarios and user stories. The testing pyramid is not a strict rule, but a general principle that can help balance the trade-offs between speed, coverage, and quality of testing.

添加您的观点

Nik Sumeiko

React, TDD, Clean Architecture made simple
举报内容
The testing pyramid we leverage to ship React apps with a zero-bugs policy: ? ? ? ? ? ? ? ? ? ? ? ? ? / ?\ ? ? ? ? ? ? ? ? ? ? ? /? M? \? ? ? ? ? ? ? ? ? ? ? ? ? — Manual & discovery testing ? ? ? ? ? ? ? ? ? ? ??----- ? ? ? ? ? ? ? ?/? ? ? ? ? E? ? ? ? ? \? ? ? ? ? ? ? ? ? ? ? — E2E/M tests ? ? ? ? ? ? ?---------? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ???????????????? ???????? ???????????????? ? ? ? ??/? ? ? ? ? ? ? ? ? ? I? ? ? ? ? ? ? ? ? ?\? ? ? ? ? ? ? — Integration tests ? ? ? -------------? ? ? ? ? ? ? ? ? ? ? ? ?????????????? ???????? ???????????????? /? ? ? ? ? ? ? ? ? ? ? ? U? ? ? ? ? ? ? ? ? ? ? ? ???\? ? ? ? — Unit tests ?-----------------? ? ? ? ? ? ? ?? ???????????????? ??????????

已翻译

赞

3 The test-driven cycle

The third challenge is to decide when and how to write and run the tests. The core of TDD is the test-driven cycle, which consists of three steps: red, green, and refactor. The red step is to write a failing test that defines the desired feature or functionality. The green step is to write the minimum amount of code that makes the test pass. The refactor step is to improve the code quality and design without changing the functionality. The test-driven cycle should be repeated frequently and iteratively, until the feature or functionality is complete and meets the requirements. The test-driven cycle can help ensure that the code is correct, clean, and consistent, as well as drive the design and development of the software.

添加您的观点

Md Maruf Rahman

ISTQB? Certified Tester | QA Automation Engineer | Cypress | WebdriverIO | Selenium |
举报内容
In the test-driven cycle, the right level and scope of testing for each feature or functionality are determined by a systematic approach. Initially, developers create unit tests to validate individual components, ensuring they meet specified requirements. Integration tests follow, verifying the interaction between these components. Finally, system tests assess the overall functionality of the feature. This iterative process enables continuous refinement of tests, aligning them closely with the desired behavior of the software. By adhering to this cycle, teams can effectively tailor the testing approach to the specific needs and complexities of each feature or functionality, ultimately enhancing product quality.

已翻译

赞
Tim Bezhashvyly

Computer Systems MD | Software Craftsman | Fellow Aspen UK
举报内容
In ideal world test driven approach is also applicable on system level. When new requirement comes QA engineers start building acceptance (a.k.a. E2E, functional) test before or in parallel with development team doing real implementation. Once done test can be passed to developers to validate their implementation.

已翻译

赞

4 The feedback loop

The fourth challenge is to decide how to use the feedback from the tests. The tests provide valuable information about the state and progress of the software, as well as the possible issues and improvements. The feedback loop is the process of using the feedback from the tests to guide the next steps of development. The feedback loop should be short, continuous, and actionable. The feedback loop can help detect and fix bugs early, avoid over-engineering and unnecessary features, and align the code with the user needs and expectations.

添加您的观点

5 The testing culture

The fifth challenge is to decide how to foster and maintain a testing culture in the team and organization. TDD is not only a technical practice, but also a cultural shift. TDD requires a mindset of quality, collaboration, and learning. The testing culture is the set of values, beliefs, and behaviors that support and encourage TDD. The testing culture can help create a shared vision and understanding of the software goals and requirements, as well as a sense of ownership and responsibility for the software quality and performance. The testing culture can also help promote communication, feedback, and trust among the team members and stakeholders.

添加您的观点

6 The testing challenges

The sixth challenge is to decide how to overcome the common obstacles and difficulties of TDD. TDD is not a silver bullet, and it has its own challenges and limitations. Some of the testing challenges are technical, such as choosing the right tools, frameworks, and libraries for testing, or dealing with legacy code, dependencies, and external systems. Some of the testing challenges are organizational, such as convincing the management, clients, and users of the value of testing, or allocating enough time, resources, and training for testing. Some of the testing challenges are personal, such as overcoming the fear of failure, or adapting to the change of habits and workflow. The testing challenges can be addressed by applying best practices, learning from experience, and seeking support and guidance from peers and experts.

添加您的观点

Mukesh Shinkar

Engineering Leader @ Chase Travel
举报内容
According to me, if we want to ensure the feature or functionality should be verified or tested thoroughly, we should take a mixed approach of development which includes TDD and BDD. Why should we take a mixed approach of development including TDD and BDD? Increased collaboration: As TDD deals with code which is owned by Engineers. And BDD is one where engineering and product can participate to cover all aspects of system or functionality behaviour. Increased Inclusiveness: This mix will foster the sense of shared ownership and the accountability across stakeholders like engineering and product. This mix will lead to a robust, well tested and user focused application.

已翻译

赞

Test Driven Development

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

查看全部

How do you choose the right level and scope of testing for each feature or functionality?

1

2

3

4

5

6

1 Unit, integration, and end-to-end tests

2 The testing pyramid

3 The test-driven cycle

4 The feedback loop

5 The testing culture

6 The testing challenges

Test Driven Development

给文章评分

感谢您的反馈

更多Test Driven Development相关文章

更多相关阅读内容