Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Unit testing support for Eclipse CDT
Hi,

I think I am ready to contribute my Tests Runner to Eclipse CDT. I have added support for test modules debugging (both CDI & DSF; however DSF support requires a few changes in CDT). I also cleaned up and added documentation comments to the code, so it is quite nicer now. I have attached the archive with sources and a patch with the necessary changes to CDT to this bug. The code is also available on github (https://github.com/xgsa/cdt-tests-runner/tree/tests_runner_for_cdt9).

However a few questions in which I am not sure are left:
  1. Should I create a separate feature for these projects or will they be included to some existing CDT feature?
  2. What about plugins versions? Should they be changed?
  3. I am not sure in build and test configuration files for my plugins. Can somebody review them? How my test suite should be integrated into CDT's one?
  4. There is also more technical question: I am not sure that my debug support implementation is good enough. In my launch delegate I have to modify launch configuration, providing the necessary arguments for executable and redirect it to the CDI or DSF launch delegate. When the launching is finished I revert the configuration back (I cannot pass temporary launch configuration to CDT launch delegates cause in this case the launch history will not work properly). Is this solution reliable? Maybe a special launch configuration attribute (e.g. ATTR_GENERATED_PROGRAM_ARGUMENTS) should be created and integrated to CDI & DSF? It would be nice if somebody review the org.eclipse.cdt.testsrunner.internal.launcher package more carefully, it is not big.

So... waiting for your feedback.


Thanks,
Anton

-------- Original message --------

You can use the existing bug. Just let us know here on cdt-dev when it’s ready and one of us will start the process.

 

Cheers,

Doug.

 

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of xgsa
Sent: Wednesday, August 31, 2011 10:02 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] Unit testing support for Eclipse CDT

 

What should be done from my side to make this happen? Should I open a new bug (or reuse ) when I will be ready? Or need I to do something more?

Anton

-------- Original message --------

I agree we should bring this in a feature for CDT 9. I'm also looking at the pkg-config work that Petri did as another candidate. And we have the Tilera Visualizer View as a third.
 
We must however bring it through IP review, and I would feel much better about the contribution if we had it checked anyway. Size shouldn't matter, especially as we have 9 months left in the release cycle. I will certainly help if we need things expedited.
 
Contributions like this came up at the multi-core call. As I stated there, this is why we moved to git. We can get larger contributions developed in the open at Github, EclipseLabs, Google Code, where have you, by a team of contributors and tested before bringing it in through the IP review. That way the review is done once and hopefully the contribution is large enough that we should feel comfortable holding the committer elections as soon as that contribution is merged into our master repo. This is how Linux is done, we can do the same.
 
Other thoughts?
Doug. 
 
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Alena Laskavaia
Sent: Tuesday, August 30, 2011 8:20 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Unit testing support for Eclipse CDT
 
Doug I think we should include this in CDT 9 as optional feature, easiest way
would be to make Anton a committer, and then we don't need contribution
review, because I suspect it is massive code
 
On Fri, Aug 26, 2011 at 4:19 PM, xgsa <xgsa@xxxxxxxxx> wrote:
Unit Test Support plugin was updated (feature version 3.0.1). New
features:
 
Rerunning of the selected tests or test suites was done (via context
menu of testing hierarchy). Multiple selection for rerun is supported
for Qt.Test & Google Test (Boost.Test does not support this feature).
Test runs history was implemented (running testing sessions in
parallel mode is also supported).
Message filters by level were supported.
Error handling was improved if a test module terminated unexpectedly.
 
I have updated the project wiki, so you can take a look at new
screenshots here.
 
It seems, the last major feature that is missing yet, is debug
support. I will try to implement it for the next update. Certainly, a
lot of small features (for example, UI performance should be improved)
should be added too, so any feedback on my work will be appreciated. Stay
tuned!
 
Anton
 
-------- Original message --------
 
Unit Test Support plugin was updated (feature version 2.0.1). The most
important:
 
Google Testing Framework support;
show failed only filters;
plain view of testing hierarchy;
 
A few important bugs were fixed (in particular, failure messages
reset, reported by Axel Müller).
 
Anton
 
-------- Original message --------
 
Hi,
 
I am working on the unit testing support for Eclipse CDT. It means
integration of existing C/C++ unit testing frameworks (such as
Boost.Test, Qt Test, Google Testing framework, CPPUnit, ...) into
Eclipse like JUnit support is done. I want to contribute it to the CDT
repository at one point, so I need your feedback.
 
Currently, these features are supported:
 
Tests running with support of the following frameworks:
 
Boost.Test;
Qt Test;
 
Tests hierarchy browsing in a separate view.
Test messages viewing, filtering by test case or test suite. Source
lookup is also supported.
Testing statistics (total/failed/aborted tests count, red/green bar).
Testing time measurement.
The list of provided tests runners may be easily extended writing a
new Tests Runner Plugin.
 
If you want to try it yourself, here is an instruction how to do it (a
few screenshots are also there). You can also see known problems &
planned features here. Here is a git repository (synchronized with
yours), that contains 3 new projects and a few changes in CDT sources.
 
So I want to know your opinion about current functionality features,
what is missing and should be implemented. Comments about source code
are also appreciated. If you have any questions - feel free to ask.
 
Anton.
 
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
 
 
 
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
 
 
 
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
 
 
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
 
 

 


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top