Revision: 85dec5341464
Branch: default
Author: Robot Framework Developers ([email protected])
Date: Mon Jan 7 05:02:48 2013
Log: RF 2.7.6 notes. Proofreading needed.
http://code.google.com/p/robotframework/source/detail?r=85dec5341464&repo=wiki
Modified:
/ReleaseNotes27.wiki
=======================================
--- /ReleaseNotes27.wiki Wed Oct 24 08:43:23 2012
+++ /ReleaseNotes27.wiki Mon Jan 7 05:02:48 2013
@@ -496,3 +496,83 @@
|| Issue 1229 || Documentation || Low || Support ANSI colors on console
output also on Windows ||
Altogether 27 issues.
+
+= Robot Framework 2.7.6 =
+
+Robot Framework 2.7.6 fixes a big memory leak (issue 1202), adds new
+`*.robot` extension for plain text data files (issue 1018), and
+contains several other higher and lower priority enhancements and
+fixes. It was released on Monday 7th of January, 2013.
+
+== Most important fixes and enhancements ==
+
+=== Big memory leak fixed ===
+
+Running tests leaked memory (issue 1202) resulting to excess memory
+usage with larger test data sets. In one case memory usage dropped
+whopping 95% from 10GB to 0.5GB, and about 20% enhancements were
+noticed with other cases.
+
+=== New `*.robot` extension for plain text test data ===
+
+It is nowadays possible to use special `.robot` extension with Robot
+Framework test data. This can be handy in order to separate these
+files from other files used for testing. Other than the extension
+these files do not differ from old `.txt` files at all.
+
+The built-in Tidy tool has been enhanced to support `*.robot` files but
+[http://code.google.com/p/robotframework-ride/issues/detail?id=1182 RIDE
does not yet support them].
+
+== Potentially backwards-incompatible changes ==
+
+It is possible, but very unlikely, that these changes could cause
+backwards-compatibility problems:
+
+ * All standard libraries use logging API instead of `print` for logging
(issue 1301). This may cause messages to appear in wrong order in log files
if you extend these libraries and use `print` for logging in them. In
practice this is likely to cause problems only with `Telnet`. The fix is to
start using the logging API with custom libraries extending it.
+ * `Telnet` library got two new configuration parameters encoding (issue
1312) and default log level (issue 1318). As discussing in these issues,
libraries extending `Telnet` may be affected.
+ * `Run Keywords` keyword separates keyword calls with `AND` (issue
1303). This causes problems in the _very_ unlikely case that you use a
keyword with exact this name, including case. Using the keyword e.g. like
`And` or escaping it like `\AND` fix the problem.
+
+== Acknowledgements ==
+
+Chris Prinos provided documentation how to debug test execution with
+`pdb` (issue 1282). Thanks also for everyone reporting issues, helping
+debugging problems, and otherwise making RF 2.7.6 a great release!
+
+== Full list of enhancements and fixes ==
+
+|| *ID* || *Type* || *Priority* || *Summary* ||
+|| Issue 1202 || Defect || Critical || Test execution leaks memory ||
+|| Issue 1266 || Defect || High || User keywords return no value if they
contain continuable failures ||
+|| Issue 1277 || Defect || High || Teardown for user keyword not executed
if keyword uses embedded arguments ||
+|| Issue 1278 || Defect || High || Exit For Loop does not work inside
teardowns ||
+|| Issue 1286 || Defect || High || Testdoc is broken in RF 2.7.5 ||
+|| Issue 1018 || Enhancement || High || Alternative `*.robot` extension
for test data in plain text files ||
+|| Issue 1289 || Enhancement || High || Tidy: Split multiline documenation
into multiple lines ||
+|| Issue 1307 || Enhancement || High || Include original error message in
suite setup/teardown failed messages ||
+|| Issue 1271 || Defect || Medium || `tidy` should not resolve `${CURDIR}`
with --recursive ||
+|| Issue 1280 || Defect || Medium || Output and xunit files have invalid
line endings (\r\r\n) on Windows ||
+|| Issue 1284 || Defect || Medium || libdoc: Creating documentation for
resource file fails if it has multiple keywords with same name ||
+|| Issue 1288 || Defect || Medium || Tags in statistics are not sorted
case-insensitevely ||
+|| Issue 1300 || Defect || Medium || UNC paths are not handled correctly
when tests are executed in directory root ||
+|| Issue 1310 || Defect || Medium || Telnet library: `Read Until` keywords
fail if output contains non-ASCII characters ||
+|| Issue 1311 || Defect || Medium || Tests execution freezes with
standalone jar at least when using SSHLibrary ||
+|| Issue 1321 || Defect || Medium || Recursive for loops can cause
corrupted outputs ||
+|| Issue 1301 || Enhancement || Medium || All standard libraries should
use logging API and not print for logging ||
+|| Issue 1302 || Enhancement || Medium || New `Run Keyword And Return
Status` keyword to return true/false depending on keyword status ||
+|| Issue 1303 || Enhancement || Medium || `Run Keywords` should support
running keywords with arguments ||
+|| Issue 1309 || Enhancement || Medium || Tidy: Option to specify line
separator (and fix default line separators on Windows) ||
+|| Issue 1312 || Enhancement || Medium || Telnet library: Possibility to
specify encoding ||
+|| Issue 1282 || Documentation || Medium || Document how to debug
execution with `pdb` in User Guide ||
+|| Issue 1315 || Documentation || Medium || Telnet library: Better library
documentation ||
+|| Issue 1304 || Defect || Low || `Screenshot` library should not create
wx app references in module level ||
+|| Issue 1306 || Defect || Low || Parsing modules should preserve all
comment characters ||
+|| Issue 1308 || Defect || Low || Parsing modules do not preserve comments
after FOR loop declaration ||
+|| Issue 1314 || Defect || Low || Telnet library: Fixes and enhancements
to `Login` keyword ||
+|| Issue 1317 || Defect || Low || `ELSE IF`, `ELSE` and `AND` are not
always escaped properly ||
+|| Issue 1320 || Defect || Low || Dry-run mode fails if `Set
Global/Suite/Test Variable`, `Variable Should (Not) Exist`, or `Get
Variable Value` is used with escaped variable ||
+|| Issue 1281 || Enhancement || Low || Argument files should support '='
and any number of spaces as separator between options and values ||
+|| Issue 1293 || Enhancement || Low || Warn when using invalid run-mode ||
+|| Issue 1318 || Enhancement || Low || Telnet library: Possibility to set
default log level globally ||
+
+Altogether 32 issues.
+
