mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-04-29 19:45:01 +02:00
d0e93b665b
Hardcoding line numbers in tests make it a pain to modify the test sources. The approach adopted in the gdb testsuite is to look for a specific string in the source file and return the line number where it is found. I made a similar system for the CDT debug tests. I dubbed this system breakpoint tags, a tag being the string we look for in the source file. I modified the MIRunControlTest as an example, as well as GDBProcessesTest and MIRegistersTest because they are re-using the same breakpoints. SOURCE_PATH and EXEC_PATH were duplicated in many test cases, so I factored them in BaseTestCase. Change-Id: Id1e64b2064914005ab1d87e16704866aa1c8b9ec Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca> Reviewed-on: https://git.eclipse.org/r/36872 Tested-by: Hudson CI Reviewed-by: Elena Laskavaia <elaskavaia.cdt@gmail.com> |
||
|---|---|---|
| .. | ||
| org.eclipse.cdt.dsf.gdb | ||
| org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui | ||
| org.eclipse.cdt.dsf.gdb.tests | ||
| org.eclipse.cdt.dsf.gdb.ui | ||
| org.eclipse.cdt.examples.dsf.gdb | ||
| org.eclipse.cdt.gnu.dsf-feature | ||
| org.eclipse.cdt.gnu.dsf.source-feature | ||
| org.eclipse.cdt.gnu.multicorevisualizer-feature | ||
| org.eclipse.cdt.tests.dsf.gdb | ||