Skip to content

Custom assertion methods could benefit from returning Result #845

@FabijanC

Description

@FabijanC

Currently some of them just panic, e.g. tests/integration/common/utils::assert_contains. The original cause may be hard to identify because of this. Using .unwrap() or .expect(...) on a Result that could be returned by such functions would directly point from the stack trace to the responsible line.

This task also requires identifying all such helper functions, not just the one used as example.

Metadata

Metadata

Assignees

Labels

testingRelated to code testing

Type

Projects

Status

🆕 New

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions