Conversation
Structured docs around expected language subset, add references, minijava syntax.
Add simple test cases for boolean operators.
Add the test cases for the comparison operators supported in Javita.
Add the test cases for the control flow (sequences, conditionals, loops, static method calls).
Add a list of features included and excluded in the Javita language.
|
The pull request add a list of features supported by the language (I did not define a syntax or a formal semantic) and a set of test cases for the supported features. I would like to get feedback on how to improve the tests (e.g. is the structure of the test ok? Are there corner cases in the semantic that we want to test?) and then merge the current changes . |
Fix the code style warning for the use of duplicate string literals and duplicate imports whthout using string brackets.
smover
changed the title
|
@ftc This is the pull request we were talking about. Could you check if the structure of the test cases is adequate? The idea is that these should be test cases in the java subset that the concrete interpreter should be able to run. |
| @@ -0,0 +1,7 @@ | |||
| package edu.colorado.plv.cuanto.javita; | |||
|
|
|||
| /** | |||
| (e()) should equal (n) | ||
| }} | ||
| } | ||
| } |
There was a problem hiding this comment.
Flip the forAll and test so that you get not one big test but many small tests
| behavior of "Arithmetic operators" | ||
| val exprTests = Table( | ||
| (mcString, resString), | ||
| (Expressions.testExpr1 _,3), |
There was a problem hiding this comment.
Make this table be a mapping from "method keys" to values.
2 participants
No description provided.