Lecture

Automated Testing: Strategies and Best Practices

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.

In course

CS-305: Software engineering

This course teaches the basics of modern software development: designing software, working in a team, writing good code, shipping software, and evolving software. It emphasizes building software that meets high standards of quality, reliability, security, ...

Description

This lecture covers the importance of automated testing, emphasizing strategies to ensure accurate results. The instructor explains the significance of testing multiple scenarios, including stress testing and end-to-end testing. The concept of code coverage is explored, focusing on statement, branch, and path coverage. The lecture also delves into the practice of Test-Driven Development (TDD) and regression testing, highlighting the benefits of writing tests before and after code implementation. Various testing techniques, such as mocking frameworks and acceptance testing, are discussed to ensure robust and reliable software development.

Instructor

George Candea

George Candea heads the Dependable Systems Lab, where he develops techniques and abstractions for building efficient and trustworthy computer systems. His current work focuses on making performance and energy programmable, i.e., providing first-class abstractions to capture a system’s performance and energy behavior (as interfaces do for functionality) and to use them dependably to design, code, and operate efficient systems.In the recent past, George also served as CEO and later Chief Scientist of Cyberhav

Official source

Ontological neighbourhood

Computer engineering

Software development: Software development process

Related concepts (25)

Regression testing

Regression testing (rarely, non-regression testing) is re-running functional and non-functional tests to ensure that previously developed and tested software still performs as expected after a change. If not, that would be called a regression. Changes that may require regression testing include bug fixes, software enhancements, changes, and even substitution of electronic components (hardware). As regression test suites tend to grow with each found defect, test automation is frequently involved.

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.

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.

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.

Acceptance testing

In engineering and its various subdisciplines, acceptance testing is a test conducted to determine if the requirements of a specification or contract are met. It may involve chemical tests, physical tests, or performance tests. In systems engineering, it may involve black-box testing performed on a system (for example: a piece of software, lots of manufactured mechanical parts, or batches of chemical products) prior to its delivery.

Related lectures (64)

Testing and Debugging

Explores the history of computing, automated testing, TDD, test coverage, bug reports, and debugging.

Unit Testing in Java: Arrays

Discusses unit testing for Java arrays and methods to find min, average, and sort.

Software Testing: Avoiding and Fixing Bugs

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

Bobby's Interactive Story

Explores coding interactions with Bobby to create a personalized experience.

Software Quality: Managing Defects and Testing Strategies