Run tests from annotated ballerina files about nballerina HOT 5 CLOSED

I was thinking of

import ballerina/io;

public function main() {
  io:println(add(1, 2)); // @output 3
}

function add(int x, int y) returns int {
   return x + y;
}

from nballerina.

// @invoke 1, 2
// @expect 3
function test(int x, int y) returns int {
    int diff = x - y;
    return diff;
}

how about a format like above.

from nballerina.

I have used a convention where the name of a valid test case (a program that should compile and run without panicking) starts with the letter V; these have @output comments specifying the expected output.

I envisage having other letters for other categories of test case, including

• P: this compiles but panics when executed: this would have a @panic comment on the line which should panic
• E: this should get a compilation error: this would have an @error on the line on which an error should be reported; this should only be for cases that are errors according to the full Ballerina spec (XXX need a way to distinguish whether parse error or semantic error is expected)
• U: this should be like a V test, but is for something that is not in the subset: this should result in an error of type parse or unsupported not not semantic; when a feature is implemented U tests can be renamed to V tests
• F: this is for current failing test cases; it should be followed by one of the other letters

from nballerina.

We should use a DataProvider with testerina to run all the test cases: this should leave .ll files for all the V cases. These .ll cases can separately be tested using the testll.sh script.

from nballerina.

Still need to do #81 and #89, but this is enough for subset01

from nballerina.