Scriptharness 0.2.0 Release Notes¶
| date: | 2015/06/21 |
|---|
Highlights¶
This release adds Command and run(), ParsedCommand and parse(), and Output, get_output(), and get_text_output() with output_timeout and max_timeout support. ParsedCommand supports context lines (see OutputBuffer and context lines).
It also adds ConfigTemplates, which allow for specifying what a well-formed configuration looks like for a script, as well as config validation.
What’s New¶
More ways to enable and disable actions. Now, in addition to
--actions, there’s--add-actions,--skip-actions, and--action-groupto change the set of default actions to run. (See Enabling and Disabling Actions.)Added Command object with cross-platform output_timeout and max_timeout support, with a run() wrapper function for easier use. This is for running external tools with timeouts. (See Command and run().)
- Added ScriptHarnessTimeout exception
Added ParsedCommand subclass of Command. Also added a parse() wrapper function for easier use. This is for running external tools, and parsing the output of those tools to detect errors. (See ParsedCommand and parse().)
- Added ErrorList, OutputParser objects for ParsedCommand error parsing. (See ErrorLists and OutputParser.)
- Added OutputBuffer object for ParsedCommand context lines support. (See OutputBuffer and context lines.)
Added Output object with cross-platform output_timeout and max_timeout support. Also added get_output(), and get_text_output() wrapper functions for easier use. This is for capturing the output of an external tool for later use. (See Output, get_output(), and get_text_output().)
Added ConfigVariable and ConfigTemplate objects for configuration definition and validation support. See ConfigTemplates.
Added documentation.
Script.actions is now a namedtuple
test_config.py no longer hardcodes port 8001.
Split a number of modules out.
100% coverage
pylint 10.00
Current issues are tracked on GitHub.
Note
If you’ve cloned python-scriptharness 0.1.0, you may need to remove the scriptharness/commands directory, as it will conflict with the new scriptharness/commands.py module.