Page MenuHomeSoftware Heritage

indexer: Improve tests
Closed, MigratedEdits Locked

Description

Some are using only in-memory implementations.
Which are quite fine to go fast.
They don't necessarily catch real production issues.

Some other tests are using mock tests (journal ones).
From experience, the mocks are brittle when it comes to catching eventual
breaking evolution changes over time.

In general, reworking those tests to use actual data services would be preferrable

Related to T2814#53460

Event Timeline

ardumont triaged this task as Normal priority.Nov 27 2020, 1:19 PM
ardumont created this task.
ardumont renamed this task from indexer.journal.client: Improve tests to indexer: Improve tests.Dec 1 2020, 3:44 PM
ardumont updated the task description. (Show Details)