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 "ETrice/Test of Release Candidate"
< ETrice
Ts.protos.de (Talk | contribs) |
Ts.protos.de (Talk | contribs) |
||
| (8 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | This is the final user acceptance test that has to be executed before each eTrice release. | |
| − | + | At this point most testing has already be done by the Continuous Integration process, including generating and executing the tutorial projects. | |
| − | + | The focus here is on the things the test automation can not detect. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| + | == Installation Test == | ||
| + | * download newest or recommended "Eclipse IDE for C/C++ Developers" from https://www.eclipse.org/downloads/packages/ | ||
| + | * unpack it | ||
| + | * create empty folder for workspace | ||
| + | * open eclipse and select the new workspace | ||
| + | * 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 release use latest version from https://www.eclipse.org/etrice/downloads/ | ||
| + | # Test Drag & Drop install | ||
| + | # delete workspace and eclipse version | ||
| + | # Test the installation again with the update site | ||
| − | + | == Test Tutorial Project in C == | |
| + | * Create a project | ||
| + | * filter for etrice | ||
| + | * eTrice C Tutorials | ||
| + | * Explorer must contain 3 Projects: | ||
| + | ** org.eclipse.etrice.modellib.c | ||
| + | ** org.eclipse.etrice.runtime.c | ||
| + | ** org.eclipse.etrice.tutorials.c | ||
| + | * run from lauch configurations | ||
| + | ** generate_HelloWorldC | ||
| + | ** run_CurrentTutorial_WindowsMinGW | ||
| + | * console should contain log: | ||
| + | <pre> | ||
| + | INFO: *** T H E B E G I N *** | ||
| + | INFO: node_subSystemRef_init | ||
| + | ### Hello World! ### | ||
| + | INFO: node_subSystemRef_start | ||
| + | type quit to exit | ||
| + | </pre> | ||
| + | * type quit in console and verify shutdown of program | ||
| + | <pre> | ||
| + | INFO: node_subSystemRef_stop | ||
| + | INFO: node_subSystemRef_destroy | ||
| + | INFO: *** T H E E N D *** | ||
| + | </pre> | ||
| + | * check generated msc in log/msc.seq | ||
| + | * generate, run and verify '''generate_PingPongC''' the same way | ||
| + | |||
| + | == Test Examples Project in C == | ||
| + | * create new project with the wizzard (new -> project -> eTrice C Examples) | ||
| + | * Step 1: generate, run, quit, check MSC | ||
| + | * Step 2: start one traffic light simulator GUI (run_simulator_1_block), generate, run, click request in GUI, check MSC | ||
| + | * Step 3: start one traffic light simulator GUI (run_simulator_2_blocks), generate, run, click requests in GUI, check MSC | ||
| + | * Step 4: start one traffic light simulator GUI (run_simulator_2_blocks), generate, run, click requests in GUI, check MSC | ||
| + | |||
| + | == Test Java and C++ Versions == | ||
| + | * for C++ use the same eclipse package as for C | ||
| + | * for Java use https://www.eclipse.org/downloads/packages/release/2019-09/r/eclipse-ide-java-developers | ||
| + | * run the same tests for Tutorials and Examples as in C | ||
| + | |||
| + | == Run Ping Pong Tutorial from Template Project in C == | ||
| + | Objectives: check tutorial documentation, test usability, test all graphical and textual editors | ||
| + | * run and veify tutorial as decribed in "Tutorial Ping Pong Java, C and C++" in Documentation | ||
| + | |||
| + | == Further Checks == | ||
* make sure the Eclipse Help is working | * make sure the Eclipse Help is working | ||
| − | * | + | * test hover help: for a couple of elements in Text Editor, e.g. ActorClass, ProtocolClass, ... |
| − | + | ||
| − | + | == Unclear == | |
| − | + | * perform smoke test -> What is that? | |
| − | * | + | * [JH] run automatic GUI tests -> do they work? |
| − | * | + | |
| − | + | ||
* test hover help | * test hover help | ||
| − | |||
** <strike>C</strike> | ** <strike>C</strike> | ||
** <strike>Java</strike> | ** <strike>Java</strike> | ||
** Cpp - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=493059 Bug 493059 - [runtime.cpp] console ouput misbehavior] | ** Cpp - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=493059 Bug 493059 - [runtime.cpp] console ouput misbehavior] | ||
Latest revision as of 07:04, 19 October 2019
This is the final user acceptance test that has to be executed before each eTrice release. At this point most testing has already be done by the Continuous Integration process, including generating and executing the tutorial projects. The focus here is on the things the test automation can not detect.
Contents
Installation Test
- download newest or recommended "Eclipse IDE for C/C++ Developers" from https://www.eclipse.org/downloads/packages/
- unpack it
- create empty folder for workspace
- open eclipse and select the new workspace
- 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 release use latest version from https://www.eclipse.org/etrice/downloads/
- Test Drag & Drop install
- delete workspace and eclipse version
- Test the installation again with the update site
Test Tutorial Project in C
- Create a project
- filter for etrice
- eTrice C Tutorials
- Explorer must contain 3 Projects:
- org.eclipse.etrice.modellib.c
- org.eclipse.etrice.runtime.c
- org.eclipse.etrice.tutorials.c
- run from lauch configurations
- generate_HelloWorldC
- run_CurrentTutorial_WindowsMinGW
- console should contain log:
INFO: *** T H E B E G I N *** INFO: node_subSystemRef_init ### Hello World! ### INFO: node_subSystemRef_start type quit to exit
- type quit in console and verify shutdown of program
INFO: node_subSystemRef_stop INFO: node_subSystemRef_destroy INFO: *** T H E E N D ***
- check generated msc in log/msc.seq
- generate, run and verify generate_PingPongC the same way
Test Examples Project in C
- create new project with the wizzard (new -> project -> eTrice C Examples)
- Step 1: generate, run, quit, check MSC
- Step 2: start one traffic light simulator GUI (run_simulator_1_block), generate, run, click request in GUI, check MSC
- Step 3: start one traffic light simulator GUI (run_simulator_2_blocks), generate, run, click requests in GUI, check MSC
- Step 4: start one traffic light simulator GUI (run_simulator_2_blocks), generate, run, click requests in GUI, check MSC
Test Java and C++ Versions
- for C++ use the same eclipse package as for C
- for Java use https://www.eclipse.org/downloads/packages/release/2019-09/r/eclipse-ide-java-developers
- run the same tests for Tutorials and Examples as in C
Run Ping Pong Tutorial from Template Project in C
Objectives: check tutorial documentation, test usability, test all graphical and textual editors
- run and veify tutorial as decribed in "Tutorial Ping Pong Java, C and C++" in Documentation
Further Checks
- make sure the Eclipse Help is working
- test hover help: for a couple of elements in Text Editor, e.g. ActorClass, ProtocolClass, ...
Unclear
- perform smoke test -> What is that?
- [JH] run automatic GUI tests -> do they work?
- test hover help
-
C -
Java - Cpp - Bug 493059 - [runtime.cpp] console ouput misbehavior
-