Platform Core - Testing
As you know, we have hit Freeze 1 and we are now testing for the rest of the week. Besides testing the product as a whole, here are some of the areas that we have worked on lately and should focus on to ensure is stable.
Of course the list is not extensive so if you have items to add, please pass along to the team.
We should be focusing on stability and servicability. We don't want to crash and if bad things happen, is the user notified appropriately?
If you have any questions please ask.
Happy testing.
General Notes
- All testing should go through the executable. DO NOT start Eclipse with the Main class and args.
Platforms/Locales/JRE
- Win2000, Linux RH 7.2, WinXP (these are the ones that we have in our offices, others are available in the labs)
- en_US, ja_JP
- (some are available on internal web site, not sure where to get others) IBM JRE 1.3.1, IBM JRE 1.3.0, Sun JDK 1.3.1, Sun JDK 1.4
Startup
- test all command line paramters
- use the following characters in install directories: + -, etc etc
- remove plugins directory
- remove startup.jar
- remove boot
- remove xerces
- remove runtime
- remove jre
- always check .log to see what information is presented to the user
Registry Caching
- first time
- add new plugin
- remove plugin
- modify plugin
- make empty cache file
- make bogus cache file
- test against a lot of plugins in install dir
Project natures
- add new nature
- remove nature
- nature sets
- nature one-of
- add nature from disabled/non-existant plugin
- see natures doc for scenerios and expected behaviour
Project description
- 1.0 project in 2.0 workspace
- closed 1.0 project in 2.0 workspace
- delete .project from Navigator
- delete .project from Windows Explorer
- empty .project file
- bogus .project file
- readonly .project file
- add new entries to .project file
- see project description doc for scenerios and expected behaviour
Preference Store
- malformed ini file
- conflicting values
- valid files submitted at different levels (command line, plugin, etc)
- see pref store docs for scenerios, expected behaviour, and how to set up prefs
Ant Core
- progress and cancelation (check if UI exposes this)
- classpaths (external jars, etc)
- new External Tooling functionality
- ant scripts as builders
- refresh local
- convert path (provided by core resources)
PDE-Build
- features: build update jars with the feature.destination parameter to specify output dir for update.jar file
- plugins/fragments: build update jars with the plugin.destination parameter to specify output dir for update.jar file
- plugins/fragments: build.result.folder for specifying the output for src.zip, *.jar
- above is some new work in the pde-build area, Rodrigo may have more areas which he would like tested
Target Management
- now contributed by Team team (context menu "Deploy")
- the WebDAV target code needs to be enabled by renaming the org.eclipse.team.webdav/plugin.xml.off file to plugin.xml
- should be able to test against rain.ott.oti.com and paris.ott.oti.com (URLs to follow)
- Please check Platform/VCM Bugzilla component before submitting as there are a lot of open PRs since this is still a work in progress
- I believe that most of the PRs against the WebDAV target management code are prefixed with "dav:"
General
- installation of Eclipse in a R/O directory (easy to test on Linux)
- single installation, multiple concurrent workspaces
- multiple installations, single workspace (should fail)
- install/update