We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Created 2009-11-20 by [email protected] assigned to [email protected]
I'm not sure if this wasn't mentioned already, but currently the test do not offer any advantage.
Running the example from the documentation (http://www.meta-environment.org/doc/books//analysis/rascal-manual/rascal-manual.html#section.test): rascal>test 1 == 2; ok rascal>:test bool: false rascal>
while according to the documentation the :test should fail and print where it failed (actually making it a bit like xUnit style testing).
expected result: failed : test 1==2
Next to this bug report, I wonder of any more advanced control mechanisms are planned? A nice feature would be like this:
public Resource allFacts = extractProject('projec://big/); :test-initialize allFacts = extractProject('projec://small/);
And ensure that the initializations are run first. Perhaps use the backtracking to undo the changes made by the initialize run.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Created 2009-11-20 by [email protected] assigned to [email protected]
I'm not sure if this wasn't mentioned already, but currently the test do not offer any advantage.
Running the example from the documentation (http://www.meta-environment.org/doc/books//analysis/rascal-manual/rascal-manual.html#section.test):
rascal>test 1 == 2;
ok
rascal>:test
bool: false
rascal>
while according to the documentation the :test should fail and print where it failed (actually making it a bit like xUnit style testing).
expected result:
failed : test 1==2
Next to this bug report, I wonder of any more advanced control mechanisms are planned? A nice feature would be like this:
public Resource allFacts = extractProject('projec://big/);
:test-initialize allFacts = extractProject('projec://small/);
And ensure that the initializations are run first. Perhaps use the backtracking to undo the changes made by the initialize run.
The text was updated successfully, but these errors were encountered: