Robotframework logs in plain text?

[Janne Kohvakka]

Hi,

I seem to get this question of plain text Robot logs in my company every once and a while. Has anyone written a tool for generating human-readable plain text logs from output.xml?

Use case is mainly the ability to grep the plain text file without needing to click open the keywords in html log.

If nobody has done this, I will probably give it a try.

-Janne

[Janne Kohvakka]

Umm. Seems nobody has done this. I started to make this kind of tool and the prototype already works. You can see it in https://github.com/jkohvakk/popt. I would be happy to get ideas how to write some useful tests for this tool. Currently, there are basically none :-(.

-janne

[Tatu Aalto]

Ugh

Looks cool, thanks for sharing.

Because it parses the output.xml file, perhaps it would be good idea to collect   the output.xml from different versions of Robot Framework. Perhaps use RF acceptance tests output.xml file would be good idea, at least it is big enough. Then parse the files and verify that key parts are found correctly.

-Tatu
Send from my mobile

--
You received this message because you are subscribed to the Google Groups "robotframework-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-u...@googlegroups.com.
To post to this group, send email to robotframe...@googlegroups.com.
Visit this group at https://groups.google.com/group/robotframework-users.
For more options, visit https://groups.google.com/d/optout.

[Pekka Klärck]

Interesting idea! Instead of parsing the output.xml using ElementTree, you could consider using Robot's own modules for that:
http://robot-framework.readthedocs.org/en/master/autodoc/robot.result.html#module-robot.result

Sent from my mobile.

--

[Janne Kohvakka]

Thanks. I will do a parallel implementation with robot.result to see how it could work.

torstai 31. joulukuuta 2015 0.19.56 UTC+2 Pekka Klärck kirjoitti:

Interesting idea! Instead of parsing the output.xml using ElementTree, you could consider using Robot's own modules for that:
http://robot-framework.readthedocs.org/en/master/autodoc/robot.result.html#module-robot.result

Sent from my mobile.

30.12.2015 3.10 ip. "Janne Kohvakka" <jkoh...@gmail.com> kirjoitti:

Umm. Seems nobody has done this. I started to make this kind of tool and the prototype already works. You can see it in https://github.com/jkohvakk/popt. I would be happy to get ideas how to write some useful tests for this tool. Currently, there are basically none :-(.

-janne

tiistai 29. joulukuuta 2015 19.33.04 UTC+2 Janne Kohvakka kirjoitti:

Hi,

I seem to get this question of plain text Robot logs in my company every once and a while. Has anyone written a tool for generating human-readable plain text logs from output.xml?

Use case is mainly the ability to grep the plain text file without needing to click open the keywords in html log.

If nobody has done this, I will probably give it a try.

-Janne

--
You received this message because you are subscribed to the Google Groups "robotframework-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-users+unsub...@googlegroups.com.

[Pekka Klärck]

Notice that you can also use similar approach with --prerebotmodifier to get the log created as part of normal execution, or listeners to get it created already during execution. There's also --debugfile, but it flushes output it writes and thus can slow down execution. Flushing could be made optional and also debug file formatting enhanced, though.

Sent from my mobile.

2.1.2016 9.52 ap. "Janne Kohvakka" <jkoh...@gmail.com> kirjoitti:

Thanks. I will do a parallel implementation with robot.result to see how it could work.

torstai 31. joulukuuta 2015 0.19.56 UTC+2 Pekka Klärck kirjoitti:

Interesting idea! Instead of parsing the output.xml using ElementTree, you could consider using Robot's own modules for that:
http://robot-framework.readthedocs.org/en/master/autodoc/robot.result.html#module-robot.result

Sent from my mobile.

30.12.2015 3.10 ip. "Janne Kohvakka" <jkoh...@gmail.com> kirjoitti:

Umm. Seems nobody has done this. I started to make this kind of tool and the prototype already works. You can see it in https://github.com/jkohvakk/popt. I would be happy to get ideas how to write some useful tests for this tool. Currently, there are basically none :-(.

-janne

tiistai 29. joulukuuta 2015 19.33.04 UTC+2 Janne Kohvakka kirjoitti:

Hi,

I seem to get this question of plain text Robot logs in my company every once and a while. Has anyone written a tool for generating human-readable plain text logs from output.xml?

Use case is mainly the ability to grep the plain text file without needing to click open the keywords in html log.

If nobody has done this, I will probably give it a try.

-Janne

--
You received this message because you are subscribed to the Google Groups "robotframework-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-u...@googlegroups.com.

To post to this group, send email to robotframe...@googlegroups.com.
Visit this group at https://groups.google.com/group/robotframework-users.
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "robotframework-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-u...@googlegroups.com.

[Janne Kohvakka]

Thanks again. Any examples of --prerebotmodifyer? It seems to be a new feature of Robot 3.0. I need to think again if I want to use features of Robot for generating textual log - many people in my organization do not have Robot installed on their work computer but they anyway get the logs for analysis. It would be more handy for them to be able to produce the plain text output without dependency to Robot.

I already got another requirement despite whole thing being in prototype level: Include full paths of executed test cases and keywords to the textual log. This would be useful when wrestling with big legacy test suites as we are. As a default, output.xml only has the source path of the suite that was run. Is there any way to make it include source paths of test cases and keywords?

