Skip to main content
Jump to: navigation, search

RSE 1.0 Test Instructions

Revision as of 09:55, 25 September 2006 by (Talk | contribs)

Nav: DSDP/TM | RSE 1.0 Testing | RSE 1.0 Test Instructions | RSE 1.0M5 Known Issues and Workarounds

Latest News

  • Do not test the following features yet:
    • Do not test FTP right now since it will change: Jakarta Commons Net has been added to the repository, but not integrated with the FTP services yet. We will expose FTP to testing during the second round.
    • Experimental Discovery is not yet operational. It will be tested in the second round.
    • The Experimental EFS Provider is not documented and works only partially. Do not test it yet.
  • There is a known problem with the IBM Java5 VM: IBM Java 2 Technology Edition 5.0 - please use a different VM
  • See RSE 1.0M5 Known Issues and Workarounds now for other known bugs and how to avoid them.

Test Procedure

Step 1: Download Prerequisites

RSE has been compiled against the Callisto 3.2 releases:

Although not officially supported, we'd appreciate if somebody could also run a test pass against Eclipse Platform 3.3M2. The majority of testing should occur on the 3.2 stream though. We currently discourage testing against M-builds towards Callisto 3.2.1 - please use the 3.2 reference platforms as long as 3.2.1 is not officially completed.

Step 2: Install RSE

  • The RSE 1.0M5 download page has all packages, mirrored to at least 18 mirrors.
  • Testers assigned to install from the update site please use (at least 15 mirrors)
    • You know how to do it: Help > Software updates > Find and Install > New Remote Site
    • Dstore server packages must be obtained from the RSE 1.0M5 download page.

Step 3: Record your Test Environment

As the first step after installation, please record your exact test environment, to ensure we get good bugzilla reports:

  • In Eclipse, choose Help > About Eclipse SDK, press Configuration Details
  • Copy & Paste the configuration into an empty text file, we might need such exact information later when working on bug reports.
  • On my system, the most interesting lines you may need to fill in the OS and JVM info on the testing page are (line numbers and contents vary on your platform, of course):
    • Line 7: eclipse.buildId=M20060629-1905
    • Line 47: java.runtime.version=1.5.0_07-b03
    • Line 77: XP
    • Line 78: os.version=5.1

On the target side, the following commands are helpful to find out exact system versions (you dont need to issue all of these commands right now):

  • cat /etc/*-release
    Red Hat Enterprise Linux WS release 4 (Nahant Update 3)
  • uname -a
    Linux 2.6.9-34.EL #1 Fri Feb 24 16:44:51 EST 2006 i686 athlon i386 GNU/Linux
  • java -version
    Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)

If your test setup changed, and you want to take part in the 2nd round of testing as well, please update your entry in the RSE 1.0 Testing table to record the exact OS and JVM versions. That way we can ensure that we get good coverage by asking people to use many different OS and JVM flavors.

Step 4: Prepare for Bug Reports

  • Click this link to check if you are already logged in to Bugzilla.
    If you get a bug entry form, you are logged in already; you can proceed with the next step. Otherwise, Log in or create an account.
  • Click this link to file bug reports
  • Edit the "Platform", "OS" and "Dscription" fields to match your setup, then press the Remember values as bookmarkable entry button.
  • In Firefox or Internet Explorer, I like to move this bookmark into the Toolbar; that way I can file a new proper bug report with a single button click.

You are ready to go now! - Check the RSE 1.0M5 Known Issues and Workarounds page once more to ensure you don't duplicate the most obvious known issues. Then, go ahead and file all bugs, glitches or enhancement requests or suggestions in Bugzilla right away. Thanks to your bookmark this will be really fast and easy to do. You may also record bugs against a bad website, unclear testing instructions, bad documentation etc -- file bugs as bugs can ;-)

Also, dont lose time searching for bugs - just file them, it's quick and easy to do.

Step 5: Basic Sanity Check

All testers, regardless of their main test signup, are encouraged to do a 30-minute sanity check of the most common actions in RSE. Please do explore RSE on your own a little bit, with your own assigned configuration - the steps below are just for example what could be done. This is the "exploratory" part of testing: it will help us understand how much the online docs and getting started helps, and thus improve the out-of-box experience. As an example only, here is the sanity check I'm doing:

  • Download and extract into H:\RSETest\1.0M5
    • eclipse-platform-3.2, org.eclipse.cdt-sdk-3.1.0, RSE-runtime-core, RSE-runtime-dstore, RSE-runtime-remotecdt
  • Dbl click eclipse, workspace = H:\RSETest\1.0M5\workspace
  • Open Perspective Remote System Explorer
  • New Connection, Linux, Next; Dstore, Launcher params, Server-Launcher=Rexec; Finish
  • Expand My Home/RSETest/1.0M5 ; New Filter, Next, name="Test1.0M5"
  • Select the new filter, Show in table, create new folder "test"
  • Select the test folder, Rightclick > launch shell
  • In shell, enter: cd ../te<ctrl+space>
  • enter: ps -> check icons for output
  • The following works with dstore only:
    • enter: cat
    • Open Processes > My Processes, find "cat" process and kill it
    • From Windows Explorer, Drag&Drop a ZIP archive into the remote test folder
    • In RSE tree, browse into the ZIP archive; dbl click on a text file
    • Copy & paste the text file out of the archive
    • Select the folder above the text file, right-click > Search
  • With the connections still connected, quit & restart RSE (should reconnect)

Step 6: Do your special test assignment

Detailed instructions are currently being written. Please check back here later, and have fun exploring RSE on your own in the meantime.

Final Comments

Please edit this page, and leave your comments here. It will help us understand who's actually read up to here and understands how to edit a Wiki :-) - and it will help us improve future testing efforts.

  • Did you like the format of this test?
  • Did you have any difficulties?
  • What could we improve?


Back to the top