cornercorner
FeaturesPluginsDocs & SupportCommunityPartners

NB61L10nTestPlanPJZ

NetBeans IDE 6.1 Localization Test Plan (pt_BR, ja, zh)

Contents


1. Test Plan Identifier

1.1 Title

NetBeans IDE 6.1 Localization Test Plan

1.2 Revision History

2008-04-11 draft
2008-04-23 update, v 0.9
2008-04-24 approved, v 1.0


2. Introduction

NetBeans 6.1 is an update release that will address customer feedback by focusing on quality, feature regressions and performance. http://www.netbeans.org/products/ide/

Support for pt_BR (Brazilian Portuguese), ja (Japanese), and zh_CN (Simplified Chinese) locales will be included in the ML (Multi Lingual) installer. Other locale (language) support will also be available.


Reference

  • NetBeans IDE
 http://www.netbeans.org/
  • NetBeans 6.1 Localization Plan
 http://wiki.netbeans.org/NB61L10nPlan


3. Test items

3.1 NetBeans 6.1

 The following are the products that should be covered in the localization testing.

 Products
  • IDE/Profiler
  • Mobility
  • SOA
  • UML
  • Ruby
  • Web and Java EE
  • CND 


 Others
  • Installer
  • Update Center
  • Buleprints (if ready)
  • Stable Update Center
  • Bundles
  • Bundle with Java SE
  • Bundle with Application Server/GlassFish
  • Bundle with others

3.2 Test Focus

As NetBeans 6.1 is an update release to address performance issues and improve the overall quality of IDE, the localization testing for this release should focus on new translation and regression.

3.2.1 Major Update In 6.1

The following are the top 10 updates from the localization point of view.

  • java/beans
  • ide/mercurial
  • soa/compapp-manager-jbi
  • ide/db-mysql
  • soa/bpel-mapper
  • enterprise/j2ee-websphere6
  • java/spring-beans
  • xml/xml-xpath-ext
  • cnd/cnd-editor
  • cnd/cnd

3.2.2 Areas to be tested

  • Localized User Interface (label and message)
  • Localized OnlineHelp
  • IDE features

3.2.3 Areas not to be tested

  • Performance
  • Accessibility
  • 3rd party Application

3.3 Test Environment:

3.3.1 Operating Systems

  • Solaris 11 SPARC/x64
  • Solaris 10 SPARC/x64
  • Ubuntu 7.x x86
  • Red Hat Enterprise Linux 4 x86
  • Windows XP Professional SP2 x86
  • Windows Vista Business x86
  • Mac OS 10.5 Intel/PPC
  • Mac OS 10.4.x PPC

3.3.2 Java SE

  • 6.0 Update 6 (or higher) on Win, Linux and Solaris
  • 5.0_13 on Mac

3.3.3 Application Server

  • AS 9.1 UR PE (GlassFish v2UR)
  • Tomcat 6.0

3.3.4 Database

  • JavaDB 10

3.3.5 Web Browser

  • Firefox 2.0
  • IE 6.0
  • IE 7.0
  • Safari

3.3.6 VCS

  • CVS 1.12
  • Subversion 1.4
  • Mercurial 0.9.5


Reference: NetBeans 6.1 Supported Platforms

4. Approach

4.1 Test Case Reference

  • Test Specifications for NetBeans 6.1
 http://wiki.netbeans.org/TestSpecifications61
  • Tutorials and other documents
 http://www.netbeans.org/kb/

4.2 QA Phase

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

QA Phase 1:

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

  • sanity test for all supported platforms/locales
  • results should be recorded regularly
  • when test period expires, all status must be recorded
  • one test case will be executed on a few select platform/locale combinations
  • the combinations will be defined in 5.4 Test Matrix
  • when bugs are fixed, regression test shall be done

QA Phase 2:

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

  • install/uninstall on all platform/locale
  • sanity test IDE by quickly creating, building and running small applications
  • sanity test online help by opening the help, randomly selecting some chapters, and searching etc.
  • when bugs are fixed, regression test shall be done

4.3 Test Matrix and result

4.3.1 Test Matirx

  • QA Phase 1
OS H/W Java Language
Solaris 11 x64/x86 6 ja
Solaris 10 SPARC 5 zh_CN
Ubuntu 7.x x86 6 pt_BR
Windows XP x86 6 all
Windows Vista x86 6 zh_CM
Mac OS 10.4.x Intel 5 ja


  • QA Phase 2

All languages check on platforms defined in section 3.3.1.

4.3.2 Test Result

4.4 Bug Management

4.4.1 Report

All 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).

4.4.2 Track

Localization bugs

Reference:

5. Quality Criteria

5.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.


5.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.
  • All docs packages have been made and include final translated pdf books.


6. Test Deliverables

  • Localization test plan (this document)
  • Lists of test cases for each component (refer to section 4.1)
  • Bug Reports
  • Testing closure report

7. Staffing and training needs

Plan

Ming Zhou (Beijing)
Ashizawa Kazunori (Tokyo)


8. Schedule

plan revised
start end start end status
QA Phase 1 2008-04-28?? 2008-05-23??
QA Phase 2 2008-05-26?? 2008-05-30??


Reference:


9. Risks and contingencies

  • Potential localization or internationalization issues on platform and java supported by English version may not be detected during this localization testing because of limited test coverage.
  • Translation schedule
  • Resource issues: l10n, build engineering, NB Installer teams
Retrieved from "http://wiki.netbeans.org/NB61L10nTestPlanPJZ"