Skip to content

Test framework documentation should document every single optional argument #1406

Open
@Voileexperiments

Description

@Voileexperiments

It wasn't until I looked at cw-2.js again that there's actually an option optional argument after msg in the first place, and even with that I have to look all over the code to slightly figure out what it does: it's completely undocumented. (Or the asyncTimeout argument in describe/it, that's also completely undocumented). Similarly, allow_raise is undocumented for Python, and SQL's run_sql has tons of important and useful optional arguments.

The documentation should include every single one of these optional arguments, otherwise it's severely limiting the actual power of the test suite.

┆Issue is synchronized with this Clickup by Unito

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions