ive mention gtest since it kind of a special case, when i did the first
implementation both class and methods names that the AST parser produces
are completely different from what is in source code. So it will not detect
the class names if 1) the includes point to gtest source and 2) the prefix
added by the framework are included also in the search.

So for this case, the search function needs a bit complex to correctly pick
those functions. I still need to do a couple of tests now that i have this
running




On Fri, Apr 5, 2013 at 9:15 AM, wenns <notifications@github.com> wrote:

> In
> sonar-cxx-plugin/src/test/resources/org/sonar/plugins/cxx/xunit/project_finding_sources/tests2/Test4.hh:
>
> > @@ -0,0 +1,5 @@
> > +namespace ns{
> > +    class TestClass4{
> > +        void test1();
> > +    };
> > +};
>
> On 04/04/2013 06:07 PM, Jorge Costa wrote: In
> sonar-cxx-plugin/src/test/resources/org/sonar/plugins/cxx/xunit/project_finding_sources/tests2/Test4.hh:
> > @@ -0,0 +1,5 @@ > +namespace ns{ > + class TestClass4{ > + void test1();
> > + }; > +}; And we need to have code from other test frameworks, at least
> gtest should be included since is broadly used. My pull request was already
> dealing with it. The difficulty with this that the include files need to be
> correctly set, if not the parser will fail to construct anything. The
> problem here is how to create test data without having the complete
> framework in there.
> This test project should be framework agnostic, in my opinion. We just
> have to cover all combinations of classnames / headers / c-files in here.
> … <#13dd8d5864040506_>
>  Boost test i think it works pretty much as cppunit — Reply to this email
> directly or view it on GitHub <
> https://github.com/SonarCommunity/sonar-cxx/pull/22/files#r3657848>.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/SonarCommunity/sonar-cxx/pull/22/files#r3668528>
> .
>