NetBeans IDE 6.9 Localization Test Plan (pt_BR, zh_CN, ja_JP)

Revision History

2010-05-04 draft


1. Introduction

NetBeans 6.9 is an update release.

Supports for pt_BR (Brazilian Portuguese), zh_CN (Simplified Chinese), and ja_JP (Japanese) locales will be included in ML (Multi Lingual) installer. Other locale (language) supports will also be available.

2. Testing Scope

2.1. NetBeans IDE 6.9

The followings are the product features that should be covered in the localization testing. Only new features and enhancements will be tested.

  • IDE
  • Java SE
  • Web & Java EE
  • Mobility
  • Ruby
  • C/C++
  • PHP
  • Groovy, Support for Groovy/Grails
  • JavaFX
  • Version control, issue tracking, Kenai support
  • Installer
  • Update Center
  • Bundles
  • JDK6 Update X with NetBeans IDE 6.9

2.2. Software (Platform and Runtimes)

Reference: NetBeans 6.9 Supported Platforms

Java SE

  • 6.0 - Full test on Win, Linux, Solaris, Mac platforms
  • 7.0, OpenJDK - To be tested for 2-3 test cases

Operating Systems

Windows Linux Solaris Mac OS X
Full test Windows XP Pro SP3/ Windows 7 Ubuntu 9.10 OpenSolaris 2010.03/ Solaris 10 SPARC 10.5 Intel

Servers and tested Java EE versions for particular servers

  • Glassfish v3
  • Tomcat 6.0 (Java EE5 + persistence in web, JAX-WS)
  • JBoss 5.0


  • JavaDB (supplied with IDE)
  • MySQL 6.x


  • Mercurial 1.1 *
  • Subversion 1.6 *
  • CVS 1.12

Note: bullet marked with "*" should be given higher importance when testing

Emulator Platforms of Mobility Pack

Supported SDKs:

  • Sun Java Wireless Toolkit 2.5.2 for CLDC - Windows and Linux version - BUNDLED
  • Sun Java ME SDK 3.0 (CLDC/CDC)

Other SDKs may be supported as well depending on vendors support or quality of SDK

Web Browsers

  • Firefox 3.5 (Solaris, Ubuntu, Windows XP) *
  • IE 8 (Windows 7) *
  • IE 6 (Windows XP)
  • Safari latest (Mac OS X) *

Note: bullet marked with "*" should be given higher importance when testing

2.3. Hardware

  • SPARC machines
  • x86/x64 PC machines
  • Intel Mac machines

2.4. Locale

  • pt_BR (Brazilian Portuguese)
  • zh_CN (Simplified Chinese)
  • ja_JP (Japanese)

This test plan is intended for these locales. Other locales would have different requirements, so they are out of scope of this document.

3. Features to be tested

  • Localized User Interface (e.g. label, menu, and message)
  • IDE features behavior in target locale

4. Features not to be tested

  • Performance
  • Accessibility
  • 3rd party Application
  • Online Help

5. Approach

5.1. Test Management

Test cases, matrices, and status will be maintained on the Wiki page.

Most test cases are assumed just to point at existing tutorials and/or base test cases with additional simple instruction. If required, step-by-step procedures can be described.

Each component lead is responsible to lead the effort of selecting which tutorial and/or base test cases will be used for the testing.

Execute test cases, and save results on the Wiki pages.

5.2. QA Phase

The testing will be divided into three phases (or more if necessary). Each test phase has predefined start date and end date.

QA Phase 0

This phase is to create test cases. This phase is expected to overlap QA Phase 1. This means that QA Phase 1 can start before QA Phase 0 completes.

QA Phase 1

When the QA Phase 1 starts, translation may not complete. This test phase should be completed by ML RC.

  • Execute tutorial-based test cases for all components
  • Sanity Test for all supported platforms/locales
  • When bugs are fixed, Regression Test shall be done
  • Results should be recorded regularly
  • When test period expires, all status must be recorded
  • One test case will be executed, at least, on 3 diferent platform/locale combinations
  • The combinations will be defined in 6.9 Test Matrices

QA Phase 2

This test phase must be completed by FCS GO/NoGO.

  • Sanity Test for all supported platforms/locales
  • Download Test for all supported platforms/locales
  • when bugs are fixed, Regression Test shall be done
Phase Start Date End Date

Note: * - estimated date based on general release schedule

5.3. Bug Management

Bug Report

Any bugs (localization, internationalization, and base) should be managed through issuezilla.

New L10N bugs should be filed to translatedfiles component, with CC to jf4jbugs (@netbeans.org).

New I18N bugs should be filed to appropriate components, with Summary started with "I18N - ", Keywords I18N, CC to jf4jbugs (@netbeans.org).

6. Quality Criteria

6.1. Entrance Criteria for FCS(RC) build testing

  • All translatable components have been translated and reviewed.
  • All l10n packages build environment has been created and tested.
  • All l10n packages can be built.

6.2. Pass Criteria for FCS(RC) build testing

  • All P1/P2 bugs have been fixed. Waived P2 bugs has been discussed and approved.
  • All P3 bugs have been evaluated.

7. Testing tasks

  • Platform installation
  • Test case creation in Wiki page
  • Test case execution

8. Risks and contingencies

  • Translation schedule
  • People resource

9. Reference

  • NetBeans IDE Home Page
  • NetBeans 6.9 Overview
  • New And Noteworthy in NetBeans 6.9
  • QA Base Team Test Specifications and Testing Progress
  • NB 6.9 Quality Criteria
  • NetBeans 6.9 Supported Platforms
  • NetBeans 6.9 Localization Schedule
  • NetBeans 6.9 Localization Scope
  • Team Roles and Communications
Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo