Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium

New issue 1400 by [email protected]: Robot logs should show whole keyword documentation
http://code.google.com/p/robotframework/issues/detail?id=1400


I have e.g. Python lib with keywords with proper documentation. E.g. below:

    def summary_views_for_reporting_should_exist(self):
        """This keyword is checking that *Summary VIEWS for Reporting*
for adaptation are existing and correctly named in database according
        to given test data.

In AD document checked target is *Summary View for Reporting* column.
        | E.g. NOKLTE_PS_LCELLD_<Object>_<Time>
        | I.e. actually many views as test target (time and object levels).
        | All are checked.

Test data and database views (metadata) are compared to both directions
        i.e. both missing and extra views are reported as errors.
        """

But when tests are runned, Robot's log will show only First line of that documentation.

--clip--
KEYWORD: MetadataTester.Summary Views For Reporting Should Exist
Documentation:  
This keyword is checking that Summary VIEWS for Reporting
Start / End / Elapsed: 20130331 23:49:45.128 / 20130331 23:49:45.456 / 00:00:00.328
--clip--

I would be good to show whole documentation as I don't want to always repeat the same doc in test suite keyword.

Btw. It would be also nice feature if docs of keywords could be aggregated (copied) to upper level. E.g. if test suite keyword(or test case) calls only one keyword from lib, then it would be nice to get that's library's keyword documentation to be shown in test suite's keyword documentation somehow easily.

RF version 2.7.7

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--

--- 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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to