如何修改Ceedling测试失败输出以支持Eclipse直接跳转至错误行

Hey there! I totally get the frustration of wanting Eclipse to jump straight to test failure lines without manually hunting through files. Let's break down two solid approaches to fix this—one where we tweak Ceedling's output directly, and another that might save you from writing a custom parser.

选项1：修改Ceedling的测试报告代码以输出完整文件路径 #

Since you're already poking around Ceedling's Ruby code, this is a straightforward fix once you know what to change. The key is to make sure the failure output includes the full relative path to your test file (from your project root) instead of just the filename.

Looking at your code snippet, I'm guessing you're working in a part of Ceedling that generates test failure summaries. Right now, it's probably outputting something like:

test_file.c:123: Failure: ...

We need to adjust that to include the path, like:

test/test_file.c:123: Failure: ...

Here's how to tweak the code:

1. Find the Ruby file in Ceedling's lib directory that handles test failure reporting (likely under ceedling/reporter or similar).
2. Look for lines where the test file name is being printed—your snippet shows you're accessing the test case's file property, probably something like test_case.file.
3. Instead of using just test_case.file, prepend the relative path to your test directory. For example, if all your test files live in the test/ folder at your project root, you can modify the line to:

   full_path = File.join('test', test_case.file)
   

   Then use full_path in your output string instead of test_case.file.
4. Make sure the final output line follows the format [full path]:[line number]: [failure message]—this is the standard format Eclipse's error parser looks for to enable direct jumps.

After making this change, re-run your tests. If the output now includes the full relative path, Eclipse should pick it up and let you click straight to the failing line.

选项2：使用现成的Eclipse+Ceedling集成（无需自定义解析器） #

If messing with Ruby code feels intimidating, there's a simpler route using Eclipse's built-in tools:

1. Use Eclipse CDT: The C/C++ Development Tools (CDT) has robust error parsing for C projects. Set up your Ceedling project as a CDT project—this might automatically configure the error parser to handle test outputs better.
2. Adjust Run Configuration Working Directory: In your Eclipse run configuration for Ceedling, set the "Working Directory" to your project's root folder. This ensures that any relative paths in Ceedling's output resolve correctly to your project files.
3. Check for Pre-built Parsers: Some Ceedling users have shared custom error parser configurations for Eclipse. You can search within Eclipse's marketplace or Ceedling's community docs for pre-made setups that handle test failure jumps out of the box.

快速测试技巧 #

After making any changes, run a failing test intentionally and check the console output. If you see lines like test/my_test_file.c:45: Assertion failed: ..., Eclipse should recognize that format—just click the line in the console, and it should jump straight to line 45 in my_test_file.c.

备注：内容来源于stack exchange，提问作者cSharpStarter