Here I tried to give my classification of new features
available in the new major revision of the JT harness,
that we recently completed .
As I wrote
once, development of this product is primarily driven by
using it as a test harness for Technology Compatibility Kits. The next
big step in the history of the product was its adoption in
the new area of Java ME quality test
suites, specifically JDTS, the Java Device Test Suite. JDTS2.0
went out December 2006, see its DataSheet
for more information.
Among lots of other minor and major changes, this was first JDTS
version based on JavaTest
TM Harness, version 4.0.
The initial launch of the JT harness,
the Open Source
version of JavaTest Harness, was based on the current stable
version of the product, 3.2.2.
The version 4.0 was primarily driven and targeted to this release
of JDTS 2.0, due to tight time line it was developed
internally for some time and become available in open source only now
since version 4.1.1
Backward compatibility with JavaTest harness 3.2.2
Customization features.
The requirement was to make JavaTest 4 a testing platform, that can be
supplied
with product-specific functionality and have customizable functions and
appearance.
Custom splash screen can be used to provide stronger
identification of the JavaTest-based testing product.
Custom tool bars, menus, pop-up menus, preferences can be
used to associate functionality extensions with GUI
Customizable GUI rendering of a test's result - e.g. show
a
graph of some data for a test. This is targeted for test categories,
that may result
in more then just pass/fail criteria, like performance tests.
Plug-in report mechanism. It can be used
to fit the JavaTest-based test suite into the larger
testing/certification
system
Configuration process improvements
Configuration process is known as one of the most complex steps in
usage of the
large test suites, that are targeting multiple environments.
JavaTest 4 made significant steps to improve usability in this area.
New
usage models,
specific to quality vs compatibility testing area, were also addressed.
Improved configuration templates mechanism to allow
different levels of
configuration tuning.
Added new configuration interview question types
Per-test configuration, accessible through test tree
context
menu. This allows development of the test suites, where user is
required to configure only those parameters, that are minimally
necessary for
execution of specific test or group of tests and not pass through
complete configuration process for the whole test suite.
Management of test suite updates
Ability to dynamically apply updates using existing
installation of the configured testing product allows significant
decrease in cost of applying updates to
users, allowing more frequent updates and hence better product quality
Reporting
Merging report directories, generation of consolidated
report to improve support to multi-user environment.
XML formatted reports to simplify post-processing of test
results using custom tools and integration into large testing/reporting
infrastructure.
Other
Number of minor improvements, like: UI
enhancements, logging
java.net RSS Feeds
