Lines Matching +refs:test +refs:current +refs:scope
18 * Fixed execution of test cases as an unprivileged user, at least under
21 test cases might have previously failed for mysterious reasons when
24 * Issue #134: Fixed metadata test broken on 32-bit platforms.
26 * Issue #139: Added per-test case start/end timestamps to all reports.
36 timers to control test deadlines.
45 implements a long-standing feature request: the ability to execute test
46 cases in parallel. This is a big deal because test cases are rarely
48 large test suites, allowing faster iteration of changes during development.
50 As an example: the FreeBSD test suite as of this date contains 3285 test
51 cases. With sequential execution, a full test suite run takes around 12
57 year. The current implementation is purely subprocess-based, which works
63 * Issue #2: Implemented support to execute test cases in parallel when
64 invoking `kyua test`. Parallel execution is *only* enabled when the new
66 The default behavior is still to run tests sequentially because some test
67 suites contain test cases with side-effects that might fail when run in
69 be set to `true` on a test basis to indicate that the test must be run on
72 * Known regression: Running `kyua debug` on a TAP-based test program does
74 displayed once the test program completes. This is a shortcoming of
89 problems when running Kyua as root and executing test cases that require
94 mount points. If a test case mounts a file system and forgets to unmount
96 the test case to clean after itself. The reasons for this change are
97 simplicity and clarity: there are many more things that a test case can
99 them all, so it is better to just have the test undo anything it might
126 in the test metadata.
137 * Added support to print the details of all test cases (metadata and
142 by a test case. This is in the form of a new `required_disk_space`
143 metadata property, which can also be provided by ATF test cases as
148 particular, added more details on test program registration and their
149 metadata to `kyuafile(5)`, and added `kyua-test-isolation(7)`
150 describing the isolation features of the test execution.
153 `kyua-build-root(7)`, `kyua-results-files(7)`, `kyua-test-filters(7)`
154 and `kyua-test-isolation(7)`, into the relevant command-specific
159 from ATF's test case heads. This resolves the confusing situation
160 where test cases could only do this from their body and cleanup
163 * Issue #49: Extended `report` to support test case filters as
165 inspecting the details of a test case failure after execution.
168 a test program basis. This idiom should not be used but support for
171 * Issue #72: Added caching support to the `getcwd(3)` test in configure
176 for example, the `kyua-test` manual page with a plain name of `test`.
178 * Issue #84: Started passing test-suite configuration variables to plain
179 and TAP test programs via the environment. The name of the
187 * Issue #102: Set `TMPDIR` to the test case's work directory when running
188 the test case. If the test case happens to use the `mktemp(3)` family
190 the reuse of legacy test code), we don't want it to easily escape the
193 * Issue #103: Started being more liberal in the parsing of TAP test
206 * Issue #111: Fixed crash when defining a test program in a `Kyuafile`
207 that has not yet specified the test suite name.
225 and thus causes spurious test failures when the current user is not
226 root and the current user and `unprivileged_user` do not match.
230 * Issue #75: Change the `rewrite__expected_signal__bad_arg` test in
232 prevent triggering a core dump that made the test fail in some platforms.
242 The internal architecture of Kyua to record the results of test suite
244 the different test suite run results as different "actions" within the
246 results file inside `~/.kyua/store/` for every test suite run.
258 * Switched to results files specific to their corresponding test suite
259 run. The unified `store.db` file is now gone: `kyua test` creates a
262 corresponding test suite automatically.
291 test cases reported as `TODO` or `SKIP` as passed; handle skip plans;
293 handle test programs that report a pass but exit with a non-zero code.
303 * Issue #24: Plug the bootstrap tests back into the test suite. Fixes
304 in `kyua-testers` 0.2 to isolate test cases into their own sessions
319 test programs that comply with the Test Anything Protocol.
325 * Issue #24: Improve test case isolation by confining the tests to their
335 corresponding test case will be marked as broken instead of causing
364 * Issue #39: Added per-test-case metadata values to the HTML reports.
370 package to run the test cases. Kyua does not implement the logic to
371 invoke test cases any more, which provides for better modularity,
375 test programs right from the `Kyuafile`. This is to make plain test
395 metadata of both test programs and test cases generically, without
399 database with an old schema to the current schema.
409 * Added caching of various configure test results (particularly in those
410 tests that need to execute a test program) so that cross-compilers can
422 The goal of this first release is to adopt all the test case execution
428 The code in this package is all C as opposed to the current C++ codebase
438 * Issue #15: Added automatic stacktrace gathering of crashing test cases.
441 * Issue #32: Added the `--build-root` option to the debug, list and test
442 commands. This allows executing test programs from a different
451 every test case.
477 commands that rely on a current project and those commands that rely
505 * Made the `test` command record the results of the executed test
506 cases into a SQLite database. As a side effect, `test` now supports a
510 test results stored in the database. The interface of this command is
516 * Issue #28: Added support for the `require.memory` test case property
531 * Enabled logging to stderr for our own test programs. This makes it
533 failing test.
541 The biggest change in this release is the ability for Kyua to run test
543 that, now, a Kyua test suite can include not only ATF-based test
544 programs, but also "legacy" (aka plain) test programs that do not use
547 Kyua test suite.
558 * Generalized the run-time engine to support executing test programs
562 * Added support to the engine to run `plain` test programs: i.e. test
565 test programs into a test suite, and also to demonstrate that the
566 run-time engine is generic enough to support different test
570 the execution of a specific test case and to poke into the behavior of
572 stdout and stderr of the command in real time (which the `test`
576 inspect the current configuration variables after evaluation, without
580 was used to set the value of test-suite-sepecific variables, but it
582 `test_suites.<test-suite-name>.<variable> = <value>`. (Issue #11.)
609 The scope of this release is to provide functional replacement for the
611 can reliably run the NetBSD 5.99.53 test suite delivering the same
616 debugging failing test programs other than running them by hand. These
621 The test suite for `kyua-cli` is quite comprehensive, but some bugs may