Lecture

GoogleTest, Pytest, Git Submodule/Subtree, Python os.path

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

MATH-611: Scientific programming for Engineers

The students will acquire a solid knowledge on the processes necessary to design, write and use scientific software. Software design techniques will be used to program a multi-usage particles code, aiming at providing the link between algorithmic/complexit ...

Description

This lecture covers topics such as Google Test for C++ testing, Pytest for Python testing, Git submodule and subtree usage, and Python's os.path and subprocess modules. It includes installation guidelines, testing functions, equality tests, fixtures, and the differences between submodules and subtrees. Additionally, it explains how to manipulate files, list directories, construct filenames, and execute external programs using Python.

Instructor

Guillaume Anciaux

ResearchResearch Topics My research can be decomposed in three main blocks:First, the main goal of my current research is the physical description of contact interactions. I performed numerous studies of this topic using different models from the continuum scale down to atomistic scale. Since atomic phenomena and macroscopic observations are linked, the physics of contact needs the simultaneous consideration of several scales. For instance, plasticity is a theory defined for the macroscopic scale whereas t

Official source

Related concepts (32)

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.

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.

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.

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 (63)

Software Testing: Avoiding and Fixing Bugs

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

Genetic Inheritance and X Chromosome Inactivation

Discusses genetic inheritance, color blindness prevalence, DNA cleavage, X chromosome inactivation testing, and XIC mutations.

Software Quality: Managing Defects and Testing Strategies

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

Launching Online Courses: Preparation and Motivation

Covers the essential steps to prepare and launch an online course successfully.

Property-Based Testing: Advanced Techniques