Revision: 3228 Author: pekka.klarck Date: Thu May 6 09:09:34 2010 Log: [No log message] http://code.google.com/p/robotframework/source/detail?r=3228
Modified: /wiki/ReleaseNotes25.wiki ======================================= --- /wiki/ReleaseNotes25.wiki Thu May 6 07:33:48 2010 +++ /wiki/ReleaseNotes25.wiki Thu May 6 09:09:34 2010 @@ -1,4 +1,84 @@ -|| ID || Type || Priority || Summary || +#summary Robot Framework 2.5 pre-releases + +<wiki:toc max_depth="1"/> + += Robot Framework 2.5 Preview Releases = ++Robot Framework 2.5 is a new major release with loads of bigger and smaller enhancements
+and bug fixes. The target is to release it in May 2010. ++Before the final release there will be some alpha, beta, and release candidate releases in order to:
+ + * make the already implemented features available to users, + * get feedback from the new features, and + * allow users to test the new version on their environments. + +Please submit possible bugs to the+[http://code.google.com/p/robotframework/issues/list issue tracker] and send general
+comments to [MailingLists mailing lists]. + + += Most important new features = + +== Continuing test execution on failure == ++Being able to continue the test execution after failures was the most requested feature in RF 2.5. There are several ways to accomplish it:
+ + * Raising a _continuable_ exception from test library (issue 137) + * Using `Run Keyword And Continue On Failure` keyword (issue 545) + * In teardowns all keywords are executed automatically (issue 544) ++In all these cases the test will be marked failed at the end. Its final error message is created by combining the messages from the occurred failures together.
+ +== Stopping test execution gracefully == ++Another important test execution related features is the ability to stop the test execution fully so that reports and logs are generated. Nowadays there are several ways to do it:
+ + * Pressing Ctrl-C (issue 108) + * Using signals (issue 349) + * Raising a _fatal_ exception from library (issue 366) + * Using `Fatal Error` keyword (issue 546) + +== Support for name arguments == ++The named arguments syntax (issue 215) makes it possible to use keywords that have several arguments with default values so that only certain arguments are overridden. +For example, the keyword below could be used like `| Named Arg Example | zap=42 |` and first two arguments would get their default values.
+
+{{{
+ def named_arg_example(foo=1, bar=2, zap=3):
+ print foo, bar, zap
+}}}
+
+== Full Jython 2.5 support ==
+
+Robot Framework 2.1.3 already works with Jython 2.5 but there were some
rough edges . Nowadays Jython 2.5 is fully and officially supported, and
even installation using it works (issue 547).
+ += Backwards incompatible changes = + +== Minimum Python/Jython version is 2.5 == ++Robot Framework 2.5 only runs on Python and Jython 2.5 or newer (but on 3.x yet). +If you cannot upgrade your Python/Jython installation you can use older Robot Framework releases that support Jython 2.2 and Python 2.3 and newer.
+ +== Not compatible with current RIDE and Mabot releases == ++The internal changes in the framework have made it incompatible with the latest RIDE and Mabot releases. Compatible versions of these important supporting tools will be created as soon as the final 2.5 release is ready.
+ +== Other backwards incompatible changes == ++Potentially backwards incompatible issues are labeled with `bwic` label in the +[issue tracker http://code.google.com/p/robotframework/issues/list?can=1&=target%3D2.5+label%3Dbwic]. Why these changes may cause problems will be explained thoroughly later when these release notes are improved.
+ += Deprecated features = + +Will be listed later. + + += Robot Framework 2.5 Alpha 1 = ++The first RF 2.5 pre-release was releases on 2010-05-06. Full list of issues is below.
+ +|| *ID* || *Type* || *Priority* || *Summary* || || Issue 198 || Enhancement || Critical || Jython 2.5 support |||| Issue 288 || Defect || High || It is not possible to assign all Python and Java iterables to list variables || || Issue 529 || Defect || High || UTF-8 BOM is not ignored in plain text or TSV test data files ||
@@ -51,4 +131,3 @@|| Issue 527 || Enhancement || Low || Remove deprecated `--colormonitor` option ||
Altogether 50 issues. -
