diff options
Diffstat (limited to 'LuaSL/testLua/yueliang-0.4.1/test_lua/README')
-rw-r--r-- | LuaSL/testLua/yueliang-0.4.1/test_lua/README | 65 |
1 files changed, 65 insertions, 0 deletions
diff --git a/LuaSL/testLua/yueliang-0.4.1/test_lua/README b/LuaSL/testLua/yueliang-0.4.1/test_lua/README new file mode 100644 index 0000000..07d9eb2 --- /dev/null +++ b/LuaSL/testLua/yueliang-0.4.1/test_lua/README | |||
@@ -0,0 +1,65 @@ | |||
1 | test_scripts-5.*.lua | ||
2 | ---------------------- | ||
3 | |||
4 | The scripts test_scripts*.lua are for exercising the frontends. Such | ||
5 | testing is non-exhaustive, but useful all the same. | ||
6 | |||
7 | The files in the 5.0 directory are the sample scripts from the Lua 5.0.x | ||
8 | test directory. Ditto for the 5.1 directory. See the COPYRIGHT_Lua5 for | ||
9 | the copyright notice. | ||
10 | |||
11 | For example, to run the 5.0.x script tester: | ||
12 | |||
13 | >lua test_scripts-5.0.lua | ||
14 | |||
15 | Or, if you have both Lua 5.0.x and Lua 5.1.x, you can prepare two | ||
16 | binaries and run them like this: | ||
17 | |||
18 | >lua5.0 test_scripts-5.0.lua | ||
19 | >lua5.1 test_scripts-5.1.lua | ||
20 | |||
21 | If the compilation result is exact, "CORRECT" is printed, otherwise both | ||
22 | binary chunks are written to the current directory as bc1.out and | ||
23 | bc2.out. You can use a disassembly tool like ChunkSpy to generate | ||
24 | listings for both files, then they can be compared with a visual diff | ||
25 | tool. ChunkSpy 0.9.8 supports 5.0.x and 5.1.x. | ||
26 | |||
27 | For testing additional files, add the argument "ALL" like this: | ||
28 | |||
29 | >lua test_scripts-5.0.lua ALL | ||
30 | |||
31 | This will pull in additional personal script files for testing. But in | ||
32 | order to do so, you'd have to adjust the files files-other-*.txt. | ||
33 | |||
34 | Current status: | ||
35 | |||
36 | Frontend version File set Result | ||
37 | --------------------------------------------------------------------- | ||
38 | Yueliang 5.0.3 files-lua-5.0.txt ALL CORRECT | ||
39 | files-yueliang-5.0.txt ALL CORRECT | ||
40 | Yueliang 5.1.2 files-lua-5.1.txt ALL CORRECT | ||
41 | files-yueliang-5.1.txt ALL CORRECT | ||
42 | --------------------------------------------------------------------- | ||
43 | |||
44 | test_parser-5.x.lua | ||
45 | ------------------- | ||
46 | |||
47 | The script files test_parser-5.0.lua and test_parser-5.1.lua contains | ||
48 | many test cases for both parsers. There are a lot of failure cases as | ||
49 | well as pass cases in order to exercise the parsers well, though the | ||
50 | test list is not exhaustive. | ||
51 | |||
52 | test_parser-5.0.lua 503 test cases | ||
53 | test_parser-5.1.lua 524 test cases | ||
54 | |||
55 | For the actual test scripts, see test_lparser2.lua in the respective | ||
56 | test directories of each front end. The 5.0.x front end of Yueliang | ||
57 | passed all the tests in test_parser-5.0.lua without any failures, while | ||
58 | testing of the 5.1.x front end using test_parser-5.1.lua led to one | ||
59 | bug found and fixed. | ||
60 | |||
61 | For Lua 5.0.2, see Yueliang 0.1.3, which was the last release of Lua | ||
62 | 5.0.2 material. | ||
63 | |||
64 | For Lua 5.1.1, see Yueliang 0.2.1, which was the last release of Lua | ||
65 | 5.1.1 material. | ||