-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable Assertions in Enso Tests #5585
Comments
#5087 is probably a blocker for this issue. |
Bumping the priority - after merging of #7147, an elementary expression like |
Pavel Marek reports a new STANDUP for today (2023-11-29): Progress: - Continuing to work on JVM assertions after long time.
|
Pavel Marek reports a new STANDUP for today (2023-11-30): Progress: - VisualVM polyglot sampling does not work?
|
Pavel Marek reports a new STANDUP for today (2023-12-01): Progress: - Still bumping into multi thread access not allowed for
|
Pavel Marek reports a new STANDUP for today (2023-12-04): Progress: - Giving up on this PR for now, published the investigation results as a comment It should be finished by 2023-12-06. |
This is done by following line. |
How important is this feature to you?
3 – Lack of it makes using Enso slightly harder
Describe the idea you'd like to see implemented.
Recently we finally got assertions enabled in the engine tests. This is great, because now we will be less likely to break Truffle invariants and we can also have our own assertions.
However, engine tests are not everything, a lot of interesting interactions also happen in our 'integration tests' written directly in Enso - in the
test/
directory.Currently, running
test/Tests
yields:So we are still breaking Truffle assertions.
Moreover, ideally we should be able to use and verify
assert
s withinstd-bits
. Currently, even if we add these, they cannot really be checked because if we run with-ea
the run will fail due to the broken Truffle assertions.Ideally we should also have
-ea
enabled for the Enso tests on the CI. Currently, that is only the case for the engine tests.Problem this is solving
assert
s instd-bits
code (because the runs will fail due to (1)). Having the ability to add asserts is helpful as it allows us to verify invariants in our code and write it more correctly. We were also thinking of including anassert
construct into Enso directly. Such assertions not only allow us to more confidently verify correctness of our code but also serve as documentation purposes explaining what a given function expects.Tasks
The text was updated successfully, but these errors were encountered: