NetBeans 5.5 Test Specifications

How to Use the Table Below

The below table has a one-to-one correspondence with the modules to be translated on the NetBeans 5.5 translation status page. You may execute the test case(s) to verify the translations of each module you complete. For example, if you've completed the autoupdate module translation, go to autoupdate in the table at below. You can see the links to the test spec(s) for that directory.

All test specs were created by the NetBeans Quality Engineering team. This means that they are not specifically designed to test localizable elements, such as UI or messages; rather, they were created for functionality testing, so in many cases, it is overkill for localization. Use these test specs to navigate through the module to check the UI. You do not need have to check the product functionality per se, since this is normally done by the Quality Engineering team and some community efforts like NetCAT. For localization testing, focus on verifying the  translated UI.

Keep in mind that the goal of localization testing is as follows:

• verify that all messages and UI appear translated to the user;
• the translated messages do not break the functionality or the build;
• validate that the messages are grammaticallyand stylistically correct;
• validate the correctness and accuracy of the messages in comparison to the English or source version.

For your reference, all the test specifications for NetBeans 5.5 are on the NetBeans 5.5 Test Specifications page.

Because the test spec is not based on directory, but on functionality, some directories have multiple test specs (e.g. ide), and some directories do not have any test spec (e.g. libs and classfile). And also, some test specs are difficult to be categorized by directory (e.g. core, openide, and projects). However, you can see the related test specs, or a small  test guideline (e.g. diff) to verify your localized module. For example:

• If you are localizing core, please test localized UI with other two modules (openide and project), it's difficult to identify which messages are come from core, and which messages are come from openide. All related test spec is listed.
• If you update only small part of openide, you don't have to see all the listed test spec, you can pick up one of them, or some of them to verify you updates. Or, if you know how to display your updating messages in the IDE, you don't have to see the test specs, you can check your updating message in the actual localized IDE without any navigation.

Please give your any feedbacks, ideas, suggestions to the project mailing list. A major goal for the coming year will be to create localization-specific test specs. If you are interested in participating in this initiative, send an email to the project mailing list.

Test Specs by Module

