README
1
2CONTENTS
3
4 ACPICA ASL grammar validation Test Suite (ASLTS)
5
6
7 ASLTS verifies, in "hardware-independent" mode, conformity of ACPICA
8ASL compiler and interpreter to the ACPI ASL grammar specification. The
9more common task of ASLTS is to check, in "hardware-independent" mode also,
10all the functionality of ACPICA which can be initiated and then verified
11from inside the test modules coded in ASL. The first local task is performed
12by the test collection named 'functional', to achieve the second one the tests
13of other collections are intended: complex, exceptions, etc. The conditional
14difference between the tests of 'functional' and 'complex' collections is that
15the tests of 'functional' collection checks specific functionality of the
16particular ASL operator while the tests of 'complex' collection verify the
17more common functionality.
18
19 The testing is performed in "hardware-independent" mode without any
20access to ACPI subsystem hardware. In this purpose the AcpiExec utility
21is used which includes the entire ACPICA subsystem and allows to execute
22the AML code and thus verify functionality of ACPICA subsystem.
23
24 The ASL source code is compiled to AML code and then passed to
25AcpiExec utility. In this relation one more type tests are provided,
26so called ASL-compilation control test collection, which check ability
27of ASL compiler to reveal and report incorrect ASL code.
28
29 The tests of the exceptional conditions test collection
30initiate and verify exceptional conditions, check that the
31exceptions occur (or not occur) in the expected specified way.
32
33 The testing is provided in both 32-bit and 64-bit modes
34(option -r of ASL compiler) as well both normal and slack
35modes (option -s of AcpiExec).
36
37
38tmp
39
40 directory is automatically created (if doesn't exist) while installing
41 or running the tests performed by the utility Do
42
43tmp/aml
44
45 directory is automatically created (if doesn't exist) while installing
46 the tests performed by the utility Do and contains 32-bit and 64-bit
47 AML codes of the tests
48
49tmp/RESULTS
50
51 directory is automatically created during the test execution
52 (if doesn't exist) initiated by the Do utility and contains results
53 (so called multi-results) of runs of tests - utility Do performs each
54 run of tests is several modes:
55 32-bit norm mode
56 64-bit norm mode
57 32-bit slack mode
58 32-bit slack mode
59 so the result of run of tests is called multi-result. It is located
60 into RESULTS/<date.time.revision> directory.
61
62bin
63
64 utilities to manager the tests
65
66src
67
68 source code of tests
69
70TESTS
71
72 per-collection list of run-time tests
73
74HOW_TO_INSTALL
75
76 actions needed to prepare the tests for running
77
78HOW_TO_USE
79
80 how to run the tests and explain the result of run
81
82Makefile.def
83
84 the common use targets and rules
85
86Makefile.switch
87
88 the uniform targets and rules to pass commands of make utility
89 to the specified enclosed directories
90
91Makefile
92
93 current directory targets and rules
94
95
96 THE UNIFORM STRUCTURE OF ASLTS SOURCE CODE
97
98The ASLTS source code contains files of the same name
99which are of the same functionality described below.
100
101DECL.asl
102
103 contains all the declarations corresponding to some test
104
105RUN.asl
106
107 contains all the invocations corresponding to some test
108
109MAIN.asl
110
111 contains declaration of DefinitionBlock corresponding to some test;
112 the DefinitionBlock contains method MAIN which is a starting method
113 of the test; as a rule, this file contains the relevant DECL.asl and
114 RUN.asl includes
115
116README
117
118 the brief description of the contents of the inclusive directory
119 (hierarchy of README files explaining the contents of directories)
120
121FULL
122
123 contains declaration of DefinitionBlock corresponding to some test
124 which is conglomeration of several other tests
125
126NOTE
127
128 any notes to not forget something to do etc.
129
130- end
131
