Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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 42: | Line 42: | ||
=== Step 4: Prepare for Bug Reports === | === Step 4: Prepare for Bug Reports === | ||
| − | * <font size="+1">'''Click [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Target%20Management&version=1.0&component=RSE&rep_platform=PC&op_sys=Windows%20XP&priority=P3&bug_severity=normal&bug_status=NEW&assigned_to=dsdp.tm.rse-inbox%40eclipse.org&qa_contact=martin.oberhuber%40windriver.com&cc=&bug_file_loc=http%3A%2F%2F&short_desc=&comment= | + | * <font size="+1">'''Click [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Target%20Management&version=1.0&component=RSE&rep_platform=PC&op_sys=Windows%20XP&priority=P3&bug_severity=normal&bug_status=NEW&assigned_to=dsdp.tm.rse-inbox%40eclipse.org&qa_contact=martin.oberhuber%40windriver.com&cc=&bug_file_loc=http%3A%2F%2F&short_desc=&comment=%0D%0A%0D%0A--------------------------------------%0D%0ARSE%201.0%20Testing%20round%201%0D%0Ainstallation%20%3A%20Eclipse%20M20060629-1905%20platform-3.2%2C%20cdt-sdk-3.1.0%0D%0ARSE%20install%20%20%3A%20download%20RSE-runtime-core%2C%20runtime-dstore%2C%20runtime-remotecdt%0D%0Ajava.runtime%20%3A%20Sun%201.5.0_07-b03%0D%0Aos.name%3A%20%20%20%20%20%3A%20Windows%20XP%205.1%2C%20Service%20Pack%201%0D%0A--------------------------------------%0D%0Asystemtype%20%20%20%3A%20Linux-dstore%0D%0Atargetos%20%20%20%20%20%3A%20Red%20Hat%20Enterprise%20Linux%20WS%20release%204%20%28Nahant%20Update%203%29%0D%0Atargetvm%20%20%20%20%20%3A%20Sun%201.4.2_12-b03%0D%0A--------------------------------------%0D%0A&commentprivacy=0&keywords=&dependson=&blocked=&maketemplate=Remember%20values%20as%20bookmarkable%20template&form_name=enter_bug this link to file bug reports]'''</font> |
* Edit the "Platform", "OS" and "Dscription" fields to match your setup, then press the '''Remember values as bookmarkable entry''' button. | * 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. | * 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. | ||
| Line 80: | Line 80: | ||
Comments: | Comments: | ||
| − | * It's good that so many users join the testing effort -- [[User:Martin.oberhuber]] | + | * It's good that so many users join the testing effort -- [[User:Martin.oberhuber.windriver.com]] |
Revision as of 07:54, 22 September 2006
Contents
Latest News
- Jakarta Commons Net has been added to the repository, but not integrated with the FTP services yet. Therefore, please Do not test FTP right now since it will change. We will expose FTP to testing during the second round.
- Discovery is also not quite ready yet. We added it to the download page and update site but it is not yet operational.
- 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:
- 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, 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: 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)
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 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! - 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. 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:
- 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, 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
- 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
Step 6: Do your special test assignment
Detailed instructions will be posted on the RSE Manual Test Plan.
Final Comments
Please edit this page, and leave your comments here.
- Did you like the format of this test?
- Did you have any difficulties?
- What could we improve?
Comments:
- It's good that so many users join the testing effort -- User:Martin.oberhuber.windriver.com