NB69A11YandI18Ntesting
NetBeans 6.9 Accessibility and Internationalization Testing plan
Contents |
Results Table
Quality engineers will explicitly write issues filed during testing to this table :
| Area | QE Owner(s) | A11Y | I18N |
|---|---|---|---|
| Maven | Jaroslav Pospisil | DONE P3: 184972 | NOT TESTED |
| Web Services Client / Partner Services | Jaroslav Pospisil | NOT TESTED | NOT TESTED |
| PHP | Filip Zamboj | DONE P2: 184650, 184654, 184659, 184729 P3: 173606, 184621, 184630, 184636, 184644, 184647, 184656, 184661, 184663, 184736, 184737, 184739, 184741, 184742, 184745, 184747, 184751, 184754, 184755, 184757, 184760, 184806, 184807, 184809, 184813, 184815, 184817, 184823, 184825 | |
| Debugger | Marian Mirilovic | NOT TESTED | NOT TESTED |
| C-dev | Jara Uhrik | DONE P2: 184532, 184549, 184556 | NOT TESTED |
| Editor/ Java/ Refactoring | Peter Pis | DONE | sanity test - linewrap |
| OSGi | Tomas Musil | DONE | NOT TESTED |
| DB | Michael Nazarov | ||
| Java EE | Martin Schovanek/Michal Mocnak | NOT TESTED | NOT TESTED |
| JavaScript | Petr Blaha | NOT TESTED | NOT TESTED |
| Web, JSP, HTML, CSS | Jindra Sedek | DONE
P2: 184715 | NOT TESTED |
| XML, Installler/AU | Michael Nazarov | ||
| Mobility | Andrei Chistiakov | NOT TESTED | NOT TESTED |
| Java FX | Alexandr Scherbatiy/Lukas Hasik | DONE
P2: 184863, 184865, 184850, 184855, 184856, 184860, 184861 | NOT TESTED |
| CnD | Alexander Pepin | POSTPONED for 'Unit tests' feature No significant changes in UI | NOT TESTED |
| C/V, Platform | Ivan Sidorkin | NOT TESTED | NOT TESTED |
| Server Plugins | Davis Nguyen | ||
| Summary: | All Issues, P2 issues, P3 issues, P4 issues |
Accessibility
According to the NB 69 Quality Plan the NetBeans Quality Engineering will provide testing of accessibility during Apr 19-21. We agreed that testing will be provided only for areas that changed UI a lot or hasn't been tested yet. If your area is not tested then please write "NOT TESTED" to the table. If you are done with testing please write "DONE" to the proper cell.
A11Y-testing tool
To install the tester tool please follow the page at http://wiki.netbeans.org/A11YShortly
How to evaluate A11Y-tester output
It is not enough to execute A11Y-tester and file issues according to its output. While testing A11Y by A11Y-tester module there is human evaluation needed. The tool returns 2 types of results for each accessibility category of conflicts:
- 1/String "-none" in the output means that there is no conflict in appropriate category of conflicts.
- 2/The output of the tool tells us where could be potentially A11Y-issue but those suspicions need to be checked and the conclusion decision should be made whether it is issue or not according to common sense.
Testing process
We will use distributed process of testing NetBeans accessibility. It means that everybody from NetBeans Quality Engineering should execute A11Y testing in his/her responsible area (according to changes made in UI).
- For all new features/UI there should be executed "first round" of a11y-testing right after the feature is integrated. This testing is executed in the same range as "regular round".
- The "regular round" is usually executed at the same time for all team members according to the testing schedules. Quality engineer executes tests for all dialogs and UI components from the area of responsibility and evaluates the output. Issues are reported to issuezilla and the issue priority is set according to the Bug priority guidelines document. Add keyword "A11Y" into the keyword field of reported issue. We used to have issue summary prefix 'A11Y' but please don't use this convention and sign the a11y-issues just with the 'A11Y' keyword. The output from A11Y-tester is usually added to the issue description.
- Provide testing with the latest 6.9 Beta build or daily build.
Assessment
The 508 form will be submitted by May 3 at http://section508tool.sfbay/ and will contain link to this document.
Contact person
If you have questions related to accessibility feel free to contact Jaromir.Uhrik@Sun.Com
