Revision: 270db464821b
Branch: default
Author: Anssi Syrjäsalo
Date: Tue Jun 11 00:22:00 2013
Log: Updated 2.8 notes
http://code.google.com/p/robotframework/source/detail?r=270db464821b&repo=wiki
Modified:
/ReleaseNotes28.wiki
=======================================
--- /ReleaseNotes28.wiki Mon Jun 10 08:13:04 2013
+++ /ReleaseNotes28.wiki Tue Jun 11 00:22:00 2013
@@ -26,48 +26,51 @@
are not dependent on the installed Robot Framework version. It
is thus safe to install any Robot Framework release alongside RIDE.
+== Compatibility with Mabot ==
+
+
+
+
== Most important enhancements and new features ==
=== Public API for generating and executing tests ===
-A completely new API is introduced for generating executable test suites
-programmatically on fly. This means that test suites can be now created
-using a programming language, e.g. Python.
+A completely new API is introduced for creating executable test suites
+programmatically on fly. Practically this means that tests can be now
+created using a programming language e.g. Python.
-Robot Framework provides an API for creating executable TestSuite objects.
-Test cases, keywords, variables can be added to these objects using the
-methods provided by the API. TestSuite objects can be then executed,
-returning a Result object. It is also possible to build TestSuite
-objects directly from text files using the TestSuiteBuilder API.
+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
+test suite structure. This structure possibly includes test cases,
keywords,
+variables, imports and so on - basically everything that can be done in the
+test case files is also possible via the API.
-All the standard Robot Framework features, e.g. defining own keywords,
-using libraries and loading resources from files are supported by the API.
+Additionally, these executable TestSuite objects can be built based on the
+existing test case files and directories using
[http://robot-framework.readthedocs.org/en/latest/autodoc/robot.running.html#robot.running.builder.TestSuiteBuilder
TestSuiteBuilder API].
-Please take a look at
[http://robot-framework.readthedocs.org/en/latest/autodoc/robot.running.html
Robot Framework API documentation] for examples.
+Please take a look at
[http://robot-framework.readthedocs.org/en/latest/autodoc/robot.running.html
Robot Framework API documentation] for practical examples.
=== New test library: Process test library ===
-!ProcessLibrary is a completely new test library which introduces several
-keywords for managing processes and checking the process status.
+[https://code.google.com/p/robotframework/wiki/ProcessLibrary
ProcessLibrary]
+is a completely new test library which introduces new keywords for managing
+processes and checking the process status.
-The library allows starting and running processes in a customized
environment.
+The library includes keywords to run processes in a customized environment.
This means that processes can be executed in the specific working
directory,
in shell on demand, and with given environment variables set. Terminating
-and switching between the created processes is also possible.
+and switching between the created processes is also supported. The library
+also provides keywords for asserting if the process still running.
-The library also provides keywords for asserting the process status, which
-can be used for checking if the process still running.
-
-See [https://code.google.com/p/robotframework/wiki/ProcessLibrary Process
test library documentation] for library documentation.
+See [https://code.google.com/p/robotframework/wiki/ProcessLibrary Process
test library documentation] for the library documentation.
=== New control keywords in BuiltIn test library ===
-A few keywords were requested, so they are now available
in !BuiltInLibrary.
-All of these keywords have the conditional versions as well.
+A few new keywords were requested, so they are now available in
[https://code.google.com/p/robotframework/wiki/BuiltInLibrary
BuiltInLibrary].
+All of the introduced keywords have the conditional versions as well.
- * `Pass Execution` / `Pass Execution If`, which make the test pass
immediately and prevent executing any further steps of the test.
+ * `Pass Execution` / `Pass Execution If`, which make the test pass
immediately and skip executing any further steps of the test.
- * `Return From Keyword` / `Return From Keyword If`, which returns the
control to the calling keyword with the specified return values.
+ * `Return From Keyword` / `Return From Keyword If`, which returns the
control to the calling keyword with the user specified return values.
Also, the following keywords are introduced as improvements to the for
loops:
@@ -77,16 +80,15 @@
=== Named arguments with dynamic libraries ===
-Named arguments can be used now with dynamic libraries (e.g. !SwingLibrary)
-and they also work when library is brought into use using `Import Library`
-keyword.
+Named arguments can be used now with dynamic libraries, e.g.
[https://github.com/robotframework/SwingLibrary SwingLibrary], and they
also work when a library
+is brought into use using `Import Library` keyword.
=== Support for Python's keyword arguments ===
-Python has so called keyword argument syntax which is now supported by
-Robot Framework as well.
+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].
-If we create a new keyword:
+In practice, if we create a new keyword:
{{{
def run_process(command, *args, **conf):
# ...
@@ -97,15 +99,16 @@
Run Process ls -h cwd=/tmp
}}}
-Variable `conf` will contain dictionary `{'cwd': '/tmp'}`.
+Variable `conf` now contains a dictionary `{'cwd': '/tmp'}`. This eases
+the argument handling on the library side.
=== Variable table improvements ===
It is now possible to use imported variables in the variable table.
-=== Own command line options for run modes ===
+=== Own command line options for different run modes ===
-New, handier command line options are introduced (in favor of `--runmode`):
+New, handier command line options are introduced in favor of `--runmode`:
* `--dryrun`, equal to `--runmode dryrun`
* `--randomize none/tests/suites/all`, equal to `--runmode Random:<what>`
@@ -131,14 +134,15 @@
Also, if a positional argument is used after named arguments, this now
results to a clear error.
-=== Scalar variables with list values ===
+=== Changes to scalar variables ===
-Defining a scalar variable with a list as its value is not allowed in
-the variable table anymore. This was deprecated in Robot Framework 2.5.
+Using
[http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html#using-scalar-variables-as-lists
scalar variables as lists] is now possible.
-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.
+However, creating a scalar variable with a list as it's value in the
variable table with a list as its
+value is not allowed in the variable table anymore. 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 ===
@@ -151,7 +155,7 @@
disabled (by defining `--output NONE` on command line).
Also, report and XUnit are now generated without first reading output XML,
-which also speeds up the generation.
+which saves memory.
=== Empty timeout attributes in output XML ===
@@ -205,9 +209,9 @@
|| Issue 1379 || Defect || Medium || Settings and variable tables: Three
dots are handled correctly ||
|| Issue 1395 || Defect || Medium || Dialogs library documentation
improved ||
|| Issue 1453 || Defect || Medium || Wrong encoding detection for HTML5
document ||
-|| Issue 1455 || Defect || Medium || Process.Start Process unable to
execute command which change folder ||
+|| Issue 1466 || Defect || Medium || Dialog boxes don't properly close
with Python on Linux ||
|| Issue 174 || Enhancement || Medium || New BuiltIn keyword to stop text
execution with PASS status ||
-|| Issue 483 || Enhancement || Medium || Scalar variables as list
variables are allowed ||
+|| Issue 483 || Enhancement || Medium || Using scalar variables as list
variables is allowed ||
|| Issue 996 || Enhancement || Medium || New BuiltIn keywords for
returning from user keywords ||
|| Issue 1125 || Enhancement || Medium || New BuiltIn keyword for
continuing for loop execution ||
|| Issue 1325 || Enhancement || Medium || Explicit error if positional
arguments are used after named arguments ||
--
---
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.
