-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi devs,
we're making some medium-term plans to produce automated screencasts that explain how to download, verify, and run Tor Browser on Windows, Mac OS X, and Linux, localized to at least half a dozen languages.
The focus here is really on *automated*. Whenever there's a new Tor Browser version, we'd like to minimize manual steps for creating new screencasts to the absolute minimum.
Here's our plan, and we'd appreciate your feedback on this:
1. Set up three systems (Windows, Mac OS X, and Linux) either as virtual machines, using VirtualBox or VMware Fusion, or on a dedicated triple-boot Mac Mini.
2. Install Sikuli (http://www.sikuli.org/; thanks for Lunar for the suggestion!) either directly on these machines or on the virtual machine host or on a separate host in the same network.
3. Write a Sikuli script for each operating system and language, probably re-using large parts, to make all the necessary steps to download, verify, and run Tor Browser. This script may include steps for preparing the system by changing its language and for cleaning up afterwards. Ideally, this script can easily be maintained whenever Tor Browser changes.
4. Record audio snippets in the various language that explain the steps that will later be performed in the screencast. Either include these as part of the Sikuli script, or put them together separately and add them to the recording later.
5. Start a screen recorder and run the Sikuli script for all three systems and all supported languages.
6. Post-process the recording by cutting the video, attaching the audio, and possibly adding text slides at beginning and end; hopefully using scripts.
Again, the goal is to keep the overhead for recording a new set of screencasts as low as possible. If it takes days to do this, nobody will do it, and we'll soon have outdated videos.
What do you think about this plan? And do you have specific suggestions for the single steps?
Thanks!
Cheers, Karsten and Sherief
Hi!
Karsten Loesing:
- Install Sikuli (http://www.sikuli.org/; thanks for Lunar for the
suggestion!) either directly on these machines or on the virtual machine host or on a separate host in the same network.
- Write a Sikuli script for each operating system and language,
probably re-using large parts, to make all the necessary steps to download, verify, and run Tor Browser. This script may include steps for preparing the system by changing its language and for cleaning up afterwards. Ideally, this script can easily be maintained whenever Tor Browser changes.
I had a quick chat with intrigeri based on their experience with using Sikuli to automate Tails testing. He told me they had issues with the OCR system and that they opted for having captured images everywhere in the end. Having to update images on new Debian releases is a bit of a pain but seems to be a manageable exercice.
It saddens me a bit because having working OCR would be super awesome in that the same script could be used for multiple languages by looking at the actual software translation catalogs… So it might be worth experimenting a little bit again.
- Record audio snippets in the various language that explain the
steps that will later be performed in the screencast. Either include these as part of the Sikuli script, or put them together separately and add them to the recording later.
I think it's worth experimenting a little bit with starting the audio tracks as part of the script. It would make it easier to put synchronisation point in the script, and it might smooth out timings in different languages more nicely.
Are there scripts (as in a textual description of the scenes and voice over) already written down somewhere?
Hi,
Karsten Loesing wrote (19 Mar 2015 10:04:56 GMT) :
- Start a screen recorder and run the Sikuli script for all three
systems and all supported languages.
The Tails automated test suite uses cucumber to drive Sikuli and libvirt virtual machines. It is able to record the screen on video.
Note that last time we checked, Sikuli's OCR was too fragile for us so we look for images instead. But this was 2 years ago, so maybe things have improved since.
Design doc: https://tails.boum.org/contribute/release_process/test/automated_tests/
Example cucumber feature: https://git-tails.immerda.ch/tails/tree/features/torified_browsing.feature?h...
The script to run it is: https://git-tails.immerda.ch/tails/tree/run_test_suite?h=stable
The Sikuli glue code lives there: https://git-tails.immerda.ch/tails/tree/features/support/helpers/sikuli_help...
Cheers, -- intrigeri