NetBeans 5.5 Testing Context - Advanced Testing Test Cases
Test specifications for Advanced Testing
in NetBeans 5.5 Testing Contest
Updated 16 November 2006
About the Test Cases
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
found on the
NetBeans 5.5 Test
Specifications page.
Purpose
of
Localization Testing
Localization (L10N) refers to the
process, on a properly
internationalized core product, of translating messages and
documentations as
well as modifying other locale specific files.
The goals of localization testing are as
follows:
- Verify that all translations are complete
and text does not
appear in
English, unless the English term is the preferred usage;
- UI components are not truncated or cut off and display completely;
- Verify that all characters render and display correctly (no
encoding or character/font display issues);
- Verify that the translated messages do not break the
functionality or the
build;
- Validate that the translations follow the standard language rules
(grammar, spelling, punctuation, style, etc.);
- Verify that the terminology is consistent throughout and across
the entire product (all UI is the same across modules; software UI and
messages match exactly with the Online Help and product documentation);
- Verify there are no overtranslations (items that should not be
translated such as code, commands, etc. that would cause a functional
failure);
- Validate the correctness and accuracy of the messages within
context (compare to the English);
- Verify that the software UI and messages match exactly with the
Online Help and product documentation.
Test Specs
Advanced Testing
1. Go to the community download page and download the NetBeans IDE
installer
- http://www.netbeans.info/downloads/dev.php
- Select 5.5 and Daily. Continue.
- Find the latest build (Example: NetBeans IDE 5.5 daily build
200611130100). Continue.
- You will see a page that has the Installers for the Multilanguage
builds. The download happens automatically when you choose the
platform.
- The file being downloaded might have a name similar to
"netbeans-5_5-daily-bin-200611130100-windows-ml_ja_zh_CN_pt_BR_Nov_2006_0100.exe"
2. Go through Installation Instruction to install the IDE http://www.netbeans.org/community/releases/55/install.html#standalone
3. Select a configuration (1 OS, 1 Browser, 1 Java SE....)
It is recommended to
test using the
localized (Brazilian Portuguese)
version of these platforms, where available.
OS/Locale
|
Locale
|
Java
SE
|
| Windows XP Pro SP2 |
Brazilian Portuguese |
Java Standard Development Kit
(JDK™) version 5.0 Update 9 or version 6.0 (download) |
| Solaris 10 Sparc/x64 (x86) |
pt_BR.UTF-8 |
| RH Fedora Core 3 |
pt_BR.UTF-8 |
| Windows 2000 SP4 |
Brazilian Portuguese |
| Mac OS 10.4.5 PPC |
Brazilian Portuguese |
4. Choose the specific module you wish to test from the Test Specs table below. Java EE 5 and related
modules and test cases
since this is a major new feature in NB 5.5.
5. Carefully
check the
localized UI and
report
the bugs you find.
Categories
Test specs are classified as "small", "medium" and "large".
- small: Testing steps are small, or test scenario is easy
or simple
- medium: Testing steps are not a small effort, but testing
can be done by following the specfic test spec.
- large: Test steps are not a small effort, and there are
some prerequisites in order to perform the testing.
Test Specs
