Skip to content
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

Add tests with all possible exit codes #174

Closed
1 of 8 tasks
anton-trunov opened this issue Mar 12, 2024 · 1 comment · Fixed by #823
Closed
1 of 8 tasks

Add tests with all possible exit codes #174

anton-trunov opened this issue Mar 12, 2024 · 1 comment · Fixed by #823
Assignees
Labels
Milestone

Comments

@anton-trunov
Copy link
Member

anton-trunov commented Mar 12, 2024

https://github.com/ton-community/tact-fireworks does an amazing job at this.

One solution would be to add tact-fireworks to CI to make sure we stay in sync.

Here is a list of what we should test:

  • integer overflow (addition, subtracts, negation, multiplication, division)
  • division by zero (division, modulo)
  • cell overflow (data)
  • cell overflow (refs)
  • cell underflow (data)
  • cell underflow (refs)
  • repeat-loop's out-of-bounds counter: Test repeat's counter valid range #654
  • ...

TODO: add more things from https://docs.tact-lang.org/book/exit-codes and various parts of tact-docs

@anton-trunov
Copy link
Member Author

Looks like this is going to be easier when #212 is merged -- exit codes can then be easily returned from getters and checked in tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants