Right now it shows a placeholder.

Because it's hard to upgrade chrome on the Windows image to a version compatible with the chromedriver we're shipping, wait until it's available natively:

https://github.com/Microsoft/azure-pipelines-image-generation/issues/307

RobotLab is big and likely to get bigger as more cool features need more (exotic) dependencies.

We could just as easily spin a couple different intstallers a la Miniconda/Anaconda in CI.

MicrobotLab 🔬

• for CI environments
  • you'll already have browsers, etc. hopefully
• don't even ship conda (pip usually works, right? and conda is showing up on more CIs)

RobotLabLite 🔍

• still a full working environment
• cut it down to the bone (opencv, nodejs, pandoc), and even repackage some things (jupyterlab assets)
• still ship conda so you can upgrade stuff

RobotLab 🔭

• as it is now!
  • even shipping Firefox is great!
• this is ideal for the original intent of training on non-trivial things, where the setup of some of the things have proven (really hard for people to install](https://stackoverflow.com/search?q=opencv+install).

RobotHub 📡

• ship a whole littlest jupyter hub
  • why not?

Hi
Can I upgrade Robot Framework version to the newest one? Can I also update the Selenium library to the newest one?
I tried to use pip and update Robot Framework but the functionality was not there anymore.

Also is it possible to install new functionality to RobotLab? QWeb seems quite interesting and it would have some nice features for browser testing.
Br
-Lauri

Hello, I just installed Robotlab to my computer and everything else is working very well, except for some reason I can't use Selenium keywords. Do you have any idea what might cause this?

The example notebooks are already packaged as part of robotlab into \var\www\robotkernel-examples, but are hard to find.

There should also be an easy-to-use script to copy them (and any supporting stuff) into a given directory so that they are easy to find and try out.

The acceptance tests should then verify that they function properly. This will also uncover ermergent example dependencies (additional libraries, etc). At present, RESTInstance is the long pole...

Linux looks fine, but the win installer's shortcut doesn't, as I use relative imports on launch, which doesn't work the way it is invoked. Working on a fix!

Is there a hook in Jupyter that would allow us to import a raw source file?

Sure a good experience would not be trivial, because we should split the source into cells in some sane way. It could require parsing and generating the file.

I have no particular driver for this change, as 3.6 doesn't EOL for a good long time now, but the performance improvements might be worth it.

How much work it would be build also version for 32bit Windows, just in case?

The latest pull did merge as green, so we are ready to tag and release 1.0rc1. I guess, I could still do this one manually.

I’ve done small refresh for https://robots-from-jupyter.github.io/ also.

https://pypi.org/project/robotframework-imagelibrary/

Requires OpenCV and Tesseract OCR both which may be hard to install elsewhere.

Updates

• robotframework-seleniumlibrary 4.1.0
• robotkernel 1.1 (unreleased)

Additions

• robotframework-seleniumtestability > 0.0.15 (unreleased, a lot of changes in master since 0.0.15)
• jupytext 1.3.0 (supports Robot Framework)

What else?

Gotta keep up-to-date!

When i run RobotLab it give me error "'chcp' is not recognized as an internal or external command"

Hi
Is this doable? Does RobotLab produce same kind of result files as vanilla Robot Framework? Where can I find the test result logs?
Thanks

Congratulations on the robotkernel 1.0 release @datakurre! 🙌

To coincide with that, we should get a new build out of RobotLab: sorry I haven't been more help on the previous attempts this summer! But it's back to 🏫 now, let's build some Labs!

upstreams

• jupyterlab 1.1.3 is shaking out to be a pretty solid release after some hiccups up front... there will be no support for the 0.35 line to come, and 1.0.x might not get much more love, either.
• restinstance 1.0.2 is out, and not a pre-release, so could probably go ahead and start conda-forgeing it
  • same with robotkernel, if you'd like

build chain

• constructor can do noarch packages now (and got rid of the bzip dependency, which has actually caused me troubles)
  • we can shed a lot of recipes in the first place
  • we can build some of the remaining ones just on linux, and reuse them on osx/windows
• conda run is back in conda 4.7, which makes the headache of getting $PATH (or more specifically, %PATH% #39) right less horrible
  • need to investigate what this means for pyshortcuts, or if we can get rid of them altogether
• all the azure hosted instances just comes with conda now, so it will be less tedious to get set up

xyzdriver

• still a mess 🤕
• geckodriver 1.0 is probably the next release, and will probably still work for a few years' worth of browsers
• chromedriver.... bah... maybe we just tell people to use firefox :P

version

I would hesitate to call any RobotLab build a 1.0, so i propose adopting a different versioning scheme for RobotLab, e.g. 2019.9.0... if we put out more than one in a month, hooray, but otherwise not so much trouble.

will do some more thinking (and then some actual doing)...

Today @ju55i tested robotlab installer https://dev.azure.com/nickbollweg/nickbollweg/_build/results?buildId=99 on OSX

Only issue was that the proper way to launch the robotlab was unclear.

Installer prompts about updating bashrc, but that could be something that not everyone wants. Besides that Jussi was using zsh and the source-command proposed by the installer did not update PATH (so neither robotlab nor geckodriver/chromedriver was on path).

After manually setting PATH to robotlab/bin everything worked as expected.

It would be convinient to be able to use robotlab in an IDE.
Visual studio has support for jupyter but i cant find a way to make it understand robot syntax.

The robot framework lexer currently in Pygments does not support *** Tasks ***.

https://pypi.org/project/robotframeworklexer/ has been updated, but obviously is not yet merged or in downstream in pygments.

Probably adding robotframeworklexer == 1.1 into robotlab would be enough and HTML files exported from robotlab would then highlight tasks properly.

Let's get the band back together!

There have been so many nice things published recently that it's worth warming this back up.

Some ideas (please feel free to add more):

Packages

Infra

• adapt build from gt-coarl-lab
  • use doit
  • use GitHub Actions (it actually generates most of the workflow scripts)

for posterity:

Hooray JupyterLab 2.0!

https://pypi.org/project/jupyterlab/2.0.0/

Looks like RF 3.2 is also dangerously close:

https://github.com/robotframework/robotframework/milestone/48

It may also be worth considering moving to python 3.8, as the whole Jupyter stack (at least) is good to go on windows (that was a mess 😝)

I can't commit to a bunch of time to move the ball forward right now, but am going to start tinkering on various things (like jupyterlab-starters) so that we're in a better spot when it's go-time.

Steps

1. install RobotLab on Windows
2. start RobotLab
3. File => New => Terminal

Expected

Terminal session opens

What actually happens

Terminal session opens and closes so fast that I'm unable to see what happens.

RobotLab launch terminal printed the following

[I 23:18:00.308 LabApp] EOF on FD 2688; stopping reading
[I 23:18:00.526 LabApp] Terminal 1 closed
TermSocket.open: 1
[I 23:18:00.526 LabApp] New terminal with specified name: 1
TermSocket.open: Opened 1
Exception in thread Thread-16:
Traceback (most recent call last):
  File "C:\Users\user\RobotLab\lib\threading.py", line 916, in _bootstrap_inner
    self.run()
  File "C:\Users\user\RobotLab\lib\threading.py", line 864, in run
    self._target(*self._args, **self._kwargs)
  File "C:\Users\user\RobotLab\lib\site-packages\winpty\ptyprocess.py", line 331
, in _read_in_thread
    data = pty.read(4096)
  File "C:\Users\user\RobotLab\lib\site-packages\winpty\winpty_wrapper.py", line
 73, in read
    ReadFile(self.conout_pipe, data, length, None, None)
OSError: exception: access violation writing 0x0000000000000000

[I 23:18:00.761 LabApp] EOF on FD 2680; stopping reading
[I 23:18:00.980 LabApp] Terminal 1 closed

We'll need to pin to <4 to get the release out.

Is there an option to set proxy for systems behind a company firewall?

Not super high value for the workshop, but how does this hit you?

Looks pretty straightforward:

https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/github-release?view=vsts

Probably just do it on tags, need to find some good examples.