站内搜索: 请输入搜索关键词
当前页面: 在线文档首页 > NetBeans API Javadoc (Current Development Version)

Change History for the NetBeans JUnit Extensions API - NetBeans API Javadoc (Current Development Version)

Introduction

This document lists changes made to the NetBeans JUnit Extensions API.


Index of APIs

Incompatible changes by date

Fuller descriptions of all changes can be found below (follow links).

Not all deprecations are listed here, assuming that the deprecated APIs continue to essentially work. For a full deprecation list, please consult the Javadoc.

All changes by date

Changes by version

These API specification versions may be used to indicate that a module requires a certain API feature in order to function. For example, if you see here a feature you need which is labelled 1.20, your manifest should contain in its main attributes the line:

OpenIDE-Module-Module-Dependencies: org.netbeans.modules.nbjunit > 1.20

Changes by affected class

org.netbeans.junit.Log

org.netbeans.junit.MockServices

org.netbeans.junit.NbTestCase


Details of all changes by API and date


NetBeans JUnit Extensions

Default implementation of Preferences isn't used for running tests anymore

Oct 13 '06; API spec. version: 1.38; affected top-level classes: NbTestCase; made by: rmatous

Not persistent implementation of java.util.prefs.Preferences is installed in place of the platform-specific default implementation for running tests. See document Preferences in NetBeans to learn more.

Added class MockServices

Jun 30 '06; API spec. version: 1.33; affected top-level classes: MockServices; made by: jtulach

The MockServices class now supports closer cooperation with Lookup. By default, clients listening to Lookup.Result changes will be notified about change in its content whenever one calls MockServices.setServices.

Added class MockServices

May 11 '06; API spec. version: 1.30; affected top-level classes: MockServices; made by: jglick

Added new utility to help unit tests create mock implementations of global services for lookup.

Non-deterministic execution can be made deterministic

Apr 1 '06; API spec. version: 1.28; affected top-level classes: NbTestCase Log; made by: jtulach; issues: #35067

An excelent tool to emulate race condition, deadlock or any other non-deterministic behaviour created in the form of Log.controlFlow method.

Added support for logging

Apr 1 '06; API spec. version: 1.27; affected top-level classes: NbTestCase Log; made by: jtulach; issues: #35067

Added two ways how to enable logging in a test case. One can either overwrite NbTestCase.logLevel method and return the right level to capture in the test and then all the messages logged with the level and greater will be sent to NbTestCase.getLog() stream which is placed in working directory.

Or one can directly call Log.enable to capture all the logging into a CharSequence which can be later queried for its content, usually by calling its.toString() method.


Built on May 28 2007.  |  Portions Copyright 1997-2007 Sun Microsystems, Inc. All rights reserved.