|
1 <HTML> |
|
2 <HEAD> |
|
3 <TITLE> Resource compiler test code |
|
4 </TITLE> |
|
5 <!-- |
|
6 Copyright (c) 2005-2009 Nokia Corporation and/or its subsidiary(-ies). |
|
7 All rights reserved. |
|
8 This component and the accompanying materials are made available |
|
9 under the terms of the License "Eclipse Public License v1.0" |
|
10 which accompanies this distribution, and is available |
|
11 at the URL "http://www.eclipse.org/legal/epl-v10.html". |
|
12 |
|
13 Initial Contributors: |
|
14 Nokia Corporation - initial contribution. |
|
15 |
|
16 Contributors: |
|
17 |
|
18 Description: |
|
19 |
|
20 --> |
|
21 |
|
22 </HEAD> |
|
23 |
|
24 <BODY> |
|
25 <H1 ALIGN = CENTER> |
|
26 RCOMP test code |
|
27 </H1> |
|
28 |
|
29 Test procedures can be run from MNT TEST. This invokes TEST.CMD in the |
|
30 test code directory. The procedure takes a parameter ALL to run all of the |
|
31 tests or a number to run a specific test. TEST HELP says what each test |
|
32 does briefly. Here is a more complete explanation. |
|
33 |
|
34 <H2> |
|
35 Tests |
|
36 </H2> |
|
37 |
|
38 |
|
39 <H3>Test 1</H3> |
|
40 |
|
41 This performs various compilations of resource files and checks to see if the |
|
42 results are the same as in previous versions. Unfortunately, because the |
|
43 comparison utilities don't return a flag, results have to be inspected by |
|
44 eye. The test procedure tells you which files to inspect. |
|
45 <P> |
|
46 Note that some compiler warnings about deprecated non-unicode character values |
|
47 will be output during this test. |
|
48 |
|
49 <H3>Test 2</H3> |
|
50 |
|
51 This compiles a test source file containing deliberate errors. Because the |
|
52 compiler usually stops when it encounters an error, this is done by |
|
53 repeatedly compiling the same source with different preprocessor flags |
|
54 set to enable the offending text. This is driven by a file called TEST2.DAT |
|
55 which contains the flags and a brief description of their effects. |
|
56 <P> |
|
57 Unfortunately (again), the error messages from the compiler can't be easily |
|
58 redirected for automated testing so they have to be inspected by eye. The |
|
59 output is adjusted to keep this uncluttered on the screen. |
|
60 <P> |
|
61 The current set of errors is as follows: |
|
62 |
|
63 <DL> |
|
64 <DT>STUPID |
|
65 <DD>Tries to define an unknown character set. This just generates |
|
66 a warning mesage. |
|
67 |
|
68 <DT>ERROR_INVALID_MEMBER |
|
69 <DD>A resource member keyword is mis-spelled. This gives a wonderful |
|
70 "Label not found" error. |
|
71 |
|
72 <DT>MAIN_SYNTAX_ERROR_1 |
|
73 <DD>STRUCT is mis-spelled as STRICT, giving a "Syntax error". |
|
74 |
|
75 <DT>H_SYNTAX_ERROR_1 |
|
76 <DD>As above but in an include file, so you can see that the filename |
|
77 where the error occurs is reported correctly. |
|
78 |
|
79 <DT>ERROR_MISSING_STRUCT |
|
80 <DD>Leave out a struct definition. This gives another "label not found" |
|
81 message. |
|
82 |
|
83 </DL> |
|
84 |
|
85 |
|
86 |
|
87 <HR> |
|
88 </BODY> |
|
89 |
|
90 </HTML> |