kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/kyua/Makefile

55 lines
1.4 KiB
Makefile
Raw Normal View History

Recursive revision bump after textproc/icu update
2020-04-12 10:27:48 +02:00
# $NetBSD: Makefile,v 1.21 2020/04/12 08:28:32 adam Exp $
Initial import of kyua-cli, version 0.1: Kyua (pronounced Q.A.) is a testing framework for both developers and users. Kyua is different from most other testing frameworks in that it puts the end user experience before anything else. There are multiple reasons for users to run the tests themselves, and Kyua ensures that they can do so in the most convenient way. At the moment, Kyua is focused on implementing a solid foundation and a powerful command-line tool to run tests implemented with the Automated Testing Framework (ATF). Later on, Kyua will also provide a set of language bindings (C, C++ and shell, at the least) to ease the implementation of test cases in a variety of programming languages. In effect, Kyua is intended to be a replacement for ATF.
2011-07-08 11:49:11 +02:00
Update devel/kyua to 0.13: **Released on August 26th, 2016.** * Fixed execution of test cases as an unprivileged user, at least under NetBSD 7.0. Kyua-level failures were probably a regression introduced in Kyua 0.12, but the underlying may have existed for much longer: test cases might have previously failed for mysterious reasons when running under an unprivileged user. * Issue #134: Fixed metadata test broken on 32-bit platforms. * Issue #139: Added per-test case start/end timestamps to all reports. * Issue #156: Fixed crashes due to the invalid handling of cleanup routine data and triggered by the reuse of PIDs in long-running Kyua instances. * Issue #159: Fixed TAP parser to ignore case while matching `TODO` and `SKIP` directives, and to also recognize `Skipped`. * Fixed potential crash due to a race condition in the unprogramming of timers to control test deadlines.
2016-08-26 12:41:56 +02:00
DISTNAME= kyua-0.13
Recursive revision bump after textproc/icu update
2020-04-12 10:27:48 +02:00
PKGREVISION= 9
Initial import of kyua-cli, version 0.1: Kyua (pronounced Q.A.) is a testing framework for both developers and users. Kyua is different from most other testing frameworks in that it puts the end user experience before anything else. There are multiple reasons for users to run the tests themselves, and Kyua ensures that they can do so in the most convenient way. At the moment, Kyua is focused on implementing a solid foundation and a powerful command-line tool to run tests implemented with the Automated Testing Framework (ATF). Later on, Kyua will also provide a set of language bindings (C, C++ and shell, at the least) to ease the implementation of test cases in a variety of programming languages. In effect, Kyua is intended to be a replacement for ATF.
2011-07-08 11:49:11 +02:00
CATEGORIES= devel
Update kyua to 0.11 Changes in version 0.11 ======================= Released on October 23rd, 2014. * Added support to print the details of all test cases (metadata and their output) to 'report'. This is via a new '--verbose' flag which replaces the previous '--show-context'. * Added support to specify the amount of physical disk space required by a test case. This is in the form of a new "required_disk_space" metadata property, which can also be provided by ATF test cases as "require.diskspace". * Assimilated the contents of all the kyua-*-tester(1) and kyua-*-interface(7) manual pages into more relevant places. In particular, added more details on test program registration and their metadata to kyuafile(5), and added kyua-test-isolation(7) describing the isolation features of the test execution. * Assimilated the contents of all auxiliary manual pages, including kyua-build-root(7), kyua-results-files(7), kyua-test-filters(7) and kyua-test-isolation(7), into the relevant command-specific manual pages. This is for easier discoverability of relevant information when reading how specific Kyua commands work. * Issue 30: Plumbed through support to query configuration variables from ATF's test case heads. This resolves the confusing situation where test cases could only do this from their body and cleanup routines. * Issue 49: Extended 'report' to support test case filters as command-line arguments. Combined with '--verbose', this allows inspecting the details of a test case failure after execution. * Issue 55: Deprecated support for specifying test_suite overrides on a test program basis. This idiom should not be used but support for it remains in place. * Issue 72: Added caching support to the getcwd(3) test in configure so that the result can be overriden for cross-compilation purposes. * Issue 83: Changed manual page headings to include a "kyua" prefix in their name. This prevents some possible confusion when displaying, for example, the "kyua-test" manual page with a plain name of "test". * Issue 84: Started passing test-suite configuration variables to plain and TAP test programs via the environment. The name of the environment variables set this way is prefixed by TEST_ENV_, so a configuration variable of the form 'test_suites.some_name.allow_unsafe_ops=yes' in kyua.conf becomes 'TEST_ENV_allow_unsafe_ops=YES' in the environment. * Issue 97 and 116: Fixed the build on Illumos. * Issue 102: Set TMPDIR to the test case's work directory when running the test case. If the test case happens to use the mktemp(3) family of functions (due to misunderstandings on how Kyua works or due to the reuse of legacy test code), we don't want it to easily escape the automanaged work directory. * Issue 103: Started being more liberal in the parsing of TAP test results by treating the number in 'ok' and 'not ok' lines as optional. * Issue 105: Started using tmpfs instead of md as a temporary file system for tests in FreeBSD so that we do not leak md(4) devices. * Issue 109: Changed the privilege dropping code to start properly dropping group privileges when unprivileged_user is set. Also fixes testers/run_test:fork_wait__unprivileged_group. * Issue 110: Changed 'help' to display version information and clarified the purpose of the 'about' command in its documentation. * Issue 111: Fixed crash when defining a test program in a Kyuafile that has not yet specified the test suite name. * Issue 114: Improved the kyuafile(5) manual page by clarifying the restrictions of the include() directive and by adding abundant examples.
2015-10-01 17:17:32 +02:00
MASTER_SITES= ${MASTER_SITE_GITHUB:=jmmv/kyua/releases/download/${DISTNAME}/}
Initial import of kyua-cli, version 0.1: Kyua (pronounced Q.A.) is a testing framework for both developers and users. Kyua is different from most other testing frameworks in that it puts the end user experience before anything else. There are multiple reasons for users to run the tests themselves, and Kyua ensures that they can do so in the most convenient way. At the moment, Kyua is focused on implementing a solid foundation and a powerful command-line tool to run tests implemented with the Automated Testing Framework (ATF). Later on, Kyua will also provide a set of language bindings (C, C++ and shell, at the least) to ease the implementation of test cases in a variety of programming languages. In effect, Kyua is intended to be a replacement for ATF.
2011-07-08 11:49:11 +02:00
MAINTAINER= jmmv@NetBSD.org
Update kyua-cli to 0.9: Experimental version released on August 8th, 2014. Major changes: The internal architecture of Kyua to record the results of test suite runs has completely changed in this release. Kyua no longer stores all the different test suite run results as different "actions" within the single store.db database. Instead, Kyua now generates a separate results file inside ~/.kyua/store/ for every test suite run. Due to the complexity involved in the migration process and the little need for it, this is probably going to be the only release where the 'db-migrate' command is able to convert an old store.db file to the new scheme. Changes in more detail: * Added the 'report-junit' command to generate JUnit XML result files. The output has been verified to work within Jenkins. * Switched to results files specific to their corresponding test suite run. The unified store.db file is now gone: 'kyua test' creates a new results file for every invocation under ~/.kyua/store/ and the 'kyua report*' commands are able to locate the latest file for a corresponding test suite automatically. * The 'db-migrate' command takes an old store.db file and generates one results file for every previously-recorded action, later deleting the store.db file. * The '--action' flag has been removed from all commands that accepted it. This has been superseded by the tests results files. * The '--store' flag that many commands took has been renamed to '--results-file' in line with the semantical changes. * The 'db-exec' command no longer creates an empty database when none is found. This command is now intended to run only over existing files.
2014-08-08 16:30:24 +02:00
HOMEPAGE= https://github.com/jmmv/kyua/
Import kyua-0.10. This is a "new" import that unifies all the previous Kyua subpackages (kyua-atf-compat, kyua-cli and kyua-testers) under a single package. The change has been made upstream mainly for simplicity reasons; the old modular scheme was unnecessary. Given that this new import should be really considered to be an update, the following are the changes since kyua-cli-0.9 and kyua-testers-0.3, both released last week: Experimental version released on August 14th, 2014. * Merged 'kyua-cli' and 'kyua-testers' into a single 'kyua' package. * Dropped the 'kyua-atf-compat' package. * Issue 100: Do not try to drop privileges to unprivileged_user when we are already running as an unprivileged user. Doing so is not possible and thus causes spurious test failures when the current user is not root and the current user and unprivileged_user do not match. * Issue 79: Mention kyua.conf(5) in the "see also" section of kyua(1). * Issue 75: Change the rewrite__expected_signal__bad_arg test in testers/atf_result_test to use a different signal value. This is to prevent triggering a core dump that made the test fail in some platforms.
2014-08-14 16:14:52 +02:00
COMMENT= Testing framework for infrastructure software
These packages are all modified-bsd, not 2-clause-bsd.
2012-07-19 20:30:18 +02:00
LICENSE= modified-bsd
Initial import of kyua-cli, version 0.1: Kyua (pronounced Q.A.) is a testing framework for both developers and users. Kyua is different from most other testing frameworks in that it puts the end user experience before anything else. There are multiple reasons for users to run the tests themselves, and Kyua ensures that they can do so in the most convenient way. At the moment, Kyua is focused on implementing a solid foundation and a powerful command-line tool to run tests implemented with the Automated Testing Framework (ATF). Later on, Kyua will also provide a set of language bindings (C, C++ and shell, at the least) to ease the implementation of test cases in a variety of programming languages. In effect, Kyua is intended to be a replacement for ATF.
2011-07-08 11:49:11 +02:00
Import kyua-0.10. This is a "new" import that unifies all the previous Kyua subpackages (kyua-atf-compat, kyua-cli and kyua-testers) under a single package. The change has been made upstream mainly for simplicity reasons; the old modular scheme was unnecessary. Given that this new import should be really considered to be an update, the following are the changes since kyua-cli-0.9 and kyua-testers-0.3, both released last week: Experimental version released on August 14th, 2014. * Merged 'kyua-cli' and 'kyua-testers' into a single 'kyua' package. * Dropped the 'kyua-atf-compat' package. * Issue 100: Do not try to drop privileges to unprivileged_user when we are already running as an unprivileged user. Doing so is not possible and thus causes spurious test failures when the current user is not root and the current user and unprivileged_user do not match. * Issue 79: Mention kyua.conf(5) in the "see also" section of kyua(1). * Issue 75: Change the rewrite__expected_signal__bad_arg test in testers/atf_result_test to use a different signal value. This is to prevent triggering a core dump that made the test fail in some platforms.
2014-08-14 16:14:52 +02:00
CONFLICTS= kyua-atf-compat-[0-9]* kyua-cli-[0-9]* kyua-testers-[0-9]*
PKG_DESTDIR_SUPPORT= user-destdir
Initial import of kyua-cli, version 0.1: Kyua (pronounced Q.A.) is a testing framework for both developers and users. Kyua is different from most other testing frameworks in that it puts the end user experience before anything else. There are multiple reasons for users to run the tests themselves, and Kyua ensures that they can do so in the most convenient way. At the moment, Kyua is focused on implementing a solid foundation and a powerful command-line tool to run tests implemented with the Automated Testing Framework (ATF). Later on, Kyua will also provide a set of language bindings (C, C++ and shell, at the least) to ease the implementation of test cases in a variety of programming languages. In effect, Kyua is intended to be a replacement for ATF.
2011-07-08 11:49:11 +02:00
GNU_CONFIGURE= yes
Import kyua-0.10. This is a "new" import that unifies all the previous Kyua subpackages (kyua-atf-compat, kyua-cli and kyua-testers) under a single package. The change has been made upstream mainly for simplicity reasons; the old modular scheme was unnecessary. Given that this new import should be really considered to be an update, the following are the changes since kyua-cli-0.9 and kyua-testers-0.3, both released last week: Experimental version released on August 14th, 2014. * Merged 'kyua-cli' and 'kyua-testers' into a single 'kyua' package. * Dropped the 'kyua-atf-compat' package. * Issue 100: Do not try to drop privileges to unprivileged_user when we are already running as an unprivileged user. Doing so is not possible and thus causes spurious test failures when the current user is not root and the current user and unprivileged_user do not match. * Issue 79: Mention kyua.conf(5) in the "see also" section of kyua(1). * Issue 75: Change the rewrite__expected_signal__bad_arg test in testers/atf_result_test to use a different signal value. This is to prevent triggering a core dump that made the test fail in some platforms.
2014-08-14 16:14:52 +02:00
USE_LANGUAGES= c c++
Update to 0.6: Experimental version released on February 22nd, 2013. * Issue 36: Changed 'kyua help' to not fail when the configuration file is bogus. Help should always work. * Issue 37: Simplified the syntax() calls in configuration and Kyuafile files to only specify the requested version instead of also the format name. The format name is implied by the file being loaded, so there is no use in the caller having to specify it. The version number of these file formats has been bumped to 2. * Issue 39: Added per-test-case metadata values to the HTML reports. * Issue 40: Rewrote the documentation as manual pages and removed the previous GNU Info document. * Issue 47: Started using the independent testers in the kyua-testers package to run the test cases. Kyua does not implement the logic to invoke test cases any more, which provides for better modularity, extensibility and robustness. * Issue 57: Added support to specify arbitrary metadata properties for test programs right from the Kyuafile. This is to make plain test programs more versatile, by allowing them to specify any of the requirements (allowed architectures, required files, etc.) supported by Kyua. * Reduced automatic screen line wrapping of messages to the 'help' command and the output of tables by 'db-exec'. Wrapping any other messages (specially anything going to stderr) was very annoying because it prevented natural copy/pasting of text. * Increased the granularity of the error codes returned by kyua(1) to denote different error conditions. This avoids the overload of '1' to indicate both "expected" errors from specific subcommands and unexpected errors caused by the internals of the code. The manual now correctly explain how the exit codes behave on a command basis. * Optimized the database schema to make report generation almost instantaneous. * Bumped the database schema to 2. The database now records the metadata of both test programs and test cases generically, without knowledge of their interface. * Added the 'db-migrate' command to provide a mechanism to upgrade a database with an old schema to the current schema. * Removed the GDB build-time configuration variable. This is now part of the kyua-testers package. * Rewrote the Kyuafile parsing code in C++, which results in a much simpler implementation. As a side-effect, this gets rid of the external Lua files required by 'kyua', which in turn make the tool self-contained. * Added caching of various configure test results (particularly in those tests that need to execute a test program) so that cross-compilers can predefine the results of the tests without having to run the executables.
2013-02-23 04:37:40 +01:00
USE_TOOLS= pkg-config
Initial import of kyua-cli, version 0.1: Kyua (pronounced Q.A.) is a testing framework for both developers and users. Kyua is different from most other testing frameworks in that it puts the end user experience before anything else. There are multiple reasons for users to run the tests themselves, and Kyua ensures that they can do so in the most convenient way. At the moment, Kyua is focused on implementing a solid foundation and a powerful command-line tool to run tests implemented with the Automated Testing Framework (ATF). Later on, Kyua will also provide a set of language bindings (C, C++ and shell, at the least) to ease the implementation of test cases in a variety of programming languages. In effect, Kyua is intended to be a replacement for ATF.
2011-07-08 11:49:11 +02:00
Import kyua-0.10. This is a "new" import that unifies all the previous Kyua subpackages (kyua-atf-compat, kyua-cli and kyua-testers) under a single package. The change has been made upstream mainly for simplicity reasons; the old modular scheme was unnecessary. Given that this new import should be really considered to be an update, the following are the changes since kyua-cli-0.9 and kyua-testers-0.3, both released last week: Experimental version released on August 14th, 2014. * Merged 'kyua-cli' and 'kyua-testers' into a single 'kyua' package. * Dropped the 'kyua-atf-compat' package. * Issue 100: Do not try to drop privileges to unprivileged_user when we are already running as an unprivileged user. Doing so is not possible and thus causes spurious test failures when the current user is not root and the current user and unprivileged_user do not match. * Issue 79: Mention kyua.conf(5) in the "see also" section of kyua(1). * Issue 75: Change the rewrite__expected_signal__bad_arg test in testers/atf_result_test to use a different signal value. This is to prevent triggering a core dump that made the test fail in some platforms.
2014-08-14 16:14:52 +02:00
PKG_OPTIONS_VAR= PKG_OPTIONS.kyua
Update to 0.4. Other than the upgrade itself, this also adds a new 'tests' option to the package to indicate whether the Kyua-specific tests should be built or not. I do not recommend disabling their build, but not specifiying the 'tests' option cuts down the build time significantly. The major changes since 0.3 are: * Added the 'report-html' command to generate HTML reports of the execution of any recorded action. * Changed the '--output' flag of the 'report' command to only take a path to the target file, not its format. Different formats are better supported by implementing different subcommands, as the options they may receive will vary from format to format. * Added a '--with-atf' flag to the configure script to control whether the ATF tests get built or not. May be useful for packaging systems that do not have ATF in them yet. Disabling ATF also cuts down the build time of Kyua significantly, but with the obvious drawbacks. * Grouped 'kyua' subcommands by topic both in the output of 'help' and in the documentation. In general, the user needs to be aware of commands that rely on a current project and those commands that rely purely on the database to generate reports. * Made 'help' print the descriptions of options and commands properly tabulated. * Changed most informational messages to automatically wrap on screen boundaries. * Rewrote the configuration file parsing module for extensibility. This will allow future versions of Kyua to provide additional user-facing options in the configuration file. No syntax changes have been made, so existing configuration files (version 1) will continue to be parsed without problems. There is one little exception though: all variables under the top-level 'test_suites' tree must be declared as strings. Similarly, the '-v' and '--variable' flags to the command line must now carry a 'test_suites.' prefix when referencing any variables under such tree.
2012-06-07 03:13:58 +02:00
PKG_SUPPORTED_OPTIONS= tests
PKG_SUGGESTED_OPTIONS= tests
Initial import of kyua-cli, version 0.1: Kyua (pronounced Q.A.) is a testing framework for both developers and users. Kyua is different from most other testing frameworks in that it puts the end user experience before anything else. There are multiple reasons for users to run the tests themselves, and Kyua ensures that they can do so in the most convenient way. At the moment, Kyua is focused on implementing a solid foundation and a powerful command-line tool to run tests implemented with the Automated Testing Framework (ATF). Later on, Kyua will also provide a set of language bindings (C, C++ and shell, at the least) to ease the implementation of test cases in a variety of programming languages. In effect, Kyua is intended to be a replacement for ATF.
2011-07-08 11:49:11 +02:00
CONFIGURE_ARGS+= KYUA_CONFSUBDIR=
CONFIGURE_ARGS+= --sysconfdir=${PKG_SYSCONFDIR}
CONFIGURE_ARGS+= --without-doxygen
PKG_SYSCONFSUBDIR= kyua
Update to 0.4. Other than the upgrade itself, this also adds a new 'tests' option to the package to indicate whether the Kyua-specific tests should be built or not. I do not recommend disabling their build, but not specifiying the 'tests' option cuts down the build time significantly. The major changes since 0.3 are: * Added the 'report-html' command to generate HTML reports of the execution of any recorded action. * Changed the '--output' flag of the 'report' command to only take a path to the target file, not its format. Different formats are better supported by implementing different subcommands, as the options they may receive will vary from format to format. * Added a '--with-atf' flag to the configure script to control whether the ATF tests get built or not. May be useful for packaging systems that do not have ATF in them yet. Disabling ATF also cuts down the build time of Kyua significantly, but with the obvious drawbacks. * Grouped 'kyua' subcommands by topic both in the output of 'help' and in the documentation. In general, the user needs to be aware of commands that rely on a current project and those commands that rely purely on the database to generate reports. * Made 'help' print the descriptions of options and commands properly tabulated. * Changed most informational messages to automatically wrap on screen boundaries. * Rewrote the configuration file parsing module for extensibility. This will allow future versions of Kyua to provide additional user-facing options in the configuration file. No syntax changes have been made, so existing configuration files (version 1) will continue to be parsed without problems. There is one little exception though: all variables under the top-level 'test_suites' tree must be declared as strings. Similarly, the '-v' and '--variable' flags to the command line must now carry a 'test_suites.' prefix when referencing any variables under such tree.
2012-06-07 03:13:58 +02:00
.include "../../mk/bsd.options.mk"
Use standard way to test for options.
2016-12-31 10:39:31 +01:00
.if !empty(PKG_OPTIONS:Mtests)
Depend on atf 0.20 (not atf-libs) and bump PKGREVISION.
2014-02-08 16:59:30 +01:00
. include "../../devel/atf/buildlink3.mk"
Update to 0.4. Other than the upgrade itself, this also adds a new 'tests' option to the package to indicate whether the Kyua-specific tests should be built or not. I do not recommend disabling their build, but not specifiying the 'tests' option cuts down the build time significantly. The major changes since 0.3 are: * Added the 'report-html' command to generate HTML reports of the execution of any recorded action. * Changed the '--output' flag of the 'report' command to only take a path to the target file, not its format. Different formats are better supported by implementing different subcommands, as the options they may receive will vary from format to format. * Added a '--with-atf' flag to the configure script to control whether the ATF tests get built or not. May be useful for packaging systems that do not have ATF in them yet. Disabling ATF also cuts down the build time of Kyua significantly, but with the obvious drawbacks. * Grouped 'kyua' subcommands by topic both in the output of 'help' and in the documentation. In general, the user needs to be aware of commands that rely on a current project and those commands that rely purely on the database to generate reports. * Made 'help' print the descriptions of options and commands properly tabulated. * Changed most informational messages to automatically wrap on screen boundaries. * Rewrote the configuration file parsing module for extensibility. This will allow future versions of Kyua to provide additional user-facing options in the configuration file. No syntax changes have been made, so existing configuration files (version 1) will continue to be parsed without problems. There is one little exception though: all variables under the top-level 'test_suites' tree must be declared as strings. Similarly, the '-v' and '--variable' flags to the command line must now carry a 'test_suites.' prefix when referencing any variables under such tree.
2012-06-07 03:13:58 +02:00
CONFIGURE_ARGS+= --with-atf
PLIST_SUBST+= TESTS=
Fix "make install" in devel/kyua without "tests" package option. * Add a space after the "@comment" PLIST keyword inserted in the case where "tests" option is disabled. * Only create the "${PREFIX}/tests" directory and install the Kyuafile there if the "tests" option is enabled.
2017-06-08 00:57:02 +02:00
post-install: post-install-tests
Update to 0.4. Other than the upgrade itself, this also adds a new 'tests' option to the package to indicate whether the Kyua-specific tests should be built or not. I do not recommend disabling their build, but not specifiying the 'tests' option cuts down the build time significantly. The major changes since 0.3 are: * Added the 'report-html' command to generate HTML reports of the execution of any recorded action. * Changed the '--output' flag of the 'report' command to only take a path to the target file, not its format. Different formats are better supported by implementing different subcommands, as the options they may receive will vary from format to format. * Added a '--with-atf' flag to the configure script to control whether the ATF tests get built or not. May be useful for packaging systems that do not have ATF in them yet. Disabling ATF also cuts down the build time of Kyua significantly, but with the obvious drawbacks. * Grouped 'kyua' subcommands by topic both in the output of 'help' and in the documentation. In general, the user needs to be aware of commands that rely on a current project and those commands that rely purely on the database to generate reports. * Made 'help' print the descriptions of options and commands properly tabulated. * Changed most informational messages to automatically wrap on screen boundaries. * Rewrote the configuration file parsing module for extensibility. This will allow future versions of Kyua to provide additional user-facing options in the configuration file. No syntax changes have been made, so existing configuration files (version 1) will continue to be parsed without problems. There is one little exception though: all variables under the top-level 'test_suites' tree must be declared as strings. Similarly, the '-v' and '--variable' flags to the command line must now carry a 'test_suites.' prefix when referencing any variables under such tree.
2012-06-07 03:13:58 +02:00
.else
CONFIGURE_ARGS+= --without-atf
Fix "make install" in devel/kyua without "tests" package option. * Add a space after the "@comment" PLIST keyword inserted in the case where "tests" option is disabled. * Only create the "${PREFIX}/tests" directory and install the Kyuafile there if the "tests" option is enabled.
2017-06-08 00:57:02 +02:00
PLIST_SUBST+= TESTS="@comment "
Update to 0.4. Other than the upgrade itself, this also adds a new 'tests' option to the package to indicate whether the Kyua-specific tests should be built or not. I do not recommend disabling their build, but not specifiying the 'tests' option cuts down the build time significantly. The major changes since 0.3 are: * Added the 'report-html' command to generate HTML reports of the execution of any recorded action. * Changed the '--output' flag of the 'report' command to only take a path to the target file, not its format. Different formats are better supported by implementing different subcommands, as the options they may receive will vary from format to format. * Added a '--with-atf' flag to the configure script to control whether the ATF tests get built or not. May be useful for packaging systems that do not have ATF in them yet. Disabling ATF also cuts down the build time of Kyua significantly, but with the obvious drawbacks. * Grouped 'kyua' subcommands by topic both in the output of 'help' and in the documentation. In general, the user needs to be aware of commands that rely on a current project and those commands that rely purely on the database to generate reports. * Made 'help' print the descriptions of options and commands properly tabulated. * Changed most informational messages to automatically wrap on screen boundaries. * Rewrote the configuration file parsing module for extensibility. This will allow future versions of Kyua to provide additional user-facing options in the configuration file. No syntax changes have been made, so existing configuration files (version 1) will continue to be parsed without problems. There is one little exception though: all variables under the top-level 'test_suites' tree must be declared as strings. Similarly, the '-v' and '--variable' flags to the command line must now carry a 'test_suites.' prefix when referencing any variables under such tree.
2012-06-07 03:13:58 +02:00
.endif
Import kyua-0.10. This is a "new" import that unifies all the previous Kyua subpackages (kyua-atf-compat, kyua-cli and kyua-testers) under a single package. The change has been made upstream mainly for simplicity reasons; the old modular scheme was unnecessary. Given that this new import should be really considered to be an update, the following are the changes since kyua-cli-0.9 and kyua-testers-0.3, both released last week: Experimental version released on August 14th, 2014. * Merged 'kyua-cli' and 'kyua-testers' into a single 'kyua' package. * Dropped the 'kyua-atf-compat' package. * Issue 100: Do not try to drop privileges to unprivileged_user when we are already running as an unprivileged user. Doing so is not possible and thus causes spurious test failures when the current user is not root and the current user and unprivileged_user do not match. * Issue 79: Mention kyua.conf(5) in the "see also" section of kyua(1). * Issue 75: Change the rewrite__expected_signal__bad_arg test in testers/atf_result_test to use a different signal value. This is to prevent triggering a core dump that made the test fail in some platforms.
2014-08-14 16:14:52 +02:00
PRINT_PLIST_AWK+= { sub("^tests/", "$${TESTS}tests/"); }
Update to 0.4. Other than the upgrade itself, this also adds a new 'tests' option to the package to indicate whether the Kyua-specific tests should be built or not. I do not recommend disabling their build, but not specifiying the 'tests' option cuts down the build time significantly. The major changes since 0.3 are: * Added the 'report-html' command to generate HTML reports of the execution of any recorded action. * Changed the '--output' flag of the 'report' command to only take a path to the target file, not its format. Different formats are better supported by implementing different subcommands, as the options they may receive will vary from format to format. * Added a '--with-atf' flag to the configure script to control whether the ATF tests get built or not. May be useful for packaging systems that do not have ATF in them yet. Disabling ATF also cuts down the build time of Kyua significantly, but with the obvious drawbacks. * Grouped 'kyua' subcommands by topic both in the output of 'help' and in the documentation. In general, the user needs to be aware of commands that rely on a current project and those commands that rely purely on the database to generate reports. * Made 'help' print the descriptions of options and commands properly tabulated. * Changed most informational messages to automatically wrap on screen boundaries. * Rewrote the configuration file parsing module for extensibility. This will allow future versions of Kyua to provide additional user-facing options in the configuration file. No syntax changes have been made, so existing configuration files (version 1) will continue to be parsed without problems. There is one little exception though: all variables under the top-level 'test_suites' tree must be declared as strings. Similarly, the '-v' and '--variable' flags to the command line must now carry a 'test_suites.' prefix when referencing any variables under such tree.
2012-06-07 03:13:58 +02:00
Fix "make install" in devel/kyua without "tests" package option. * Add a space after the "@comment" PLIST keyword inserted in the case where "tests" option is disabled. * Only create the "${PREFIX}/tests" directory and install the Kyuafile there if the "tests" option is enabled.
2017-06-08 00:57:02 +02:00
.PHONY: post-install-tests
post-install-tests:
Update to 0.4. Other than the upgrade itself, this also adds a new 'tests' option to the package to indicate whether the Kyua-specific tests should be built or not. I do not recommend disabling their build, but not specifiying the 'tests' option cuts down the build time significantly. The major changes since 0.3 are: * Added the 'report-html' command to generate HTML reports of the execution of any recorded action. * Changed the '--output' flag of the 'report' command to only take a path to the target file, not its format. Different formats are better supported by implementing different subcommands, as the options they may receive will vary from format to format. * Added a '--with-atf' flag to the configure script to control whether the ATF tests get built or not. May be useful for packaging systems that do not have ATF in them yet. Disabling ATF also cuts down the build time of Kyua significantly, but with the obvious drawbacks. * Grouped 'kyua' subcommands by topic both in the output of 'help' and in the documentation. In general, the user needs to be aware of commands that rely on a current project and those commands that rely purely on the database to generate reports. * Made 'help' print the descriptions of options and commands properly tabulated. * Changed most informational messages to automatically wrap on screen boundaries. * Rewrote the configuration file parsing module for extensibility. This will allow future versions of Kyua to provide additional user-facing options in the configuration file. No syntax changes have been made, so existing configuration files (version 1) will continue to be parsed without problems. There is one little exception though: all variables under the top-level 'test_suites' tree must be declared as strings. Similarly, the '-v' and '--variable' flags to the command line must now carry a 'test_suites.' prefix when referencing any variables under such tree.
2012-06-07 03:13:58 +02:00
${INSTALL_DATA_DIR} ${DESTDIR}${PREFIX}/tests
Initial import of kyua-cli, version 0.1: Kyua (pronounced Q.A.) is a testing framework for both developers and users. Kyua is different from most other testing frameworks in that it puts the end user experience before anything else. There are multiple reasons for users to run the tests themselves, and Kyua ensures that they can do so in the most convenient way. At the moment, Kyua is focused on implementing a solid foundation and a powerful command-line tool to run tests implemented with the Automated Testing Framework (ATF). Later on, Kyua will also provide a set of language bindings (C, C++ and shell, at the least) to ease the implementation of test cases in a variety of programming languages. In effect, Kyua is intended to be a replacement for ATF.
2011-07-08 11:49:11 +02:00
${INSTALL_DATA} ${WRKSRC}/examples/Kyuafile.top \
${DESTDIR}${PREFIX}/tests/Kyuafile
Update kyua-cli to 0.3: Experimental version released on February 24th, 2012. * Made the 'test' command record the results of the executed test cases into a SQLite database. As a side effect, 'test' now supports a '--store' option to indicate where the database lives. * Added the 'report' command to generate plain-text reports of the test results stored in the database. The interface of this command is certainly subject to change at this point. * Added the 'db-exec' command to directly interact with the store database. * Issue 28: Added support for the 'require.memory' test case property introduced in ATF 0.15. * Renamed the user-specific configuration file from ~/.kyuarc to ~/.kyua/kyua.conf for consistency with other files stored in the ~/.kyua/ subdirectory. * Switched to use Lutok instead of our own wrappers over the Lua C library. Lutok is just what used to be our own utils::lua module, but is now distributed separately. * Removed the 'Atffile's from the source tree. Kyua is stable enough to generate trustworthy reports, and we do not want to give the impression that atf-run / atf-report are still supported. * Enabled logging to stderr for our own test programs. This makes it slightly easier to debug problems in our own code when we get a failing test.
2012-02-24 22:07:41 +01:00
.include "../../databases/sqlite3/buildlink3.mk"
.include "../../devel/lutok/buildlink3.mk"
Initial import of kyua-cli, version 0.1: Kyua (pronounced Q.A.) is a testing framework for both developers and users. Kyua is different from most other testing frameworks in that it puts the end user experience before anything else. There are multiple reasons for users to run the tests themselves, and Kyua ensures that they can do so in the most convenient way. At the moment, Kyua is focused on implementing a solid foundation and a powerful command-line tool to run tests implemented with the Automated Testing Framework (ATF). Later on, Kyua will also provide a set of language bindings (C, C++ and shell, at the least) to ease the implementation of test cases in a variety of programming languages. In effect, Kyua is intended to be a replacement for ATF.
2011-07-08 11:49:11 +02:00
.include "../../lang/lua/buildlink3.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink