Revision: 186c4ed3e00f
Author: Mikko Korpela <[email protected]>
Date: Tue Jul 26 05:21:58 2011
Log: Some typos etc. corrected. Added note about no support for Excel
http://code.google.com/p/robotframework/source/detail?repo=wiki&r=186c4ed3e00f
Modified:
/FinalReleaseNotes26.wiki
=======================================
--- /FinalReleaseNotes26.wiki Mon Jul 25 15:36:06 2011
+++ /FinalReleaseNotes26.wiki Tue Jul 26 05:21:58 2011
@@ -34,7 +34,7 @@
Robot Framework 2.6 can read and process outputs generated by
2.5.x. releases. This allows testing the enhanced log and report (see
below) also without executing tests using 2.6. All you need to do is
-getting the output file (such as `ouput.xml`) and generating logs and
+get the output file (such as `ouput.xml`) and generate logs and
reports based on it with `rebot`.
= Most important enhancements and new features =
@@ -42,7 +42,7 @@
== Better log file performance ==
The biggest enhancement in this release is making the performance
-of the log files better when the amount of test cases and test data
+of the log files better when the number of test cases and test data
increases (issue 360).
This enhancement is implemented so that when you open the log file it is
@@ -60,7 +60,7 @@
== Transparent log splitting ===
-A common problem when the amount of test cases increases is that log
+A common problem when the number of test cases increases is that log
files gets too big. They do not open nicely into browsers anymore and
if they are on a remote machine downloading them takes too much time.
@@ -71,7 +71,7 @@
early during 2.6 development because it never worked that well and it
was incompatible with the new log generation system discussed above.
-Although the new logs are orders of magnitude smaller than earlier,
+Although the new logs are order of magnitude smaller than earlier,
some log splitting functionality was still needed with very large test
suites. The new approach introduced in RF 2.6 (issue 898) is splitting
the log into smaller files that can be loaded dynamically when
@@ -86,9 +86,9 @@
and the logs in 2.6 are otherwise so small compared to the old logs.
Another drawback is that copying log files or otherwise manipulating
-them after the execution gets a bit more complicated because you have
+them after the execution gets a bit more complicated when a log file has
been splitted because you have
lot of small files. Technically data from each test and suite
-setup/teardwon is written into a separate Javascript file and the
+setup/teardown is written into a separate Javascript file and the
number of files grows when the number of tests grows. The files have
name in format `'log-42.js'` where `'log'` changes depending on the
actual name of the log file and `'42'` is a growing index.
@@ -130,7 +130,7 @@
(issue 711). The mechanism of this new feature is very simple, the keyword
teardown is executed both when the keyword passes and when it fails.
-Keyword teardowns allows, for example, splitting a large test teardown
+Keyword teardowns allow, for example, splitting a large test teardown
into more fine-grained teardowns that are executed closer to the activity
that needs to be cleaned up. Another good use case is with test templates
(a new feature in [ReleaseNotes25 RF 2.5]) where
@@ -210,6 +210,8 @@
files. Upgrading your browser may thus be a good idea even if you can open
logs and reports with your old browser.
+Viewing in Excel is not supported anymore. You can still copy statistics
and other results from logs and reports to Excel, though.
+
If your company policy prevents you from upgrading IE or using
alternative browsers, you can always keep on using older Robot
Framework versions.
