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 "PTP/testing/Junittest"
| Line 17: | Line 17: | ||
</li> | </li> | ||
<li> | <li> | ||
| − | All test cases are required to start JUnit test and then | + | All test cases are required to start by "JUnit test" and then to run sdm manually in command line. Please follows the command on console window, eg. mpirun -np 5 ./sdm --localhost=127.0.0.1 --debugger=test --port=34567. |
<pre> | <pre> | ||
All cases can be changed the startup processes by modifying the value of "total_process" | All cases can be changed the startup processes by modifying the value of "total_process" | ||
Revision as of 22:04, 15 April 2007
Overview
PTP JUnit test can be divided into two parts (GUI test and non-GUI test). GUI test needs to run JUnit Plugin test to create an eclipse runtime-application. It can be used to test PTP viewers and GUI functions such as annotation marker, breakpoint marker, processes status, etc. Non-GUI test runs sdm manually. User needs to run JUnit test and then start sdm manually in command line.
Non-GUI JUnit test
All test cases are located on org.eclipse.ptp.debug.ui.tests.base package. The following steps illustrate how to setup and run JUnit test:
-
AbstractBaseTest - Global settings for all test cases under Non-GUI section
Change testing application name by modifying the value of "testAppName" Change testing application path by modifying the value of "appPath" Change event timeout by modifying the value of "timeout"
-
All test cases are required to start by "JUnit test" and then to run sdm manually in command line. Please follows the command on console window, eg. mpirun -np 5 ./sdm --localhost=127.0.0.1 --debugger=test --port=34567.
All cases can be changed the startup processes by modifying the value of "total_process"