adding a disclaimer on the documentation to warn users about xunit and behave_as…

adding a disclaimer on the documentation to warn users about xunit and behave_as features that are not well tested in the codebase

docs/_static/lettuce-docs.css

@@ -139,6 +139,16 @@ dt .literal, table .literal { background:none}
 div.admonition-philosophy { padding-left:65px; background:url(docicons-philosophy.png) .8em .8em no-repeat}
 div.admonition-behind-the-scenes { padding-left:65px; background:url(docicons-behindscenes.png) .8em .8em no-repeat}
 
+.admonition.warning {
+  width: 520px;
+  background-color: #FFE8E8;
+}
+.admonition.warning .first.admonition-title {
+  font-size: 20px;
+  font-weight: bold;
+  color: #933;
+}
+
 /*** versoinadded/changes ***/
 div.versionadded, div.versionchanged {  }
 div.versionadded span.title, div.versionchanged span.title { font-weight: bold}

docs/index.rst

@@ -129,3 +129,24 @@ recipes
 **make your own salad**
 
     * :ref:`nicer assertions with nose <recipes-nose>`
+
+.. warning::
+   Disclaimer on unstable features you should NOT rely on.
+
+   For instance use the features ``step.behave_as`` and the **xunit
+   XML output** are unstable and untested.
+
+   Lettuce is a software for testing other software, but I've been
+   receiving some contributions of new features that are coming
+   without proper tests.
+
+   These contributions have to be rewritten with proper tests, so that
+   they won't break so often, but they are a current source of issues
+   in the bug tracker.
+
+   So until someone contributes with unit and functional tests for
+   those features, or I find some time to do it myself, you should
+   avoid relying on them.
+
+   Sincerely,
+   Gabriel Falcão