This appendix describes the main changes to the Developer’s Kit and the Developer’s Guide for this release and recent past releases.
New in Release 2.4
This section summarizes how the 2.4 Developer’s Kit and Developer’s Guide differ from their immediate predecessors.
- @card.requires comments in source files can use parameter expansion to specify path name components symbolically. CODE EXAMPLE 4-3 gives an example.
- @card.requires can be specified for test cases as well as classes.
- The new @card.ziprequires card file entry specifies a required zip or JAR file. See Required Files.
- The server part of a network test can obtain property values. See Writing the Server Part.
- In this guide, an erroneous note that said that testsuite.info properties cannot refer symbolicially (${propertyName}) to other property values has been removed. The following usage is legal in a testsuite.info file:
A=1
C=${A}
- OTA applications (MIDlets) can send log messages to the harness. See Application Logging for details.
- Test servers (see Writing Network Tests) that use keystores must be modified due to a change in the interface ResourceHelper. See devKitHome/docs/test-server-api/com/sun/midp/testmanager/ResourceHelper.html for details including an example.
- devKitHome/docs/ contains the Test Design Policies document that Sun engineers use when writing tests.
- In source file comment blocks, lines can be continued and non-ASCII characters can be specified. See Comment Block Overview for details.
New in Release 2.3
This section summarizes how the 2.3 Developer’s Kit and Developer’s Guide differ from their immediate predecessors.
New in Release 2.2
This section summarizes how the 2.2 Developer’s Kit and Developer’s Guide differ from their immediate predecessors.
- Samples illustrate the multi-level Logger API for generating log messages. A new class, Level, has been added to the test API.
- The description of the scope, readonly, and doc attributes that can be specified for test class and case properties has been corrected. See @card.property.
- Property expansion has been unified in runtime, benchmark, and OTA tests. All behave as OTA tests did in previous recent releases: A value in a case definition overrides a value in a class definition, and a value in a class definition overrides a value in a testsuite.info definition. In other words, if a user does not specify a property value, Runner.getProperty() always returns the most local default value. Properties and Parameter Expansion gives the details.
- Property expansion applies to special properties.
- filter is deprecated in property descriptions. Use keyword instead.
- @precondition is not required in test class or case comment blocks.
- The formerly required testsuite.info property SupportedFrameworks has been removed from this guide because it is no longer used.
- JDK version 1.5 is no longer supported. Use JDK version 1.6.0_03.
- The chapter “Converting 1.4 Test Suites to 2.0 Test Packs” has been removed because Java Device Test Suite version 1.4 is no longer supported.
- You can rename test pack properties while preserving compatibility with templates that use the old name. See Test Pack Property Rename File for details.
- Two methods, close() and flush() have been added to the Logger API.
- The role of test pack identifiers in the testsuite.info file, such as TestSuiteName, has been clarified for new and updated test packs. See Required Properties and Test Pack Identifiers.
- Test classes and cases can be assigned functionality and impact codes, from which the Java Device Test Suite calculates and reports the severity of a test failure. See @card.attribute for details. Sample tests have been updated with these codes.
- The interaction of push test components has been corrected, see Architecture of a Push Test.
- The descriptions of test pack versioning have been corrected and clarified. See Optional Properties , Test Pack Versioning Alternative, and Test Pack Version Identifier.
- The role of the optional policy.txt file for defining new permissions has been clarified. See Defining New Security Permissions.
- The use of the optional TSPermissions testsuite.info property has been clarified and corrected. See Optional Properties.
- A new appendix Exclude Lists describes how exclude lists can disable execution of buggy or incomplete tests.
New in Release 2.1.2
No change in this release.
New in Release 2.1.1
This section summarizes how the 2.1.1 Developer’s Kit differs from its predecessor.
- Advanced property values can be defined with markup in comment blocks for test cases and cases, not just in the testsuite.info file for test packs.
- The conceptual diagrams in Chapter 1 of this manual showing the test types have been updated.
- The version of the test pack can now be incremented by building with the ant target inc.testpack.version. For more information, see the property TestSuiteVersion under Required Properties.
- Sample test classes in the DevKit now demonstrate advanced property attributes such as .type, .min, .max, .values, and .readonly. This is now documented in Chapter 4 of the Developer’s Guide.
- Some environment variables have been renamed:
me.home is now called client.platform.home
me.lib is now called client.platform.lib
- The string “jtwi” has been eliminated from build files.
New in Release 2.1
This section summarizes how the 2.1 Developer’s Kit differs from its predecessor.
- The Developer’s Guide has been reorganized to separate material that is of interest to particular sets of readers, such as advanced and legacy topics.
- By default, card files and interactive test evaluation files are automatically generated from comments embedded in source files. See Chapter 4.
- By default, the packages.list file is generated automatically.
- In the sample distributed test documentation, the terms UUT (unit under test) and UE (execution unit) have been changed to TD (test device) and PD (partner device) for better consistency with product terminology. Test function is not affected.
- The officially supported Java Developer’s Kit is version 1.6.0_03. By default, tests are compiled to run with 1.5 JRE software.
- The $IPFILTER macro is provided for static push MIDlet registration. See Using $IPFILTER.
- The following new sample illustrates the use of log trace levels: devKitHome/tests/runtime/src/client/com/sun/samples/automated/Logging.java.
- A new chapter in this guide explains property value precedence and parameter expansion. See Chapter 16.
- ${TS_DIR} refers only to the Relay file system root. Formerly, it could also refer to the test pack root in the Developer Installation.
- You can customize the text displayed for new permissions questions. See Chapter 15 for details.
- You can specify text for configuration and template editors to display as a category name and description. See Categories.
- You can specify the location of server source files in a testsuite.info file with the new TestServerSourcesDir property. The value was formerly hard coded as src/server, which remains the default. The runtime sample includes a usage example.
- The structure of the MIDlet source files in the OTA sample test pack has been changed.
- You can specify the location of MIDlet files with the new testsuite.info MIDletDir and MIDletSourcesDir properties. The sample distributed and OTA test packs have usage examples.
- By default, the build creates a “catalog” of test pack components in the listings/ directory in the test pack root. You can disable generation by setting build.test.list=false in the test pack’s build.properties file. The listings.dir property specifies the output directory.
