Releases: byexamples/byexample
Releases · byexamples/byexample
7.2.1
7.2.0
Changes from previous version:
Enhancements:
- Find prompt-based examples of Ruby even if they are prefixed by #
This may detect new examples but it should be unlikely and with
low impact. (The Ruby module is still experimental) - Enable +fail-fast inside in an example #42 As side effect, the
examples will be skipped (marked as SKIP). See c17f433 - Enable -skip inside in an example to executing even if the execution
is failing fast #43 See c17f433 - Improved the documentation.
Fixes: - Don't let gdb to ask for confirmation.
7.1.2
7.1.1
7.1.0
Changes from previous version:
Enhancements
- Implemented the stop-on-silence option for Shell: instead of raising a
timeout, if an example takes too long the runner will stop the long-running
process. It is undefined if there isn't a process running and the
example times out. See docs/languages/shell for a complete overview and
possible usage of this.
7.0.3
7.0.2
7.0.1
7.0.0
Changes from previous version:
Fixes
- Save in
Example
its own local options and not its options merged with
the global one. It will be during the execution of the example that its
options will be merged. Expected
'sget_captures
can be called without calling
check_got_output
before.- Fixed the interact functionality for
Python 3.x
. - Print the error (if any) after the interact session.
- Make sure that
expected_str
is a string even if the example has no
expected output (in which caseexpected_str
will be the empty string). - Fixed the heuristics to avoid collisions: pick the specific finder
over the generic one even if they are of different languages. - Fix print traceback for
Python 2.x
.
Enhancements
- Allow a
Ruby
=>
following by the end of the string: this trigger the
auto print expressions without needing a value after the=>
. - The
Concerns
can add their own options and flags like theParsers
. - Made
Example
modifiable a full class instead of anamedtuple
. - Improve the errors printing the source code of the example where the
error happen (if available). - Extended the
Concern
interface adding hooks to the parsing phase of
an example:start_parse
,before_build_regex
andfinish_parse
. - Delayed the parsing phase just before executing the example: this
allow the modification of an example before parsing (like its expected). - Better error printing if the parsing of an example fails.
Clipboard
module to support 'paste' of previously captured texts. See
720916a. Use+paste
option to enable it.- Better prints (logs). See 45e3188.
Incompatible changes (examples)
- Removed
+shell
option fromShell
runner
Incompatible changes (lib)
- No more
ExampleMatch
,Example
will do its job. See f949d64.
Initially theExample
is created by theFinder
in an "incomplete, not
parsed yet" state. Later, theExample
is parsed calling
Example.parse_yourself
which callsParser.parse
. Parser.build_example
renamed toParse.parse
(and simplified its
interface).
Incompatible changes (modules)
- The option parser
optparser
is not passed explicitly, you can still
get it fromoptions['optparser']
. Runner.initialize
will not be called with the examples.Concern.start_run
will be called with a not parsed examples: some
of theirs attributes will be missing.- Renamed some
Concern
's hooks:start_run
tostart
,end_run
tofinish
,
end_example
tofinish_example
. - Removed
Example
'smeta
;Example
is writable so there is no need to
have an extra attribute.
Erratum: In the git tag says that the new Concern
methods are start_build
and finish_build
but this is incorrect, the new methods are start_parse
and finish_parse
.