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 "DSDP/MTJ/Tests/Instructions"
(New page: == Test Procedure == === Step 1: Download Prerequisites ===) |
(→Step 1: Download Prerequisites) |
||
| Line 1: | Line 1: | ||
| − | |||
== Test Procedure == | == Test Procedure == | ||
=== Step 1: Download Prerequisites === | === Step 1: Download Prerequisites === | ||
| + | These are the prerequisites to install MTJ: | ||
| + | * Java Runtime Environment (JRE) version 1.5.0 or greater. | ||
| + | * Eclipse SDK 3.3.2 ([http://download.eclipse.org/eclipse/downloads/drops/R-3.3.2-200802211800 build page]) ([http://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops/R-3.3.2-200802211800/eclipse-SDK-3.3.2-win32.zip download win32 zip]) | ||
| + | |||
| + | === Step 2: Install MTJ === | ||
| + | The [http://download.eclipse.org/dsdp/mtj/downloads/ download page] has the latest builds produced by the MTJ Project | ||
| + | * Download and install the runtime, it has all components to test. | ||
| + | |||
| + | === 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'''=M20080221-1800 | ||
| + | ** Line 47: '''java.runtime.version'''=1.5.0_12-b04 | ||
| + | ** Line 77: '''os.name'''=Windows XP | ||
| + | ** Line 78: '''os.version'''=5.1 | ||
| + | |||
| + | === Step 4: Prepare for Bug Reports === | ||
| + | * Log in or create an account in Bugzilla. | ||
| + | * '''Click [https://bugs.eclipse.org/bugs/enter_bug.cgi?assigned_to=wgp010%40motorola.com&blocked=&bug_file_loc=http%3A%2F%2F&bug_severity=normal&bug_status=NEW&comment=-----------Enter%20bugs%20above%20this%20line-----------%0D%0AMTJ%20(version)%20Testing%0D%0AInstallation%20%3A%20eclipse-SDK-3.3.2%20(M20080221-1800)%20%0D%0AMTJ%20install%20%20%3A%20mtj-runtime%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%0A&component=General&contenttypeentry=&contenttypemethod=autodetect&contenttypeselection=text%2Fplain&data=&dependson=&description=&flag_type-1=X&flag_type-2=X&flag_type-4=X&flag_type-6=X&flag_type-7=X&flag_type-8=X&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=Windows%20XP&priority=P3&product=MTJ&qa_contact=&rep_platform=PC&short_desc=&version=unspecified 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, you can move this bookmark into the Toolbar; that way you can file a new proper bug report with a single button click. | ||
| + | |||
| + | |||
| + | ---- | ||
| + | |||
| + | |||
| + | '''You are ready to go now!''' - Check the [[DSDP/MTJ/Tests/Known_Issues_and_Workarounds|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. | ||
| + | |||
| + | [[Category:DSDP]] [[Category:MTJ]] | ||
Revision as of 13:38, 7 July 2008
Contents
Test Procedure
Step 1: Download Prerequisites
These are the prerequisites to install MTJ:
- Java Runtime Environment (JRE) version 1.5.0 or greater.
- Eclipse SDK 3.3.2 (build page) (download win32 zip)
Step 2: Install MTJ
The download page has the latest builds produced by the MTJ Project
- Download and install the runtime, it has all components to test.
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=M20080221-1800
- Line 47: java.runtime.version=1.5.0_12-b04
- Line 77: os.name=Windows XP
- Line 78: os.version=5.1
Step 4: Prepare for Bug Reports
- Log in or create an account in Bugzilla.
- 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, you can move this bookmark into the Toolbar; that way you can file a new proper bug report with a single button click.
You are ready to go now! - Check the 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.