Dear Craigslist, seeking mortal foe. Have secret identity that nobody can know
Now hiring
Sometimes I work, sometimes I do my own thing. This weekend was one of those times that I mostly worked. I have been working on some large overarching projects which require a lot of work and are unfortunately the kind of projects that don't have a defined done point. So far it has gone super well. I have been able to get everything working that I wanted to get working some things are much more complicated than necesarry and some are much simplier. I'm generally a little obsessive and don't stop until I can get stuff to work. So this weekend we were mostly talking about SauceLabs.
One of the big things I needed to tackle was how to run robot on sauce labs. Unfortunately, it turned out the only tutorial that I could find for this I couldn't get to work. For whatever reason Selenium2Library seems to hate the version of robot or python or something. Whatever it was I finally gave up and decided to approach it like I was trying to pull two things together that no one else had pulled together. Techanically all robot is really doing is running python so it I could get it to work in python it only made sense that it should be equally workable in python run by robot.
The main problems with this over unittest.
I couldn't find a way to get a single run to generate all the tests for me.
I didn't set up naming well.
Perhaps great things:
It seems reasonably possible to generate all libraries this way.
There is a damn good library for running concurently. Unfortunately this library does break some stuff. It appears to get lost when it's looking for the files if we use a robot output directory. Perhaps I will look at solving this problem I haven't really thought about it at this point.
I also looked at ways to set the host file. Amazingly this appears to be super easy. It does look like it might be prudent to create a settings directory in QA for robot settings, executable settings, etc.
Tomorrow I will probably look into how to actually build a single instance that does all of these things. Perhaps wrapping the driver and changing create and close functions. We shall see tomorrow.