Revision: e8d87ddd5458
Branch: default
Author: robotframew...@gmail.com
Date: Tue Jun 11 07:04:09 2013
Log: Edited wiki page ReleaseNotes28 through web user interface.
http://code.google.com/p/robotframework/source/detail?r=e8d87ddd5458&repo=wiki
Modified:
/ReleaseNotes28.wiki
=======================================
--- /ReleaseNotes28.wiki Tue Jun 11 06:31:39 2013
+++ /ReleaseNotes28.wiki Tue Jun 11 07:04:09 2013
@@ -34,7 +34,7 @@
=== Public API for generating and executing tests ===
A completely new API is introduced for creating executable test suites
-programmatically on fly. Practically this means that tests can be now
+programmatically on fly (issue 825). Practically this means that tests can
be now
created using Python programming language using based on external models
or otherwise.
Robot Framework now provides
[http://robot-framework.readthedocs.org/en/latest/autodoc/robot.running.html#robot.running.model.TestSuite
TestSuite] API for creating an executable
@@ -49,67 +49,66 @@
=== New `Process` test library ===
-[ProcessLibrary Process] library is a completely new test library which
introduces new keywords for running processes.
+[ProcessLibrary Process] library is a completely new test library which
introduces new keywords for running processes (issue 485).
The main enhancements compared to the process execution keywords in
[OperatingSystemLibrary OperatingSystem] library are better configuration
and possibility to terminate started processes. See the [ProcessLibrary
documentation of the library] for more information.
=== Named arguments changes ===
-All arguments can be
[http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html#named-arguments
named] now, not just the arguments with default values.
-If a positional argument is used after named arguments, this now
-results to a clear error.
+There are several bigger and smaller enhancements to the named argument
syntax:
-Named arguments can now
[http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html#named-argument-syntax-with-dynamic-libraries
be used with dynamic libraries], e.g.
[https://github.com/robotframework/SwingLibrary SwingLibrary], and they
also work when a library
-is brought into use using
[http://robotframework.googlecode.com/hg/doc/libraries/BuiltIn.html#Import%20Library
Import Library] keyword.
+ * All arguments can be
[http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html#named-arguments
named] now, not just the arguments with default values (issue 1324).
+ * Named arguments are
[http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html#named-argument-syntax-with-dynamic-libraries
supported by dynamic libraries], e.g.
[https://github.com/robotframework/SwingLibrary SwingLibrary] (issue 1115).
+ * If a positional argument is used after named arguments, this now
results to a clear error (issue 1325).
+ * Named arguments work when importing a library using
[http://robotframework.googlecode.com/hg/doc/libraries/BuiltIn.html#Import%20Library
Import Library] keyword (issue 1424).
=== Support for Python's keyword arguments ===
-Python has a so called keyword argument syntax which is now supported by
-[http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html#named-arguments
Robot
Framework as well].
+Python has a so called keyword argument syntax (`**kwarsg` which is now
supported by
+[http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html#free-keyword-arguments
Robot
Framework as well].
-In practice, if we create a new keyword:
+In practice, if we create a keyword like this:
{{{
-def run_process(command, *args, **conf):
+def run_process(command, *arguments, **configuration):
# ...
}}}
-And call this keyword as following:
+and call it as follows:
{{{
Run Process ls -h cwd=/tmp
}}}
-Variable `conf` now contains a dictionary `{'cwd': '/tmp'}`. This eases
+the parameter `configuration` now contains a dictionary `{'cwd': '/tmp'}`.
This eases
the argument handling on the library side.
-=== Variable table improvements ===
+Note: `Run Process` keyword in the new [ProcessLibrary Process] library
works exactly like above.
-It is now possible to use imported variables in the variable table. (Issue
561)
+=== Support for re-executing failed test cases ===
+
+New command line option `--runfailed` allows executing tests that have
failed again (issue 702).
+=== Creating reports and xUnit outputs is possible without processing
output.xml ===
-=== New control keywords in !BuiltIn test library ===
+If tests are run with `--log NONE`, report and possible xUnit output are
created without processing output.xml (issue 1432). This can save both time
and memory considerably.
-A few new keywords were requested, so they are now available in
[https://code.google.com/p/robotframework/wiki/BuiltInLibrary BuiltIn
library].
-All of the introduced keywords have the conditional versions as well.
+=== Variable related enhancements ===
- * `Pass Execution` and `Pass Execution If`, which make the test pass
immediately and skip executing any further steps of the test.
+ * It is possible to use imported variables in the variable table (issue
561).
+ * It is possible to use scalar variables as list variables (issue 483).
- * `Return From Keyword` and `Return From Keyword If`, which returns the
control to the calling keyword with the user specified return values.
+=== New control keywords in !BuiltIn test library ===
-Also, it's now possible to
[http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html#exiting-for-loop
exit from] and
[http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html#continuing-for-loop
continue]
-for loop with the following keywords are introduced:
+A few new keywords were requested, so they are now available in
[BuiltInLibrary BuiltIn] library.
+All of the introduced keywords have the conditional versions as well.
- *
[http://robotframework.googlecode.com/hg/doc/libraries/BuiltIn.html#Continue%20For%20Loop
Continue For Loop] and
[http://robotframework.googlecode.com/hg/doc/libraries/BuiltIn.html#Continue%20For%20Loop%20If
Continue For Loop If], which are equal to `continue` in popular programming
languages.
+ * `Pass Execution` and `Pass Execution If`, which make the test pass
immediately and skip executing any further steps of the test (issue 174).
- *
[http://robotframework.googlecode.com/hg/doc/libraries/BuiltIn.html#Exit%20For%20Loop
Exit For Loop] and
[http://robotframework.googlecode.com/hg/doc/libraries/BuiltIn.html#Exit%20For%20Loop%20If
Exit For Loop If], which are equal to `break` in popular programming
languages.
+ * `Return From Keyword` and `Return From Keyword If`, which return the
control to the calling keyword with the user specified return values (issue
996).
-=== Own command line options for different run modes ===
+ * `Continue For Loop` and `Continue For Loop If`, which work like
`continue` statement in popular programming languages (issue 1125).
-New, handier command line options are introduced in favor of `--runmode`:
+ * `Exit For Loop If`, as a conditional variant for the existing `Exit
For Loop` (issue 1411).
- * `--dryrun`, equal to `--runmode dryrun` for
[http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html#dry-run
dry running tests].
- * `--randomize none/tests/suites/all`, equal to `--runmode
Random:<what>` for
[http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html#randomizing-execution-order
randomizing test execution order].
- * `--exitonfailure`, equal to `--runmode exitonfailure` for
[http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html#stopping-when-first-test-case-fails
stopping when the first test case fails].
- * `--skipteardownonexit`, equal to `--runmode skipteardownonexit` for
[http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html#handling-teardowns
skipping teardowns when execution is stopped].
== Backwards incompatible changes ==
--
---
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.
