We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Building a clean, maintainable and tested code base

Formal Metadata

Title
Building a clean, maintainable and tested code base
Title of Series
Number of Parts
115
Author
Contributors
License
CC Attribution - NonCommercial - ShareAlike 4.0 International:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
An introduction to how to write clean code (type hinting, docstrings, inline comments et cetera) and supporting the clean code with maintainable project structure and unit tests. Goals - with comparisons/examples: What's clean, maintainable code? (type hinting, docstrings, inline comments et cetera) What's a clean, navigatable project structure? Should the tests package be nested into each package? Should my 'tests' package structure mirror the project structure? (for easy navigation of which module/package is being tested) (Testing) What should I test and what shouldn't I test? (Testing) When should I mock and when shouldn't I? (Testing) Writing clean test cases (Testing) Using pytest to utilize parametrize to test multiple combinations, whilst keeping a clean codebase