Skip to main content
Jump to: navigation, search

Difference between revisions of "ETrice/Test of Release Candidate"

Line 1: Line 1:
## Installation Test
+
== Installation Test
** download newest or recommended "Eclipse IDE for C/C++ Developers" from https://www.eclipse.org/downloads/packages/  
+
* download newest or recommended "Eclipse IDE for C/C++ Developers" from https://www.eclipse.org/downloads/packages/  
** unpack it
+
* unpack it
** create empty folder for workspace
+
* create empty folder for workspace
** open eclipse and select the new workspace
+
* open eclipse and select the new workspace
** for release candidates: install eTrice from developer build https://download.eclipse.org/etrice/<version>/updates
+
* for release candidates: install eTrice from developer build https://download.eclipse.org/etrice/<version>/updates
** for nightly: http://download.eclipse.org/etrice/nightly/updates
+
* for nightly: http://download.eclipse.org/etrice/nightly/updates
** for release use latest version from https://www.eclipse.org/etrice/downloads/
+
* for release use latest version from https://www.eclipse.org/etrice/downloads/
 +
 
 
1. Test Drag & Drop install
 
1. Test Drag & Drop install
 
2. delete workspace and eclipse version
 
2. delete workspace and eclipse version
Line 12: Line 13:
  
  
Checklist:
+
== Checklist:
 
* make sure the Eclipse Help is working
 
* make sure the Eclipse Help is working
 
* perform smoke test
 
* perform smoke test

Revision as of 01:47, 19 October 2019

== Installation Test

1. Test Drag & Drop install 2. delete workspace and eclipse version 3. Test the installation again with the update site


== Checklist:

  • make sure the Eclipse Help is working
  • perform smoke test
    • create Java tutorial in empty workspace
    • generate and run Hello World and PingPong
    • create C tutorial in empty workspace
    • generate and run Hello World and PingPong
    • create C++ tutorial in empty workspace
    • generate and run Hello World and PingPong
  • test hover help
  • [JH] run automatic GUI tests

Back to the top