Tag Sauce Robot test jobs with test name and test status

[kahunacohen]

Need arises to tag sauce Robot jobs with at least test name and test status, otherwise sauce jobs are hard to browse on saucelabs.com. Making Page library a listener itself as per: http://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#test-libraries-as-listeners. Code in progress at:
https://github.com/ncbi/robotframework-pageobjects/blob/sauce-listener/robotpageobjects/base.py#L531

I have it now properly logging what it should. Just need to get communicating with Sauce. Remember for each test we want to initially tag the job with the test name, so that you can see the test is in progress and know what test it is. When it finishes, you want to tag that job with the status:

$ pybot test.robot 
==============================================================================
Test :: Some docs                                                             
==============================================================================
Test 1                                                                INFO - My Page - session ID: 8ae3fb7e4f8f4268a5b50885a513478a
.INFO - My Page - Tag sauce job 8ae3fb7e4f8f4268a5b50885a513478a with Test 1
Test 1                                                                | PASS |
------------------------------------------------------------------------------
INFO - My Page - Tag sauce job, 8ae3fb7e4f8f4268a5b50885a513478a with PASS
Test 2                                                                INFO - My Page - session ID: 493f09c78cbe46539363cca3f8ecace1
.INFO - My Page - Tag sauce job 493f09c78cbe46539363cca3f8ecace1 with Test 2
Test 2                                                                | PASS |
------------------------------------------------------------------------------
INFO - My Page - Tag sauce job, 493f09c78cbe46539363cca3f8ecace1 with PASS
Test :: Some docs                                                     | PASS |
2 critical tests, 2 passed, 0 failed
2 tests total, 2 passed, 0 failed
==============================================================================

@gluk-w, @frishberg, @hellmanj : I know gluk-w, wrote some code for a nose plugin to communicate with stash's Rest API using Sauce's module. We need to be able to share that between the core repo and the nose plugin. If the nose plugin is tied to robotframework-pageobjects then the easiest thing to do is have Stan contribute that plugin to this repo, and then we share the helper module. Thoughts?

If gluk-w, frishberg, hellman agree it's a question of where to put things.

[kahunacohen]

OK, got Robot tests tagging sauce jobs using saucerest. Since we can only tag jobs with session id, and we only have that once the browser opens, and since this can take a while in sauce, you won't see the job named tagged for a bit. But once the browser loads, you'll see the job tagged. Once the job is done, you'll see it either passed or failed in the Sauce UI.

https://github.com/ncbi/robotframework-pageobjects/blob/sauce-listener/robotpageobjects/base.py#L521

Still need to get nose plugin integrated. This makes me wonder...currently we don't require nose, since this rf-po is supposed to be ambivalent about frameworks apart from Robot. Perhaps we should either change that assumption and package nose with requirements.txt, or I should refactor Stan's code to use the more generic unittest's TestRunner and extend that. We'd then have to pass in options the standard rf-po way by using env vars. The latter seems more consistent with how we've been doing things. I hate to tie to nose given that it's no longer supported.

[dpsfrishberg]

I'd rather not require nose as a dependency. Could the nose plugin have its
own requirements?

On Fri, Mar 20, 2015 at 3:33 PM, kahunacohen notifications@github.com
wrote:

OK, got Robot tests tagging sauce jobs using saucerest. Since we can only
tag jobs with session id, and we only have that once the browser opens, and
since this can take a while in sauce, you won't see the job named tagged
for a bit. But once the browser loads, you'll see the job tagged. Once the
job is done, you'll see it either passed or failed in the Sauce UI.

https://github.com/ncbi/robotframework-pageobjects/blob/sauce-listener/robotpageobjects/base.py#L521

Still need to get nose plugin working. This makes me wonder...currently we
don't require nose, since this package is supposed to be ambivalent about
frameworks apart from Robot. Perhaps we should either change that
assumption and package nose with requirements, or I should refactor Stan's
code to use the more generic unittest's TestRunner and extend that. We'd
then have to pass in options the standard rf-po way by using env vars.

—
Reply to this email directly or view it on GitHub
#22 (comment)
.

[kahunacohen]

Not sure. Do you mean be a separate package from RF-PO? I was trying to avoid that too.

[dpsfrishberg]

Separate package in the same repository, is what I was thinking.... but
let's talk about it in person on Monday.

On Fri, Mar 20, 2015 at 3:47 PM, kahunacohen notifications@github.com
wrote:

Not sure. Do you mean be a separate package from RF-PO? I was trying to
avoid that too.

—
Reply to this email directly or view it on GitHub
#22 (comment)
.