Tester Stories: How I Encountered and Fixed Flaky Testsby@aveuiller

Tester Stories: How I Encountered and Fixed Flaky Tests

tldt arrow
Read on Terminal Reader
Read this story w/o Javascript

Too Long; Didn't Read

It can happen that the result of a unit test changes over multiple executions of a test suite without any change in the code. Such a test is named a flaky test. It is not dangerous per se but reduces the confidence a developer can give to his test suite, diminishing the benefits of the latter. In a project where continuous integration was broken during the 5 first days of each month, it led to the tests being faulty at the beginning of the month. One way of fixing such issues would be to sandbox the execution of the tests to control the current date.

Company Mentioned

Mention Thumbnail
featured image - Tester Stories:  How I Encountered and Fixed Flaky Tests
Antoine Veuiller HackerNoon profile picture

@aveuiller

Antoine Veuiller


Receive Stories from @aveuiller

react to story with heart

RELATED STORIES

L O A D I N G
. . . comments & more!
Hackernoon hq - po box 2206, edwards, colorado 81632, usa