Author: pekka.klarck
Date: Wed Apr 8 02:55:34 2009
New Revision: 1752
Modified:
wiki/ReleaseNotes21.wiki
Log:
update
Modified: wiki/ReleaseNotes21.wiki
==============================================================================
--- wiki/ReleaseNotes21.wiki (original)
+++ wiki/ReleaseNotes21.wiki Wed Apr 8 02:55:34 2009
@@ -4,14 +4,14 @@
= Robot Framework 2.1 =
-Robot Framework 2.1 is the first major release in the first open
-source release in June 2008. It contains plenty of new functionality
-and also ssome new libraries.
+Robot Framework 2.1 is the first major release after the framework was
+open sourced in June 2008. It contains plenty of new functionality
+and also some new libraries.
Robot Framework 2.1 beta was released on Wednesday 2009-04-08 and it
can be downloaded from the
-[http://code.google.com/p/robotframework/downloads/list download
-page]. The beta release should already contain all the changes to the
+[http://code.google.com/p/robotframework/downloads/list download page].
+The beta release should already contain all the changes to the
core framework but String library (issue 231) and Remote library
(issue 118) are still under development and some documentation still
needs to be updated.
@@ -22,10 +22,17 @@
== Backwards incompatible changes ==
- * Using test data with URLs is not possible anymore (issue 123)
+Robot Framework 2.1 has plenty of internal changes which make external
+tools like RobotIDE and Mabot incompatible with it. New releases of
+these tools will be released right after the final 2.1 version.
+
+Changes possibly affecting existing test cases or how they are executed:
+
* Information about critical tags and filtered tests is not stored in
output XML (issue 146)
+ * Using test data with URLs is not possible anymore (issue 123)
* Internal logging is changed which might affect external tools (issue
254)
- * Some very raraly needed keywords and some arguments to keywords
deprecated (issue 217, issue 257, issue 259, issue 262, issue 270)
+ * Some very rarely needed keywords and arguments to keywords have been
deprecated (issue 217, issue 257, issue 259, issue 262, issue 270)
+
== Acknowledgements ==
@@ -37,4 +44,56 @@
== List of fixes and enhancements ==
+
+|| *ID* || *Type* || *Priority* || *Summary* ||
+|| Issue 241 || Defect || Critical || Character references in HTML data
are ignored ||
+|| Issue 28 || Defect || High || Tests and suites don't have unique link
targets in log files ||
+|| Issue 275 || Defect || High || Using varargs in Java keywords fails
with libraries imported using 'WITH NAME' syntax ||
+|| Issue 123 || Enhancement || High || Remove code related to using test
data with URLs ||
+|| Issue 146 || Enhancement || High || Don't store information related to
critical tags and filtered tests to XML outputs ||
+|| Issue 182 || Enhancement || High || Tags should not be normalized ||
+|| Issue 197 || Enhancement || High || Update robotidy.py tool to replace
deprecated keyword repeating syntax with Repeat Keyword ||
+|| Issue 200 || Enhancement || High || Log messages with WARN level should
be automatically written to syslog ||
+|| Issue 203 || Enhancement || High || New keyword "Set Library Search
Order" to ease handling keywords with same names ||
+|| Issue 254 || Enhancement || High || Centralized logger ||
+|| Issue 18 || Library || High || New standard library "String" for
different string operations ||
+|| Issue 118 || Library || High || Remote library ||
+|| Issue 253 || Library || High || New standard library for interactive
dialogs ||
+|| Issue 213 || Defect || Medium || Telnet login fails if server sends
wierd unicode chars ||
+|| Issue 224 || Defect || Medium || Unicode error with libdoc.py ||
+|| Issue 230 || Defect || Medium || --argumentfile option should be
accepted multiple times ||
+|| Issue 234 || Defect || Medium || Installation using install.py fails if
Python is installed into a path with spaces ||
+|| Issue 236 || Defect || Medium || system path appears to not be updated
if installing RF in virtual-env on Mac OSX ||
+|| Issue 244 || Defect || Medium || Test case criticality is not updated
after using Set Tags or Remove Tags keywords ||
+|| Issue 249 || Defect || Medium || libdoc.py requires double \n is
resource files ||
+|| Issue 250 || Defect || Medium || libdoc.py and testdoc.py should not
evaluate ${CURDIR} variable ||
+|| Issue 252 || Defect || Medium || Library implemented as a module cannot
have a function or other attribute with the same name as the module ||
+|| Issue 267 || Defect || Medium || robotidy.py recursive mode does not
work with directories containing other than html and tsv files ||
+|| Issue 2 || Enhancement || Medium || Show source where test suite data
orignated in log ||
+|| Issue 88 || Enhancement || Medium || Listener interface methods need
more information about suites, tests and keywords ||
+|| Issue 89 || Enhancement || Medium || Possibility to specify test suite
execution order with non-visible prefixes ||
+|| Issue 214 || Enhancement || Medium || New builtin variable - ${EXECDIR}
||
+|| Issue 217 || Enhancement || Medium || Deprecate Create File
keyword's 'mode' argument in favor of 'encoding' ||
+|| Issue 231 || Enhancement || Medium || Add a ReStructuredText parser for
plain-text definition of suites/tests ||
+|| Issue 239 || Enhancement || Medium || All OperatingSystem keywords
handling paths shoud create links to affected files/dirs in the log file ||
+|| Issue 245 || Enhancement || Medium || Automatic type conversion for
Java keywords ||
+|| Issue 248 || Enhancement || Medium || Top level documentation in
resource files ||
+|| Issue 255 || Enhancement || Medium || New keyword 'Append To File' to
OperatingSystem library ||
+|| Issue 257 || Enhancement || Medium || Deprecate 'Grep File' keyword ||
+|| Issue 259 || Enhancement || Medium || Deprecate 'pattern_type' argument
of List Directory keywords ||
+|| Issue 262 || Enhancement || Medium || Deprecate using Set Variable
keyword with more/less than one value ||
+|| Issue 264 || Enhancement || Medium || Keyword "Comment" should not
resolve variables ||
+|| Issue 268 || Enhancement || Medium || Non-existing variables in suite,
test and keyword documentations should not cause errors ||
+|| Issue 274 || Enhancement || Medium || Enhancements to how test and
suite names are written in report (no more x.y.z.Name format) ||
+|| Issue 277 || Enhancement || Medium || New keywords Get Count, Should
Contain X Times and Should Not Contain X Times to BuiltIn library ||
+|| Issue 167 || Documentation || Medium || Document using
BuiltIn.replace_variables as a public API for getting variables and
settings to test libraries ||
+|| Issue 211 || Documentation || Medium || Need to document that TSV files
are expected to have UTF-8 encoding ||
+|| Issue 52 || Defect || Low || Running tests fails if a suite has name
ending with a dot ||
+|| Issue 133 || Enhancement || Low || Remove warning about having same
test multiple times in a suite ||
+|| Issue 216 || Enhancement || Low || Remove the warning for empty
__init__.html in directory suites ||
+|| Issue 240 || Enhancement || Low || Evaluate keyword should take an
optional list of modules to add into the namespace of the evaluated
expression ||
+|| Issue 263 || Enhancement || Low || Log Variables keyword should log
variable names using their original format ||
+|| Issue 270 || Enhancement || Low || Deprecate Syslog keyword ||
+|| Issue 278 || Enhancement || Low || 'Set Test/Suite/Global Variable'
and 'Variable Should (Not) Exist' keywords work also when the variable name
is given in normal format ||
+|| Issue 226 || Documentation || Low || Better explanation on how to
install RF when using Jython ||
