Test other generators: run several tests in test_*/conanfile.py

[jgsogo]

We are introducing several changes with Conan v2 in mind, the biggest effort and challenge will be to modify recipes to work with new features backported from Conan v2 while we ensure they keep working with current Conan version.

One of the things we need to be really sure that works is the logic behind the generators and cpp_info. The best way to do it is to actually run a test_package for them. For sure we can run everything in the same test_package/conanfile.py, but IMHO it would be much clear to have each generator being tested in its own test_* folder. We don't need to go crazy with it, neither add it to every single recipe, but it might be really useful for those that define some convoluted cpp_info.name/filename and/or set_property together with components.

This is just a test and a proposal. The main point is that project files should be the same: same CMakeLists.txt, same .h/.cpp files. Only conanfile.py is different. Here I propose to keep this files in the test_package folder as it is the official one, while the other/s folder/s will just use sources from it.

Let's hear the CI and the people. Wdyt?

Note.- This feature was already there, but not documented.

[ghost]

I detected other pull requests that are modifying fmt/all recipe:

• [fmt] Remove old versions #9370

This message is automatically generated by https://github.com/ericLemanissier/conan-center-conflicting-prs so don't hesitate to report issues/improvements there.

[jgsogo]

As you can see in the table outputs, in the test logs, both test-package are executed:

********************************************************************************
conan test conan-center-index/recipes/fmt/all/test_cmakedeps/conanfile.py fmt/5.3.0@ --profile=/home/conan/w/BuildSingleReference/60145/3345f072-8cfa-48fc-ae4f-9fc0a3346760/profile.txt
********************************************************************************

...

********************************************************************************
conan test conan-center-index/recipes/fmt/all/test_package/conanfile.py fmt/5.3.0@ --profile=/home/conan/w/BuildSingleReference/60145/3345f072-8cfa-48fc-ae4f-9fc0a3346760/profile.txt
********************************************************************************

cc/ @czoido @SSE4 @franramirez688 any suggestions about the project structure?

[ericLemanissier]

what is the witchcraft which makes C3I run test_cmakedeps ? most of the contributors most likely just run conan create ... lib/1.0@ which only runs test_package right ?

[jgsogo]

what is the witchcraft which makes C3I run test_cmakedeps ? most of the contributors most likely just run conan create ... lib/1.0@ which only runs test_package right ?

@ericLemanissier , in C3i we run conan install --build=XXX and then conan test in order to provide better information in the output table (we can say if the error comes from the build or from the testing). The command conan test takes an argument which is the path to the conanfile.py from the test package... and we are just iterating all the folders that match test_*** pattern.

Of course, we will:

• document this behavior in this repository
• write a hook to ensure that there is always a test_package (users cloning the repo and running conan create will expect some test)

In this PR I'm interested in knowing if this is the best approach to test different generators, or we can figure out something better.

[prince-chrismc]

what is the witchcraft which makes C3I run test_cmakedeps ?

We'll need to write some docs for this :)

[SSE4]

why is it needed?

[jgsogo]

This is needed because the same CMakeLists.txt file is used from the test_cmakedeps/conanfile.py and there we are not adding the cmake generator.

IMO, it is important to reuse as much as possible the same project files.

[conan-center-bot]

All green in build 29 (18da51d56a5a625be943d4e867b949683ffa79bc):

• fmt/6.2.1@:
  All packages built successfully! (All logs)

• fmt/8.0.1@:
  All packages built successfully! (All logs)

• fmt/5.3.0@:
  All packages built successfully! (All logs)

• fmt/8.1.1@:
  All packages built successfully! (All logs)

• fmt/7.1.3@:
  All packages built successfully! (All logs)

[uilianries]

Amazing, a new step towards Conan 2.0

[jgsogo]

@prince-chrismc , can you review here again? Thanks!