Sun Microsystems Javac -d V2.0 V2.0/test.java, V2.0/example/test.class, STATUSFailed.3 errors

3.Compile the V2.0/test.java source file version with this command, noting that this newly compiled version serves as the implementation class under test.

% javac -d V2.0 V2.0/test.java

This step generates the following new class file to be tested against the test.sig file in the next step:

./V2.0/example/test.class

4.Run the SignatureTest command against the new class file using the -outoption to direct the results to a report.txt file with this command:

%java -cp V2.0:$CLASSPATH \ com.sun.tdk.signaturetest.SignatureTest \ -apiVersion 2.0 \

-package example \

-FileName test.sig \ -out report.txt

To set the CLASSPATH, see “CLASSPATH and -classpathSettings” on page 10. The command produces a console message similar to this:

STATUS:Failed.3 errors

5.Examine the result of the comparison made by the tool in the newly created report.txt file noting that it should be similar to CODE EXAMPLE A-4with possible differences due to your system characteristics.

This report file lists the tested differences between the reference API and the implementation under test. Also see “Report Formats” on page 24.

Note – Save the files you created in this procedure for use next in “Example

SetupAndTest Command” on page 34.

CODE EXAMPLE A-4 The report.txt File

SignatureTest report

Tested version: 2.0

Check mode: src [throws normalized]

Constant checking: off

Missing Methods

---------------

example.test: method public <%0 extends java.lang.Object> {%%0} example.test.get({%%0})

Appendix A Quick Start Examples 33