Skip to main content
Jump to: navigation, search

RSE 1.0 Test Instructions

Revision as of 10:51, 19 September 2008 by (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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

Latest News

Test Procedure

Step 1: Download Prerequisites

RSE has been compiled against the Callisto 3.2 releases, but we'd like to do most testing against 3.2.1:

  • Eclipse Platform 3.2.1 - use the "SDK" or the "Platform" bundle, just as you like
  • Optional - Remote CDT Launcher only: CDT 3.1.1 - Install the runtime or the sdk package, or use the Callisto update site
  • Optional - Experimental Discovery only: EMF 2.2.1 - only the EMF runtime is needed, you can install more if you want or use the Callisto update site

In addition to that, we'd like 1 tester to use the standard 3.2 environment: Eclipse Platform 3.2 / CDT 3.1.0 / EMF 2.2.0.
Although not officially supported, we'd appreciate if somebody could also run a test pass against Eclipse Platform 3.3M3.
The majority of testing should occur on the 3.2.1 stream though.

The minimum installation is to get Eclipse-platform-3.2.1, and then install RSE-runtime-core from the update site. To do something useful, you'll also need your choice of either FTP, or SSH, or the examples (one or more of them)

Step 2: Install RSE

  • The RSE 1.0RC3 download page has all packages, mirrored to at least 18 mirrors.
    • The simplest is to download and install the SDK, it has all components to test
    • If you dont want programmer examples or ISV docs, you can also pick the runtime packages
    • For testing dstore, you'll need one of the rseserver-* packages.
  • If you prefer installing 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
    • Pick the SDK, or the runtime just as you like
    • When testing dstore: the Dstore server packages (rseserver-*) must be obtained from the RSE 1.0RC1 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.
  • The most interesting lines in this file 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, please update your entry in the RSE 1.0 Testing round 2 table, and update your bugzilla bug entry template (see below). We'd like to 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 get a sample bug entry template
  • Edit the "Platform", "OS" and "Description" fields to match YOUR setup. The goal is to get YOUR personal customized bug entry template that you'll use to make your reports easily, while conveying all information about your system. When done, 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.0 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. Dont invest more than 30 minutes for this sanity check. Its more important to cover the coordinated test matrix right now. As an example only, here is the sanity check I'm doing:

  • Download and extract into H:\RSETest\1.0RC3
    • eclipse-platform-3.2.1, org.eclipse.cdt-sdk-3.1.1, RSE-runtime-core, RSE-runtime-dstore, RSE-runtime-remotecdt
  • Dbl click eclipse, workspace = H:\RSETest\1.0RC3\workspace
  • Open Perspective Remote System Explorer
  • New Connection, Linux, Next; Dstore, Launcher params, Server-Launcher=Rexec; Finish
  • Expand My Home/RSETest/1.0RC3 ; New Filter, Next, name="Test1.0RC3"
  • 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.

See the RSE Manual Test Plan

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?

Comments for testing round 1

  • It's good that so many users join the testing effort -- Martin Oberhuber
  • Given that all assignment are voluntary it is good that you try to formalize things somewhat. (Haven't seen this in the CDT) --
  • I thought it went very well. --
  • I thought it was well organized -- better than most. --
  • I think the reminders are great! --
  • We should have a formal database with test cases to perform. This could be just Wiki pages grouped by feature and/or use case. --
  • I thought the coverage was good. Also, the test instructions were good. --
  • FTP was just sanity tested since there are quite a lot of standing issues and the engine is going to be replaced. --
  • The testing was very coordinated. --
  • writes:
    • A presentation from RSE team could have really helped to ramp up our testing and know the features. I didn't have much time reading the documentation.  :)
      • Comment MOB: This was intentional, we wanted to test how good the standard RSE docs are.
    • Didn't like the remote console (term) part. Why command line is separate from the console? It was slow. The lines in the console was selectable, but when I right-clicked, "Open With" was disabled. Did not know what to do? And why this feature is there and what it is supposed to do.
      • Comment MOB: This is an FAQ. The command view is well suited for compile jobs only. We are going to contribute a full-blown terminal shortly after RSE 1.0.

Comments for testing round 2

  • I'm glad that more and more users get familiar with editing the Wiki, and making use of its features like notification -- Martin Oberhuber

Comments for testing round 3

Back to the top