Question 1

How do I set up unit-threaded with dub for my D project?

Accepted Answer

Use the dub configuration with `preBuildCommands` to generate the test runner file, as shown in the README's JSON and SDL examples, or manually list modules in a mixin for more control.

Question 2

What's the difference between unit-threaded and dunit for D testing?

Accepted Answer

unit-threaded extends D's built-in unittest blocks with features like parallel execution and fluent assertions, while dunit follows an xUnit style. unit-threaded integrates more seamlessly with D's native testing but requires more setup.

Question 3

Can I run unit-threaded tests without multi-threading?

Accepted Answer

Yes, use the `-s` command-line switch to run tests in single-threaded mode. This is useful for debugging or when dealing with thread-unsafe code that isn't marked with `@Serial`.

Question 4

How do I mock an interface in unit-threaded?

Accepted Answer

Create a mock with `mock!Interface`, set expectations using `expect` or `expectCalled`, and verify calls with `verify`. The README shows examples with return value control for sequential calls.

Question 5

Is property-based testing in unit-threaded stable for production use?

Accepted Answer

It's labeled as preliminary support, so while functional for basic cases, it might lack advanced features or robustness compared to mature property-based testing libraries in other languages.

Question 6

How to handle flaky tests with unit-threaded?

Accepted Answer

Use the `@Flaky` UDA to rerun the test up to a default of 10 times, customizable by passing a number. However, the README recommends fixing the test as a better long-term solution.

unit-threaded

What is unit-threaded?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions