| Re: [cdt-dev] help needed: CDT refactoring test suite results |
In article <8B1BC84A-2B70-47D4-A5B0-A53B30A9F3B2@xxxxxxxxx>,
Martin Oberhuber <mober.at+eclipse@xxxxxxxxx> writes:
> Just an idea, when adding new tests you could consider a format
> that encodes the caret position / selection relative to the #TEST# markup:
>
> // #TEST#: R25 Rename the macro argument x_ from declaration 3:23-3:25
> // #TEST#: R99 Rename the macro argument x_ from usage 2:33-2:35
> // #TEST#: R26 Rename this macro 1:9-1:22
> #define MACRO_ONE_ARG(x_) (2.0f*x_)
That's a good idea. clang-tidy test suites have a similar sort of
markup to identify the warnings/errors emitted by the tool and the
expected change. e.g.
<https://github.com/llvm-mirror/clang-tools-extra/blob/master/test/clang-tidy/readability-simplify-bool-expr.cpp>
--
"The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline>
The Terminals Wiki <http://terminals-wiki.org>
The Computer Graphics Museum <http://ComputerGraphicsMuseum.org>
Legalize Adulthood! (my blog) <http://LegalizeAdulthood.wordpress.com>