TestE Test ing Environment · • TestE will execute your code on SVN • you will get feedback on a website • you will receive further information on the newsgroup Public test

Design practical Compiler Construction

S C I E N C E ■ P A S S I O N ■ T E C H N O L O G Y

u www.tugraz.at

Univ.-Prof. Dr. Franz Wotawa, DI Roxane Koitz Martin Zimmermann, Christopher Liebmann, Stephan Frühwirt

Institute for Software Technology

TestE CC-Testing Environment


2

• Automated testing

• give you feedback • public test cases

• grading • private test cases

Why a testsystem?


3

• very basic test cases

• demonstrate which input should lead to which output

• feedback if we can compile your code

• you will get public test cases for all three tasks

• TestE will execute your code on SVN

• you will get feedback on a website

• you will receive further information on the newsgroup

Public test cases


4

• special offer from us

• TestE will be maintained

• we reserve the right to stop the system at any time

• TestE will likely be executed 4 times a day

• server problems may occur at any time • start early • write your own TCs

• passing all public TCs != passing private TCs

Public test cases


5

• different categories • test different aspects of your code • separately test each aspect

• after each deadline you will get information about your performance

Private test cases


6

• timeout after 2 seconds

• remove blank new lines

• remove spaces

• after that sort of 1:1 diff

TestE in general


7

• Task 1: add some grammar rules

• ordering of rules can cause different message-types

• ANTLR generates error messages according to grammar definition

• wrong ordering may lead to problems in task 2 and 3

Task 1


8

• 1:1 diff

• if no difference • PASS

• else • FAIL

Task 1 - lexer

Number of lexical errors: 0

Number of lexical errors: 1 #1: line 6:3 token recognition error at: '$'


9

Task 1 - parser


Number of syntax errors: 0


Number of syntax errors: 1 #1: line 5:9 missing ID at ';'

PASSPASS





reference reference

actual output actual output


10

Task 1 - parser





FAIL FAIL





reference reference

actual output actual output


11

Task 1 - parser



FAIL


Number of syntactical errors: 0

reference

actual output


12

Task 1 - parser




Number of syntax errors: 1 #1: line 5:9 mismatched input 'i' expecting ‚)'

INCONCLUSIVE

reference

actual output


13

• not counted as FAIL = you will receive points

• possibly not entirely correct

• may cause problems in further tasks

• feedback: how many TCs inconclusive

hint: fix this!

Task 1 - inconclusive principle


Important for all tasks

14

• NO additional output! • use the debug flag

• write as many test cases as possible! • for finding wrong behavior • for finding bugs

• think of different scenarios and combinations of datatypes, operators etc.


15

Questions?

Documents

TestE Test ing Environment · • TestE will execute your code on SVN • you will get feedback on a website • you will receive further information on the newsgroup Public test