Question 1

How do I create a custom assertion in Luassert?

Accepted Answer

Use the `assert:register` method to define a function that checks state and arguments, and set up messages with the `say` library. The README shows an example with `has_property` for checking table keys.

Question 2

Can Luassert work without Busted?

Accepted Answer

Yes, it can be used standalone by requiring 'luassert', but features like snapshots are best leveraged within a testing framework. The README provides direct usage examples, but integration may require manual setup.

Question 3

How to match complex arguments in spy calls with Luassert?

Accepted Answer

Use the `match` module with built-in matchers like `is_string()` or custom ones, and composite matchers like `all_of`. The README demonstrates this for verifying calls with flexible conditions.

Question 4

Luassert vs Lua's built-in assert: what's better?

Accepted Answer

Luassert extends native `assert` with rich types, modifiers, and extensibility, making it superior for detailed unit testing. However, for simple truthiness checks, Lua's built-in `assert` is lighter and faster.

Question 5

How to control table depth in failure messages?

Accepted Answer

Set the `TableFormatLevel` parameter using `assert:set_parameter` to limit display depth. The README includes an example showing output for different levels to improve readability.

Question 6

Is Luassert good for testing with spies and stubs?

Accepted Answer

Yes, it has built-in support for spies and stubs, with assertions like `called_with` and matchers for argument verification. Snapshots help manage state, but this adds complexity for simple use cases.

luassert

What is luassert?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions