~azzar1/unity/add-show-desktop-key

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
These files are several examples that may be run by the test framework.

------------------
all_input_text.xml
all_input.py
------------------
An xml spec for a problem which requires reading various input sources and a possible attempt at the problem.

------------------
fib_text.xml
fib.py
------------------
An xml spec for a problem which requires writing a function to calculate fibonnaci numbers, and a slightly incorrect implementation.

--------
tests.py
--------
A python script which runs the all_input and fib examples through the test framework.

---------
hack_1.py
---------
An example script that can be used to pass any test case which tests the output of a script (not functions).

-----------------
filespace_test.py
file_test.py
-----------------
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.

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.

------------
tute_doc.tex
------------
Some notes on requirements of the tutorial system and test framework and how it should operate. Last revised 9th Jan.


New functionality not covered in these examples:

* problem element has a rows attribute for specifying the number of rows in the
  text area
* function element has pass and fail attributes containing strings to report
  test outcome to user
* new code element permits tests on the code string, not just the program output