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.
PTP/testing/Junittest
< PTP | testing
Revision as of 06:06, 15 April 2007 by Clement.chu.infotech.monash.edu.au (Talk | contribs)
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 the GUI stuff 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. It can avoid heavy GUI stuff and concentrates on backend connection.
Non-GUI JUnit test
All test cases are located on org.eclipse.ptp.debug.ui.tests.base package. The following steps are introducing 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 necessary to start JUnit test and then manually to run sdm. 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"