Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in
Toggle navigation
Menu
Open sidebar
uwdkn
mjtest
Commits
3cae0be0
Commit
3cae0be0
authored
Jan 10, 2017
by
Johannes Bechberger
Browse files
Update README, fix #66
parent
c15d72d9
Changes
1
Hide whitespace changes
Inline
Side-by-side
README.mdwn
View file @
3cae0be0
...
...
@@ -16,13 +16,14 @@ such code as it probably helps the other teams (and could later be integrated in
Test modes
----------
The test cases are divided in
5
'modes':
The test cases are divided in
6
'modes':
- __lexer__: Test cases that check the lexed token (and their correct output)
- __syntax__: Test cases that just check whether `./run --parsecheck` accepts as correct or rejects
them.
- __ast__: Test cases that check the generated ast by using the pretty printing functionality.
- __semantic__: Test cases that check semantic checking of MiniJava programs
- __compile-firm__: Test cases that check the correct compilation and execution of MiniJava programs with the libfirm backend.
- __compile__: Test cases that check the correct compilation and execution of MiniJava programs with the self implemented backend.
The test different test cases for each mode are located in a folder with the same name.
Except the compile-firm test cases which are located in the `exec` folder.
...
...
@@ -101,8 +102,8 @@ Test types for the semantic mode
__All semantic mode tests have to be syntactically correct___
Test types for the compile-firm mode
------------------------------------
Test types for the compile-firm
and compile
mode
------------------------------------
------------
<table>
<tr><th>File ending(s) of test cases</th><th>Expected behaviour to complete a test of this type</th></tr>
...
...
@@ -114,7 +115,7 @@ Test types for the compile-firm mode
</tr>
</table>
__All compile-firm mode tests have to be semantically correct___
__All compile-firm
and compile
mode tests have to be semantically correct___
__All bigger test cases (e.g. for benchmarking) should be placed into the `big` folder__
...
...
@@ -147,7 +148,7 @@ usage: mjt.py [-h] [--only_incorrect_tests] [--all_exec_tests]
[--produce_no_reports] [--produce_all_reports] [--parallel]
[--output_no_incorrect_reports] [--color] [--ci_testing]
[--log_level LOG_LEVEL]
{all,lexer,syntax,ast,semantic,compile-firm,
exec
} MJ_RUN
{all,lexer,syntax,ast,semantic,compile-firm,
compile
} MJ_RUN
MiniJava test runner
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment