mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-04-29 19:45:01 +02:00
4af00a316e
Using more specific assert functions (e.g. assertEquals(a, b) rather than assertTrue(a.equals(b)) helps a bit to make the test more readable. It can also improve the display in the JUnit view, by showing expected and actual values. Also, there is no need to manually catch an exception and fail the test. If an exception is thrown, the test will fail automatically. Change-Id: I333cfd0d0ade41463dc773ab02e14df4b063a22f Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca> Reviewed-on: https://git.eclipse.org/r/38617 Reviewed-by: Alvaro Sanchez-Leon <alvsan09@gmail.com> Tested-by: Alvaro Sanchez-Leon <alvsan09@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 | ||