-Janne

lauantai 2. tammikuuta 2016 16.43.56 UTC+2 Pekka Klärck kirjoitti:

Notice that you can also use similar approach with --prerebotmodifier to get the log created as part of normal execution, or listeners to get it created already during execution. There's also --debugfile, but it flushes output it writes and thus can slow down execution. Flushing could be made optional and also debug file formatting enhanced, though.

Sent from my mobile.

2.1.2016 9.52 ap. "Janne Kohvakka" <jkoh...@gmail.com> kirjoitti:

Thanks. I will do a parallel implementation with robot.result to see how it could work.

torstai 31. joulukuuta 2015 0.19.56 UTC+2 Pekka Klärck kirjoitti:

Interesting idea! Instead of parsing the output.xml using ElementTree, you could consider using Robot's own modules for that:
http://robot-framework.readthedocs.org/en/master/autodoc/robot.result.html#module-robot.result

Sent from my mobile.

30.12.2015 3.10 ip. "Janne Kohvakka" <jkoh...@gmail.com> kirjoitti:

Umm. Seems nobody has done this. I started to make this kind of tool and the prototype already works. You can see it in https://github.com/jkohvakk/popt. I would be happy to get ideas how to write some useful tests for this tool. Currently, there are basically none :-(.

-janne

tiistai 29. joulukuuta 2015 19.33.04 UTC+2 Janne Kohvakka kirjoitti:

Hi,

I seem to get this question of plain text Robot logs in my company every once and a while. Has anyone written a tool for generating human-readable plain text logs from output.xml?

Use case is mainly the ability to grep the plain text file without needing to click open the keywords in html log.

If nobody has done this, I will probably give it a try.

-Janne

--
You received this message because you are subscribed to the Google Groups "robotframework-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-users+unsub...@googlegroups.com.

To post to this group, send email to robotframe...@googlegroups.com.
Visit this group at https://groups.google.com/group/robotframework-users.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "robotframework-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-users+unsub...@googlegroups.com.

[Pekka Klärck]

--prerebotmodifier is new in RF 2.9. More info and example here:
http://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#programmatic-modification-of-results

You can get test source simply from its parent suite. Keyword sources aren't available in output.xml. You can get them via import_xxx listener methods during execution:
http://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#listener-interface-methods

Sent from my mobile.

4.1.2016 8.59 ap. "Janne Kohvakka" <jkoh...@gmail.com> kirjoitti:

Thanks again. Any examples of --prerebotmodifyer? It seems to be a new feature of Robot 3.0. I need to think again if I want to use features of Robot for generating textual log - many people in my organization do not have Robot installed on their work computer but they anyway get the logs for analysis. It would be more handy for them to be able to produce the plain text output without dependency to Robot.

I already got another requirement despite whole thing being in prototype level: Include full paths of executed test cases and keywords to the textual log. This would be useful when wrestling with big legacy test suites as we are. As a default, output.xml only has the source path of the suite that was run. Is there any way to make it include source paths of test cases and keywords?

-Janne

lauantai 2. tammikuuta 2016 16.43.56 UTC+2 Pekka Klärck kirjoitti:

Notice that you can also use similar approach with --prerebotmodifier to get the log created as part of normal execution, or listeners to get it created already during execution. There's also --debugfile, but it flushes output it writes and thus can slow down execution. Flushing could be made optional and also debug file formatting enhanced, though.

Sent from my mobile.

2.1.2016 9.52 ap. "Janne Kohvakka" <jkoh...@gmail.com> kirjoitti:

Thanks. I will do a parallel implementation with robot.result to see how it could work.

torstai 31. joulukuuta 2015 0.19.56 UTC+2 Pekka Klärck kirjoitti:

Interesting idea! Instead of parsing the output.xml using ElementTree, you could consider using Robot's own modules for that:
http://robot-framework.readthedocs.org/en/master/autodoc/robot.result.html#module-robot.result

Sent from my mobile.

30.12.2015 3.10 ip. "Janne Kohvakka" <jkoh...@gmail.com> kirjoitti:

Umm. Seems nobody has done this. I started to make this kind of tool and the prototype already works. You can see it in https://github.com/jkohvakk/popt. I would be happy to get ideas how to write some useful tests for this tool. Currently, there are basically none :-(.

-janne

tiistai 29. joulukuuta 2015 19.33.04 UTC+2 Janne Kohvakka kirjoitti:

Hi,

I seem to get this question of plain text Robot logs in my company every once and a while. Has anyone written a tool for generating human-readable plain text logs from output.xml?

Use case is mainly the ability to grep the plain text file without needing to click open the keywords in html log.

If nobody has done this, I will probably give it a try.

-Janne

--
You received this message because you are subscribed to the Google Groups "robotframework-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-u...@googlegroups.com.

To post to this group, send email to robotframe...@googlegroups.com.
Visit this group at https://groups.google.com/group/robotframework-users.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "robotframework-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-u...@googlegroups.com.

To post to this group, send email to robotframe...@googlegroups.com.
Visit this group at https://groups.google.com/group/robotframework-users.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "robotframework-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-u...@googlegroups.com.