Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "RSE 1.0 Test Instructions"

(Step 6: Do your special test assignment)
 
(11 intermediate revisions by one other user not shown)
Line 1: Line 1:
Nav: [[DSDP/TM]] | [[RSE 1.0 Testing]] | RSE 1.0 Test Instructions | [[RSE 1.0M5 Known Issues and Workarounds]]
+
Nav: [[DSDP/TM]] | [[RSE 1.0 Testing]] | RSE 1.0 Test Instructions | [[RSE 1.0 Known Issues and Workarounds]] | [[RSE Manual Test Plan]]
 
<hr/>
 
<hr/>
  
 
== Latest News ==
 
== Latest News ==
  
* '''Do not test the following features yet:'''
+
* <font size="+1">'''See [[RSE 1.0 Known Issues and Workarounds]] now''' for other known bugs and how to avoid them.</font>
** 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
+
* <font size="+1">'''See [[RSE 1.0M5 Known Issues and Workarounds]] now''' for other known bugs and how to avoid them.</font>
+
  
 
== Test Procedure ==
 
== Test Procedure ==
 
=== Step 1: Download Prerequisites ===
 
=== Step 1: Download Prerequisites ===
RSE has been compiled against the Callisto 3.2 releases, so that's your required test environment:
+
RSE has been compiled against the Callisto 3.2 releases, but we'd like to do most testing against 3.2.1:
* [http://download.eclipse.org/eclipse/downloads/drops/R-3.2-200606291905 Eclipse Platform 3.2] - use the "SDK" or the "Platform" bundle, just as you like
+
* [http://download.eclipse.org/eclipse/downloads/drops/R-3.2.1-200609210945/index.php Eclipse Platform 3.2.1] - use the "SDK" or the "Platform" bundle, just as you like
* '''Optional''' - Remote CDT Launcher only: [http://download.eclipse.org/tools/cdt/releases/callisto/dist/3.1.0 CDT 3.1.0] - Install the runtime or the sdk package, or use the Callisto update site
+
* '''Optional''' - Remote CDT Launcher only: [http://download.eclipse.org/tools/cdt/releases/callisto/dist/3.1.1 CDT 3.1.1] - Install the runtime or the sdk package, or use the Callisto update site
* '''Optional''' - Experimental Discovery only: [http://download.eclipse.org/tools/emf/downloads/drops/2.2.0/R200606271057 EMF 2.2.0] - only the EMF runtime is needed, you can install more if you want or use the Callisto update site
+
* '''Optional''' - Experimental Discovery only: [http://download.eclipse.org/tools/emf/downloads/drops/2.2.1/R200609210005 EMF 2.2.1] - only the EMF runtime is needed, you can install more if you want or use the Callisto update site
  
The minimum installation is to get Eclipse-platform-3.2, and then install RSE-runtime-core and RSE-runtime-ssh only.
+
In addition to that, we'd like 1 tester to use the standard 3.2 environment:  [http://download.eclipse.org/eclipse/downloads/drops/R-3.2-200606291905 Eclipse Platform 3.2] /  [http://download.eclipse.org/tools/cdt/releases/callisto/dist/3.1.0 CDT 3.1.0] / [http://download.eclipse.org/tools/emf/downloads/drops/2.2.0/R200606271057 EMF 2.2.0].
 +
<br/>
 +
Although not officially supported, we'd appreciate if somebody could also run a test pass against
 +
[http://download.eclipse.org/eclipse/downloads/drops/S-3.3M3-200611021715/index.php Eclipse Platform 3.3M3].
 +
<br/>
 +
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)
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, as soon as they are available. We recommend waiting for the final 3.2.1 stream releases though. Do not test the M-builds leading up to the release.
+
* 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
+
<!--
+
[http://download.eclipse.org/eclipse/downloads/drops/S-3.3M1-200608101230/index.php Eclipse Platform 3.3M1] or  
+
-->
+
[http://download.eclipse.org/eclipse/downloads/drops/I20060922-0010/index.php 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 ===
 
=== Step 2: Install RSE ===
* The [http://download.eclipse.org/dsdp/tm/downloads/drops/S-1.0M5-200609221723/index.php RSE 1.0M5 download page] has all packages, mirrored to at least 18 mirrors.
+
* The [http://download.eclipse.org/dsdp/tm/downloads/drops/S-1.0RC3-200610291738/index.php 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
 
** 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
 
** If you dont want programmer examples or ISV docs, you can also pick the runtime packages
Line 40: Line 30:
 
** You know how to do it: Help > Software updates > Find and Install > New Remote Site
 
** 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
 
** 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.0M5 download page.
+
** When testing dstore: the Dstore server packages (rseserver-*) must be obtained from the RSE 1.0RC1 download page.
  
 
=== Step 3: Record your Test Environment ===
 
=== Step 3: Record your Test Environment ===
Line 46: Line 36:
 
* In Eclipse, choose '''Help > About Eclipse SDK''', press '''Configuration Details'''
 
* 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.
 
* '''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):
+
* 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 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 57: Line 47:
 
* '''java -version'''<br/>Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
 
* '''java -version'''<br/>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.
+
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 ===
 
=== Step 4: Prepare for Bug Reports ===
* <font size="+1">Click [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Target%20Management this link to check if you are already logged in to Bugzilla].</font><br/>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.
+
* <font size="+1">Click [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Target%20Management this link to check] if you are already logged in to Bugzilla.</font><br/>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 [https://bugs.eclipse.org/bugs/index.cgi?GoAheadAndLogIn=1 this link to log in to Bugzilla] if you are not already logged in
 
* Click [https://bugs.eclipse.org/bugs/index.cgi?GoAheadAndLogIn=1 this link to log in to Bugzilla] if you are not already logged in
 
-->
 
-->
* <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-----------Enter%20bugs%20above%20this%20line-----------%0D%0ARSE%201.0%20Testing%20round%201%0D%0Ainstallation%20%3A%20eclipse-platform-3.2%20%28M20060629-1905%29%2C%20cdt-3.1.0%0D%0ARSE%20install%20%20%3A%20update-site%20RSE-complete%0D%0Ajava.runtime%20%3A%20Sun%201.5.0_08-b03%0D%0Aos.name%3A%20%20%20%20%20%3A%20Windows%20XP%205.1%2C%20Service%20Pack%202%0D%0A------------------------------------------------%0D%0Asystemtype%20%20%20%3A%20Unix-ssh%20%28dstore-processes%29%0D%0Atargetos%20%20%20%20%20%3A%20SUSE%20LINUX%2010.1%20%28i586%29%0D%0Atargetuname%20%20%3A%20Linux%20osgiliath%202.6.16.21-0.21-default%20%231%20Tue%20Aug%2029%2016%3A42%3A05%20UTC%202006%20i686%20athlon%20i386%20GNU%2FLinux%0D%0Atargetvm%20%20%20%20%20%3A%20Sun%20Java%20HotSpot%28TM%29%20Client%20VM%20%28build%201.5.0_07-b03%2C%20mixed%20mode%2C%20sharing%29%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>
+
* <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-----------Enter%20bugs%20above%20this%20line-----------%0D%0ARSE%201.0%20Testing%20round%203%0D%0Ainstallation%20%3A%20eclipse-platform-3.2.1%20%28M20060921-0945%29%2C%20cdt-3.1.1%2C%20emf-2.1.1%0D%0ARSE%20install%20%20%3A%20update-site%20RSE-runtime-all%20%2B%20discovery%20%2B%20efs%0D%0Ajava.runtime%20%3A%20Sun%201.5.0_08-b03%0D%0Aos.name%3A%20%20%20%20%20%3A%20Windows%20XP%205.1%2C%20Service%20Pack%202%0D%0A------------------------------------------------%0D%0Asystemtype%20%20%20%3A%20Unix-ssh%20%28dstore-processes%29%0D%0Atargetos%20%20%20%20%20%3A%20SUSE%20LINUX%2010.1%20%28i586%29%0D%0Atargetuname%20%20%3A%20Linux%20osgiliath%202.6.16.21-0.21-default%20%231%20Tue%20Aug%2029%2016%3A42%3A05%20UTC%202006%20i686%20athlon%20i386%20GNU%2FLinux%0D%0Atargetvm%20%20%20%20%20%3A%20Sun%20Java%20HotSpot%28TM%29%20Client%20VM%20%28build%201.5.0_07-b03%2C%20mixed%20mode%2C%20sharing%29%0D%0A------------------------------------------------%0D%0A&commentprivacy=0&keywords=&dependson=&blocked=&maketemplate=Remember%20values%20as%20bookmarkable%20template&form_name=enter_bug this link to get a sample bug entry template]'''</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 "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.
 
* 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 ;-)
+
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.
 
Also, dont lose time searching for bugs - just file them, it's quick and easy to do.
  
 
=== Step 5: Basic Sanity Check ===
 
=== 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 <i>could</i> 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:'''
+
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 <i>could</i> 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.0M5
+
* Download and extract into H:\RSETest\1.0RC3
** eclipse-platform-3.2, org.eclipse.cdt-sdk-3.1.0, RSE-runtime-core, RSE-runtime-dstore, RSE-runtime-remotecdt
+
** 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.0M5\workspace
+
* Dbl click eclipse, workspace = H:\RSETest\1.0RC3\workspace
 
* Open Perspective Remote System Explorer
 
* Open Perspective Remote System Explorer
 
* New Connection, Linux, Next; Dstore, Launcher params, Server-Launcher=Rexec; Finish
 
* New Connection, Linux, Next; Dstore, Launcher params, Server-Launcher=Rexec; Finish
* Expand My Home/RSETest/1.0M5 ; New Filter, Next, name="Test1.0M5"
+
* 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 new filter, Show in table, create new folder "test"
 
* Select the test folder, Rightclick > launch shell
 
* Select the test folder, Rightclick > launch shell
Line 109: Line 99:
 
* What could we improve?
 
* What could we improve?
  
Comments:
+
=== Comments for testing round 1 ===
* It's good that so many users join the testing effort -- [[User:Martin.oberhuber.windriver.com]]
+
* 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) -- [[User:norbert.ploett.siemens.com]]
 +
* I thought it went very well. -- [[User:david_dykstal.us.ibm.com]]
 +
* I thought it was well organized -- better than most. -- [[User:ted.williams.windriver.com]]
 +
* I think the reminders are great! -- [[User:Michael.Scharf.windriver.com]]
 +
* We should have a formal database with test cases to perform. This could be just Wiki pages grouped by feature and/or use case. -- [[User:uwe.stieber.windriver.com]]
 +
* I thought the coverage was good. Also, the test instructions were good. -- [[User:kmunir.ca.ibm.com]]
 +
* FTP was just sanity tested since there are quite a lot of standing issues and the engine is going to be replaced. -- [[User:Javier.MontalvoOrus.symbian.com]]
 +
* The testing was very coordinated. -- [[User:Ewa.Matejska.palmsource.com]]
 +
* [[User:sumit.sarkar.gmail.com]] 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 ===

Latest revision as of 10:51, 19 September 2008

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 http://download.eclipse.org/dsdp/tm/updates (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: 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):

  • cat /etc/*-release
    Red Hat Enterprise Linux WS release 4 (Nahant Update 3)
  • 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
  • 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) -- User:norbert.ploett.siemens.com
  • I thought it went very well. -- User:david_dykstal.us.ibm.com
  • I thought it was well organized -- better than most. -- User:ted.williams.windriver.com
  • I think the reminders are great! -- User:Michael.Scharf.windriver.com
  • We should have a formal database with test cases to perform. This could be just Wiki pages grouped by feature and/or use case. -- User:uwe.stieber.windriver.com
  • I thought the coverage was good. Also, the test instructions were good. -- User:kmunir.ca.ibm.com
  • FTP was just sanity tested since there are quite a lot of standing issues and the engine is going to be replaced. -- User:Javier.MontalvoOrus.symbian.com
  • The testing was very coordinated. -- User:Ewa.Matejska.palmsource.com
  • User:sumit.sarkar.gmail.com 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