T stands for testing. Understand it first. Chapter 1 — Prologue

Photo by Brett Jordan on Unsplash

Why are we testing ?

Photo by bruce mars on Unsplash
  • protection of functionalities against incidental changes
  • more precise and quick discovering bugs
  • creating live documentation of API usage
  • gaining confidence about a quality of our code

Who is the receiver of our tests?

Photo by Scott Graham on Unsplash

How we divide tests in terms of refactorization ?

Photo by Alex Padurariu on Unsplash

software developer, reading & learning enthusiast

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Numerical Algorithms (Gradient Descent and Newton’s Method)

Make your own tools.

Package NUTSHEL in R 3.6.3

75% Off Collage Fleece Blanket Free Shipping w/ code BLANKETDEAL

Tail Recursion in Kotlin

Recursive gates

The objects world in Python

Running Django on Google Colab.

Validating Configurations in an ASP.NET Core 2.1 Application Using Data Annotations

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Jakub Pruszyński

Jakub Pruszyński

software developer, reading & learning enthusiast

More from Medium

ServiceNow Test Management 2.0

How to Sharpen Your Unit Tests

Refactoring 101: Code Smells — Bloaters

Basic OOP for shavetail Louies — PART III [Inheritance | Composition | Encapsulation]