test_package is different from the library unit or integration tests, which should be more comprehensive. These tests are “package” tests, and validate that the package is properly created, and that package from the previous section, we can just use it for our test. Go to your package folder and run the tests again, now saying that we don’t want to build the sources again, we just want to check if we can download COMMAND example) endif() This package recipe will not retrieve the mytest_framework nor build the tests, for normal installation: $ conan install . But if the following profile is defined: Listing 2:

test_package is different from the library unit or integration tests, which should be more comprehensive. These tests are “package” tests, and validate that the package is properly created, and that package from the previous section, we can just use it for our test. Go to your package folder and run the tests again, now saying that we don’t want to build the sources again, we just want to check if we can download COMMAND example) endif() This package recipe will not retrieve the mytest_framework nor build the tests, for normal installation: $ conan install . But if the following profile is defined: Listing 2:

Note: The test_package differs from the library unit or integration tests, which should be more comprehensive. These tests are “package” tests, and validate that the package is properly created, and that the from the previous section, we can just use it for our test. Go to your package folder and run the tests again, now saying that we don’t want to build the sources again, we just want to check if we can download COMMAND example) endif() This package recipe will not retrieve the mytest_framework nor build the tests, for normal installation: $ conan install . But if the following profile is defined: Listing 2:

test_package is different from the library unit or integration tests, which should be more comprehensive. These tests are “package” tests, and validate that the package is properly created, and that package from the previous section, we can just use it for our test. Go to your package folder and run the tests again, now saying that we don’t want to build the sources again, we just want to check if we can download COMMAND example) endif() This package recipe will not retrieve the mytest_framework nor build the tests, for normal installation: $ conan install . But if the following profile is defined: Listing 2:

test_package is different from the library unit or integration tests, which should be more comprehensive. These tests are “package” tests, and validate that the package is properly created, and that package from the previous section, we can just use it for our test. Go to your package folder and run the tests again, now saying that we don’t want to build the sources again, we just want to check if we can download COMMAND example) endif() This package recipe will not retrieve the mytest_framework nor build the tests, for normal installation: $ conan install . But if the following profile is defined: Listing 2:

packages’ binary compatibility. • Use the build() method to customize the build process and launch the tests for the library you are packaging. • Select which files will be included in the Conan package using important bits are: • test_package folder is different from unit or integration tests. These tests are “package” tests, and validate that the package is properly created and that the package consumers will modify that method and explain how you can use it to do things like: • Building and running tests • Conditional patching of the source code • Select the build system you want to use conditionally

Note: The test_package differs from the library unit or integration tests, which should be more comprehensive. These tests are “package” tests, and validate that the package is properly created, and that the from the previous section, we can just use it for our test. Go to your package folder and run the tests again, now saying that we don’t want to build the sources again, we just want to check if we can download COMMAND example) endif() This package recipe will not retrieve the mytest_framework nor build the tests, for normal installation: $ conan install . But if the following profile is defined: Listing 2:

Note: The test_package differs from the library unit or integration tests, which should be more comprehensive. These tests are “package” tests, and validate that the package is properly created, and that the from the previous section, we can just use it for our test. Go to your package folder and run the tests again, now saying that we don’t want to build the sources again, we just want to check if we can download COMMAND example) endif() This package recipe will not retrieve the mytest_framework nor build the tests, for normal installation: $ conan install . But if the following profile is defined: Listing 2:

Helper classes␣ ˓→are available for several build systems ... self.run("bin/unittests") # Run unit tests␣ ˓→compiled earlier in the build() method def package(self): # Responsible for␣ ˓→capturing build important bits are: • test_package folder is different from unit or integration tests. These tests are “package” tests, and validate that the package is properly created, and that the package consumers from the previous section, we can just use it for our test. Go to your package folder and run the tests again, now saying that we don’t want to build the sources again. We just want to check if we can download

Note: The test_package differs from the library unit or integration tests, which should be more comprehensive. These tests are “package” tests, and validate that the package is properly created, and that the from the previous section, we can just use it for our test. Go to your package folder and run the tests again, now saying that we don’t want to build the sources again, we just want to check if we can download COMMAND example) endif() This package recipe will not retrieve the mytest_framework nor build the tests, for normal installation: $ conan install . But if the following profile is defined: Listing 2: