You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unit tests should systematically cover various aspects of MeTTa-Scheme interactions and run automatically for branch protection on github. Not working cases could possibly exist as skipped unit tests. More complex examples can remain as integration tests.
The text was updated successfully, but these errors were encountered:
I agree. It can be initially based on example1...6.metta in ./extend: Running automatically same file, once compiling the "to-compile-code" with compiler, one time also running the "to-compile-code" with the MeTTa interpreter, then checking whether the output matches. (same principle as in ./tests but this time MeTTa interpreter is involved in both cases, in one case calling the compiled code, in other case interpreting it). I can add a script which does this soon.
Unit tests should systematically cover various aspects of MeTTa-Scheme interactions and run automatically for branch protection on github. Not working cases could possibly exist as skipped unit tests. More complex examples can remain as integration tests.
The text was updated successfully, but these errors were encountered: