Revision: 4f7c0f79a14c
Branch: default
Author: robotframew...@gmail.com
Date: Tue Jun 11 07:27:59 2013
Log: Edited wiki page ReleaseNotes28 through web user interface.
http://code.google.com/p/robotframework/source/detail?r=4f7c0f79a14c&repo=wiki
Modified:
/ReleaseNotes28.wiki
=======================================
--- /ReleaseNotes28.wiki Tue Jun 11 07:09:55 2013
+++ /ReleaseNotes28.wiki Tue Jun 11 07:27:59 2013
@@ -100,11 +100,8 @@
New control flow related keywords have been added to the [BuiltInLibrary
BuiltIn] library:
* `Pass Execution` and `Pass Execution If`, which make the test pass
immediately and skip executing any further steps of the test (issue 174).
-
* `Return From Keyword` and `Return From Keyword If`, which return the
control to the calling keyword with the user specified return values (issue
996).
-
* `Continue For Loop` and `Continue For Loop If`, which work like
`continue` statement in popular programming languages (issue 1125).
-
* `Exit For Loop If`, as a conditional variant for the existing `Exit
For Loop` (issue 1411).
@@ -112,68 +109,61 @@
=== The old runner entry point removed ===
-Deprecated `robot/runner.py` entry point was removed.
-Please use `robot/run.py` instead. (Issue 1439)
+Deprecated `robot/runner.py` entry point was removed (issue 1439).
+Please use `robot/run.py` instead.
-=== Screenshot test library keywords removed ===
+=== Deprecated Screenshot library keywords removed ===
Deprecated keywords `Save Screenshot`, `Save Screenshot To` and
-`Log Screenshot` were removed from
[http://robotframework.googlecode.com/hg/doc/libraries/Screenshot.html
Screenshot test library]. (Issue 1093).
+`Log Screenshot` were removed from [ScreenshotLibrary Screenshot] library
(issue 1093).
-=== Changes to scalar variables ===
+=== Creating scalar list in variable table is not possible ===
-Using
[http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html#using-scalar-variables-as-lists
scalar variables as lists] is now possible.
-
-However, creating a scalar variable with a list as it's value
-is not allowed in the variable table anymore. (Issue 939) This was
already deprecated
+Creating a scalar variable with a list as it's value
+is not allowed in the variable table anymore (issue 939). This was
already deprecated
in Robot Framework 2.5. If there still is data that uses this
functionality,
updating it is nearly trivial. All that is needed is changing `$` to `@`
in the variable name in the variable table.
-=== Using __init__ files as resources ===
+=== Using test suite init files as resources is not allowed ===
-Using `__init__` files as resources is not allowed anymore. Previously this
-resulted an error message. (Issue 1276)
+Using test suite init files (e.g. `__init__.txt`) as resources is not
allowed anymore (issue 1276).
-=== Changes to report generation ===
+=== Report (and log) generated if tests run `--output NONE` ===
-A report is now generated by default, even if the generation of output XML
is
-disabled (by defining `--output NONE` on command line). (Issue 1444)
+Earlier using `--output NONE` disabled creating a log and a report in
addition to the XML output file.
+Now that the report can be generated also without the output file (issue
1432) this behavior was changed.
-Also, report and XUnit are now generated without first reading output XML,
-which saves memory.
+If just `--output NONE` is used with RF 2.8, the report is generated and
there is an error about log generation failing (issue 1444).
+Use `--output NONE --report NONE --log NONE` to disable all outputs.
=== Empty timeout attributes in output XML ===
-Empty timeout attributes are not written to output XML anymore. (Issue
1438)
+Empty timeout attributes are not written to the output XML anymore (issue
1438).
Using timeouts is pretty rare, so most of the time test cases and keywords
just
had `timeout=""`. This increased XML size without any real benefits.
The change is backwards incompatible because XML readers cannot expect
timeout
-attribute to exist. This shouldn't be a problem because most readers are
not
+attribute to exist. This should not be a big problem because most readers
are not
likely to care about the timeout. Those that care, can easily use a default
value when the attribute is not present.
=== Command line option errors are now fatal ===
-All command line option errors are now handled as fatal
-and won't start the test execution. (Issue 1447)
-
-This includes options `--reportbackground`, `--tagstatlink` and
-`--suitestatlevel`, all of which previously triggered a warning and
-proceeded using the option default value if an invalid value was given.
+All command line option errors are now handled as fatal errors preventing
test execution (issue 1447).
+Earlier some errors were fatal, but with `--reportbackground`,
`--tagstatlink` and
+`--suitestatlevel` there was just a warning.
=== Traceback removed from xUnit outputs ===
-Previously if robot was run on DEBUG level, the xUnit output contained
-a traceback of a failure, if one was available. Now that xUnit output is
-generated without reading the output xml to memory, the tracebacks are
-never written. (Issue 1456)
+Previously if test were run on DEBUG level, the xUnit output contained
+a traceback of a failure (as well as all other debug messages). Now that
xUnit output can be
+generated without reading the output.xml to memory, the tracebacks are
+never written (issue 1456).
=== Non-existing variables in tags fail the test ===
-If a non existing variable is used in a test tag, this will fail the test
on Robot 2.8.
-In earlier versions these tags got the variable name as value. (Issue 1469)
+Using a non-existing variable tests's tags fails the test (issue 1469).
== Deprecated features ==
--
---
You received this message because you are subscribed to the Google Groups "robotframework-commit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to robotframework-commit+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
