|
278
by dilshan_a
Added README files to explain the test framework and the examples. |
1 |
These files are several examples that may be run by the test framework. |
2 |
||
3 |
------------------
|
|
4 |
all_input_text.xml |
|
5 |
all_input.py |
|
6 |
------------------
|
|
7 |
An xml spec for a problem which requires reading various input sources and a possible attempt at the problem. |
|
8 |
||
9 |
------------------
|
|
10 |
fib_text.xml |
|
11 |
fib.py |
|
12 |
------------------
|
|
13 |
An xml spec for a problem which requires writing a function to calculate fibonnaci numbers, and a slightly incorrect implementation. |
|
14 |
||
15 |
--------
|
|
16 |
tests.py |
|
17 |
--------
|
|
18 |
A python script which runs the all_input and fib examples through the test framework. |
|
19 |
||
20 |
---------
|
|
21 |
hack_1.py |
|
22 |
---------
|
|
|
511
by stevenbird
README-examples: |
23 |
An example script that can be used to pass any test case which tests the output of a script (not functions). |
|
278
by dilshan_a
Added README files to explain the test framework and the examples. |
24 |
|
25 |
-----------------
|
|
26 |
filespace_test.py |
|
27 |
file_test.py |
|
28 |
-----------------
|
|
29 |
filespace_test contains a script which to test the TestFilespace class. It does this by executing file_test, which performs various file operations inside the class. |
|
30 |
||
31 |
Currently, the output is verified by inspection. I found the idle implementation of various modes is not comppletely robust, making proper verification harder. Probably the best is to actually write a C program and use fopen. |
|
|
283
by dilshan_a
Fixed a bug where variables were persistent across test cases. |
32 |
|
33 |
------------
|
|
34 |
tute_doc.tex |
|
35 |
------------
|
|
36 |
Some notes on requirements of the tutorial system and test framework and how it should operate. Last revised 9th Jan. |
|
|
511
by stevenbird
README-examples: |
37 |
|
38 |
||
39 |
New functionality not covered in these examples: |
|
40 |
||
41 |
* problem element has a rows attribute for specifying the number of rows in the |
|
42 |
text area |
|
43 |
* function element has pass and fail attributes containing strings to report |
|
44 |
test outcome to user |
|
45 |
* new code element permits tests on the code string, not just the program output |