More robust in-Ludus testing #21

Open
opened 2023-12-24 21:12:28 +00:00 by scott · 0 comments
Owner

We've got test expressions in #8. That's swell!

One issue is that there's no way to test when something should panic. Right now, tests pass only when there's no panic. How do we get a positive result when there's a panic, since there's now way to trap a panic in Ludus? (By design!) Maybe this is just a limitation of the language.

For consideration.

We've got `test` expressions in #8. That's swell! One issue is that there's no way to test when something _should_ panic. Right now, tests pass only when there's no panic. How do we get a positive result when there's a panic, since there's now way to trap a panic in Ludus? (By design!) Maybe this is just a limitation of the language. For consideration.
scott added the
errors
next
question
research
semantics
ux
labels 2023-12-24 21:12:52 +00:00
scott self-assigned this 2023-12-27 04:18:16 +00:00
scott added this to the 0.2.0 milestone 2024-05-19 19:52:59 +00:00
scott added this to the Testing! project 2024-07-21 17:46:47 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: twc/ludus#21
No description provided.