Re: [cdt-dev] createCProject vs createNewStyleCProject

[Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx>]

On Fri, Jan 9, 2015 at 1:12 PM, Andrew Gvozdev <angvoz.dev@xxxxxxxxx> wrote:

Ideally, each unit test should test one isolated case. This way when a test fails you know exactly what fails. Additionally to that, there should be "integration" or "system" test cases that test different components working together.

From this point of view the simplest project is created the better.

Are you saying that old-style projects are simpler than the new-style ones?

And IMHO cdt.core test cases should not involve dependency on managedbuild plugins.

Unfortunately, knowledge which files are included in the build and which are not is available only from the managedbuild plugin. This information is used by the indexer to decide which files to index. This situation is backwards since knowledge about inclusion/exclusion from the build transcends build systems and should not be monopolized by one of them.

Andrew

-sergey 

On Thu, Jan 8, 2015 at 7:42 PM, Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx> wrote:

I've just noticed that most tests use CProjectHelper.createCProject as opposed to CProjectHelper.createNewStyleCProject. In fact createNewStyleCProject methods don't even seem to support creation of C++ projects. This situation looks dangerous since the tests may not catch failures that happen only with the new style projects. Should we convert all tests to run on the new-style projects?

-sergey

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev