Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "RSE 1.0 Test Instructions"
| Line 13: | Line 13: | ||
== Step 2: Install RSE == | == Step 2: Install RSE == | ||
| − | * Testers assigned to the update site please use http://download.eclipse.org/dsdp/tm/testUpdates | + | * Testers assigned to install from the update site please use http://download.eclipse.org/dsdp/tm/testUpdates |
| + | ** You know how to do it: Help > Software updates > Find and Install > New Remote Site | ||
* Dstore server packages as well as full downloads are on the RSE 1.0M5 download page. | * Dstore server packages as well as full downloads are on the RSE 1.0M5 download page. | ||
| Line 22: | Line 23: | ||
* 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): | * 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 7: eclipse.buildId=M20060629-1905 | ||
| − | |||
| − | |||
| − | |||
** Line 47: java.runtime.version=1.5.0_07-b03 | ** Line 47: java.runtime.version=1.5.0_07-b03 | ||
** Line 77: os.name=Windows XP | ** Line 77: os.name=Windows XP | ||
| Line 30: | Line 28: | ||
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): | 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): | ||
| − | * uname -a<br/>Linux parser.takefive.co.at 2.6.9-34.EL #1 Fri Feb 24 16:44:51 EST 2006 i686 athlon i386 GNU/Linux | + | * '''uname -a'''<br/>Linux parser.takefive.co.at 2.6.9-34.EL #1 Fri Feb 24 16:44:51 EST 2006 i686 athlon i386 GNU/Linux |
| − | * cat /etc/*-release<br/>Red Hat Enterprise Linux WS release 4 (Nahant Update 3) | + | * '''cat /etc/*-release'''<br/>Red Hat Enterprise Linux WS release 4 (Nahant Update 3) |
| − | * | + | * '''java -version'''<br/>Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode) |
| − | + | ||
| − | + | ||
| − | + | ||
== Step 4: Prepare for Bug Reports == | == Step 4: Prepare for Bug Reports == | ||
| Line 42: | Line 37: | ||
* In Firefox, I like to move this bookmark into the Toolbar; that way I can file a new proper bug report with a single button click. | * In Firefox, 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! - Please 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 are ready to go now! - Please 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 ;-) |
As the testing progresses, we will post an [[RSE 1.0 Testing Bug Hitlist]] with the most obvious or frequently reported bugs, such that you can avoid filing the same bug again that somebody else already has. But in general, dont lose time searching for bugs - just file them, it's quick and easy to do. | As the testing progresses, we will post an [[RSE 1.0 Testing Bug Hitlist]] with the most obvious or frequently reported bugs, such that you can avoid filing the same bug again that somebody else already has. But in general, dont lose time searching for bugs - just file them, it's quick and easy to do. | ||
| Line 50: | Line 45: | ||
== Step 6: Do your special test assignment == | == Step 6: Do your special test assignment == | ||
| + | |||
| + | Detailed instructions will be posted on the [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tm.rse/tests/org.eclipse.rse.tests.manual/manual_tests.html?rev=HEAD&cvsroot=DSDP_Project&content-type=text/html RSE Manual Test Plan]. | ||
Revision as of 05:41, 22 September 2006
Contents
Step 1: Download Prerequisites
RSE has been compiled against the Callisto 3.2 releases:
- Eclipse Platform 3.2
- The Remote CDT Launcher needs CDT 3.1.0
- The Experimental Discovery Add-on needs EMF 2.2.0
We aniticipate that Callisto 3.2.1 will be available at the time of testing, so we encourage testers to use the 3.2.1 stream equivalents instead:
- Eclipse Platform 3.2.1
- CDT 3.1.1 for Remotecdt
- EMF 2.2.1 for Discovery
Although not officially supported, we'd appreciate if somebody could also run a test pass against Eclipse Platform 3.3M1 or Eclipse Platform 3.3M2. The majority of testing should occur on the 3.2.1 stream though.
Step 2: Install RSE
- Testers assigned to install from the update site please use http://download.eclipse.org/dsdp/tm/testUpdates
- You know how to do it: Help > Software updates > Find and Install > New Remote Site
- Dstore server packages as well as full downloads are on the RSE 1.0M5 download page.
Step 3: Record your Test Environment
As the first step after installation, please record your exact test environment, and update your entry in the RSE 1.0 Testing table to record the exact OS and JVM versions:
- 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: os.name=Windows 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):
- uname -a
Linux parser.takefive.co.at 2.6.9-34.EL #1 Fri Feb 24 16:44:51 EST 2006 i686 athlon i386 GNU/Linux - cat /etc/*-release
Red Hat Enterprise Linux WS release 4 (Nahant Update 3) - java -version
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Step 4: Prepare for Bug Reports
- 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, 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! - Please 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 ;-)
As the testing progresses, we will post an RSE 1.0 Testing Bug Hitlist with the most obvious or frequently reported bugs, such that you can avoid filing the same bug again that somebody else already has. But in general, 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. Feel free to also explore RSE on your own a little bit. The actual sanity check depends a bit on your configuration (minimal or full install, update site or download, what subsystem types to use). As an example, here is the sanity check I'm doing:
Step 6: Do your special test assignment
Detailed instructions will be posted on the RSE Manual Test Plan.