Revision: 61bef699f347
Branch: default
Author: [email protected]
Date: Wed Jan 9 06:33:06 2013
Log: Edited wiki page ReleaseNotes27 through web user interface.
http://code.google.com/p/robotframework/source/detail?r=61bef699f347&repo=wiki
Modified:
/ReleaseNotes27.wiki
=======================================
--- /ReleaseNotes27.wiki Mon Jan 7 05:30:36 2013
+++ /ReleaseNotes27.wiki Wed Jan 9 06:33:06 2013
@@ -543,10 +543,12 @@
== Potentially backwards-incompatible changes ==
-It is possible, but very unlikely, that the followin changes can cause
-backwards-compatibility problems:
+It is possible, but unlikely, that the following changes can cause
+backwards-compatibility problems. Most of these changes affect only
[TelnetLibrary Telnet library] that was heavily enhanced in this release.
* 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 practice this
is likely to cause problems only with `Telnet`. The fix is to start using
the logging API with custom libraries extending it.
+ * Previously `Telnet` library used ASCII encoding when writing or
reading and ignored possible encoding errors. In RF 2.7.6 encoding is
configurable (issue 1312), UTF-8 is used by default, and possible encoding
errors are not ignored. As a result there are problems with connections
using other than UTF-8 or ASCII encoding (latter is a subset of the former
and thus works by default), unless the correct encoding is explicitly
specified. This will be fixed in RF 2.7.7 by ignoring encoding errors by
default and making the error handler configurable (issue 1328).
+ * `Telnet.Read Until Regexp` keyword fails if a compiled regular
expression is used as the last argument. This bug (issue 1327) will be
fixed in RF 2.7.7.
* `Telnet` library got two new configuration parameters encoding (issue
1312) and default log level (issue 1318). As discussed in those issues,
custom 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.
@@ -565,15 +567,15 @@
|| 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 1289 || Enhancement || High || Tidy: Split multiline
documentation 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 1288 || Defect || Medium || Tags in statistics are not sorted
case-insensitively ||
|| 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 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 ||
@@ -593,4 +595,3 @@
|| Issue 1318 || Enhancement || Low || Telnet library: Possibility to set
default log level globally ||
Altogether 32 issues.
-
