Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Mocked time

Open
  • Is something wrong?
#60 25 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
scala
Domain
testing

Research direction

No files or tests are named. Start by reviewing the current Loom design and the linked cats-effect test-runtime documentation, then determine how delayed and current time are represented. Done means the issue's proposed delay and now functions can be tested with an emulated clock without waiting in real time.

Written by the indexing model from the issue text.

Description

Add delay and now functions. Add test runtime with emulated clock to test code with delays without spending actual time on delays.

Would be invaluable for testing asynchronous code, not sure is this even possible with current Loom design but might be worth a try.

There is similar feature in cats-effect, separate effect evaluator with emulated time: https://typelevel.org/cats-effect/docs/core/test-runtime#mocking-time

Dominant language
Scala
Stars
524
Forks
36
Avg merge
9h 58m
Merged PRs (30d)
20

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from softwaremill/ox

All issues in softwaremill/ox

Similar issues

More Scala issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.