Module (directory)	Test Spec
autoupdate	Autoupdate Module Installation
core	See openide test specs.
ide	Eclipse Project importer Welcome Screen
libs	Test can be skipped. If you need to check the translated UI in this module, go to the main menu [Tools]/[Module Manager]. And open "Libraries" node. The following libraries properties are come from translation from this directory. Commons Logging Integration JGoodies FormLayout Integration Java Secure Channel integration Apache Resolver Library 1.1 Swing Layout Extensions integration Xerces Integration
openide	Favorites Files and Projects view Projects (J2SE) Main Window Module Manager Navigator Output Window Property Sheet Window System Wizards
projects
installer	This is an out-of-date test spec, but it can be used to determine which panels should be verified during install/uninstall operations. Installer
ant	Ant
apisupport	NetBeans Platform Manager Projects Wizards Projects properties Projects operations Wizard for creating wizards Window Component Wizard Action Wizard
beans	Beans
classfile	Test can be skipped. If you need to check the translated UI in this module, go to the main menu [Tools]/[Module Manager]. And open "Libraries" node and check the property of "Classfile Reader".
clazz	Clazz
db	DB Explorer SQL Editor multiple select statement support Derby
debuggercore	Ant Debugger
debuggerjpda	JPDA Debugger
diff	Test case is not available. To check the UI of diff, select two .java files in "Projects" window, and select context menu [Tools]/[Diff]. So then, you can see the localized Diff window.
editor	"editor" module provides an infrastructure for various editors like Java Editor, JSP Editor, and others. For this module, it's enough to check Editor options by selecting main menu [Tools]/[Option], and select "Editor" from left pane.
extbrowser	Ext. browser
form	We have eight test specs in the following page. I recommend to follow Visual Development as a first step. "form" module is the module for GUI development aka Matisse. It's a big feature and difficult to check all the functionality as part of localization testing. Overall checking is enough. Please note that almost all the Property names and Component names come from the JDK itself. It means that it can not be localized in NetBeans. You don't have to investigate when you see many names still in English. Form editor
html	'html' module is for HTML editing. Editing functionality is not a part of localization. The "HTML editor" test spec is only for editing functionality, you can see the detailed editing feature, but not so many cases for UI checking. HTML editor You can check UI messages in the HTML palette or HTML Form palette which is displayed when HTML file is opened. See also "web".
httpserver	Test case is not available. 'httpserver' module is IDE's internal HTTP server. Most messages are for server runtime. You can check the UI of this module as follows: Select main menu "Tools" > "Options", and click "Advanced Options". Select node "IDE Configuration" > "Server and External Tool Settings" > "HTTP Server" In the right pane, you can see properties; from this module, and you can also see the dialog by clicking browse button "..." of "Hosts and General Access" property.
i18n	Internationalization
image	Test case is not available. "image" module is simple. It just displays the image file in the NetBeans Editor pane. You can see the UI by opening any image file (e.g. .png, .gif, or others). The only visible thing is Tool Bar, and you can see the pop-up message by moving the mouse cursor over each button.
j2ee	It is recommended to follow the "End to End scenarios", so you can see the overall features. Because Web Service features are tightly coupled in test specs, Web Service testing should be done as part of J2EE testing. Deployment descriptor (web.xml) editor J2EE (EJB & Web Services) Application Client EAR Project EJB 3.0 EJB with existing sources Enterprise Resources EJB Persistence Editor support Web Services Editor support JAX-RPC 1.1 Web Service Client JAX-WS 2.0 Web Service Client Persistence Unit Wizards End to End scenarios for Java EE 5: JAX-WS 2.0 Web Service from WSDL in EJB module JAX-WS 2.0 Web Service in Web Project Asynchronous JAX-WS Web Service Client End to End scenarios for J2EE 1.4: BGTranslator end to end scenario PhotoArchive scenario Library Reservation System scenario Message Board scenario Quoter end to end scenario Unit convertor scenario
j2eeserver	"j2eeserver" modules is an infrastructure to integrate J2EE server. Most UI messages are in "Servers" node in "Runtime" tab. Add Sun Java Enterprise System Application Server (GlassFish), or JBoss Applicatoin Server. So then, you can see the nested nodes and context menus. Here is another part of this module's feature (Persistence UI): Data Sources Management Test Specification
java	Java editor Java Java Hints
javacvs	NetBeans CVS Support
javadoc	JavaDoc
junit	JUnit
mdr	Test can be skipped. If you need to check the translated UI in this module, go to the main menu [Tools]/[Module Manager]. And open "Libraries" node and check the property of : "JMI reflective API", "Metadata Repository", "MOF Metadata Repository", "JMI generated API for MOF model", "JMI Utilities"
monitor	Http Monitor
openidex	Test can be skipped. If you need to check the translated UI in this module, go to the main menu [Tools]/[Module Manager]. And open "Libraries" node and check the property of: "Experimental Search API"
properties	Properties
refactoring	Refactoring - part 1 Refactoring - part 2 Refactoring - part 3
schema2beans	Test can be skipped. If you need to check the translated UI in this module, go to the main menu [Tools]/[Module Manager]. And open "Libraries" node and check the property of : "Schema-to-Beans Library" Most messages in this modules are runtime messages for NetBeans module developer.
serverplugins	Integration of JBoss Server Integration of Sun Java System Application Server Integration of Weblogic Server
tasklist	Tasklist
tomcatint	Integration of Tomcat Server
usersguide	JavaHelp And this module provide J2SE sample application "Anagram Game" and "GUI Form Examples". You can see those samples by selecting [File]/[New Project], and by selecting "Samples" > "General" node.
utilities	Utilities
versioncontrol	Test can be skipped. "versioncontrol" module provides an infrastructure to support Version Control System like CVS. If you need to check the translated UI in this module, go to the main menu [Tools]/[Module Manager]. And open "Libraries" node and check the property of: "Versioning"
web	JSP editor TLD editor Applet Headless Deployment HTML/JSP Palette Jsf Palette Jsf Support Jsf Persistence Struts User Scenario Web/Enterprise Application Debugging Web Projects and VCS Integration Wizards
websvc	See "j2ee" module.
xml	XML editor DTD editor CSS editor XSD editor