Lecture

Testing Strategies: Code Coverage and Quality

Graph Chat

Chat with Graph Search

Ask any question about EPFL courses, lectures, exercises, research, news, etc. or try the example questions below.

DISCLAIMER: The Graph Chatbot is not programmed to provide explicit or categorical answers to your questions. Rather, it transforms your questions into API requests that are distributed across the various IT services officially administered by EPFL. Its purpose is solely to collect and recommend relevant references to content that you can explore to help you answer your questions.

Description

This lecture discusses various testing strategies, focusing on the importance of code coverage and quality in software development. The instructor begins by explaining the role of counters in tracking code execution during tests. A recap of testing methodologies is provided, including unit testing, integration testing, and system testing, illustrated with examples of code coverage graphs. The instructor emphasizes the significance of understanding control flow graphs to identify which parts of the code are executed during tests. The lecture highlights the need for high-quality tests that are small and focused, verifying one aspect at a time to facilitate easier debugging. The instructor also discusses the importance of independent unit tests to avoid dependencies that could affect test outcomes. Throughout the lecture, the instructor uses visual aids to illustrate concepts, providing a comprehensive overview of how to assess and improve code quality through effective testing practices.

This video is available exclusively on Mediaspace for a restricted audience. Please log in to MediaSpace to access it if you have the necessary permissions.

Watch on Mediaspace

Official source

Ontological neighbourhood

Computer engineering

Software development: Software development process

Related concepts (32)

Unit testing

In computer programming, unit testing is a software testing method by which individual units of source code—sets of one or more computer program modules together with associated control data, usage procedures, and operating procedures—are tested to determine whether they are fit for use. It is a standard step in development and implementation approaches such as Agile. Before unit testing, capture and replay testing tools were the norm. In 1997, Kent Beck and Erich Gamma developed and released JUnit, a unit test framework that became popular with Java developers.

Integration testing

Integration testing (sometimes called integration and testing, abbreviated I&T) is the phase in software testing in which the whole software module is tested or if it consists of multiple software modules they are combined and then tested as a group. Integration testing is conducted to evaluate the compliance of a system or component with specified functional requirements. It occurs after unit testing and before system testing.

Test automation

In software testing, test automation is the use of software separate from the software being tested to control the execution of tests and the comparison of actual outcomes with predicted outcomes. Test automation can automate some repetitive but necessary tasks in a formalized testing process already in place, or perform additional testing that would be difficult to do manually. Test automation is critical for continuous delivery and continuous testing.

Software testing

Software testing is the act of examining the artifacts and the behavior of the software under test by validation and verification. Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include, but are not necessarily limited to: analyzing the product requirements for completeness and correctness in various contexts like industry perspective, business perspective, feasibility and viability of implementation, usability, performance, security, infrastructure considerations, etc.

System testing

System testing is testing conducted on a complete integrated system to evaluate the system's compliance with its specified requirements. System testing takes, as its input, all of the integrated components that have passed integration testing. The purpose of integration testing is to detect any inconsistencies between the units that are integrated together (called assemblages). System testing seeks to detect defects both within the "inter-assemblages" and also within the system as a whole.

Related lectures (64)

Software Quality: Managing Defects and Testing Strategies

Explores managing defects, testing strategies, and challenges in software quality, with real-world examples and case studies.

Automated Testing: Strategies and Best Practices

Explores automated testing strategies, including code coverage and various testing techniques, to ensure reliable software development.

Software Testing: Avoiding and Fixing Bugs

Emphasizes the critical role of software testing in preventing and resolving bugs during development.

Memory Operations: Data Alignment and Endianness

Covers memory operations, endianness, low power mode, debugging, and interface with circuits.

Software Engineering: Best Practices