summaryrefslogtreecommitdiffstats
path: root/features/images
Commit message (Collapse)AuthorAgeFilesLines
* Test suite: update expected picture for the Unsafe Browser homepage (refs: ↵intrigeri2019-08-301-0/+0
| | | | | | #17004) This is the Stretch version. It differs from the Buster version.
* Test suite: remove localized pictures of the Unsafe Browser homepage (refs: ↵intrigeri2019-08-304-0/+0
| | | | | | #17004) No language has this translated at the moment.
* Test suite: replace workaround for bug that's been fixed with proper ↵intrigeri2019-03-051-0/+0
| | | | | | | | | implementation (refs: #14596) commit:d2a67e7f7bcafdd22186a91f3b076a01797d1107 added the workaround and documented the bug but no ticket was filed back then. Thankfully anonym's review highlighted this problem as a probable bug in the code, which turned out to be the case; finally, the bug (#16475) was fixed.
* Test suite: update outdated picture (refs: #14596)intrigeri2019-01-251-0/+0
| | | | | | | | | | | | | The phrasing of the GUI has changed in t-p-s.git's commit 41252b861b2d3366a794d8d22808a067f9c1f19e, last April 27. Since then this test has kept passing only because of "Found fuzzy candidate picture for ASPPersistenceSetupOptionEnabled with similarity 0.8", which is actually a bug (fuzzy matching is supposed to be disabled by default in our test suite but for some reason, at least in some cases, it's enabled when it should not). So let's replace this picture with a current one.
* Merge remote-tracking branch 'origin/testing' into ↵intrigeri2019-01-251-0/+0
|\ | | | | | | test/14596-automated-tests-for-ASP-gui
| * Test suite: update image to match current expected one.intrigeri2019-01-131-0/+0
| | | | | | | | dkg has updated his key so the previous image does not match anymore.
* | Merge remote-tracking branch 'origin/stable' into ↵Alan2018-12-213-0/+0
|\ \ | |/ | | | | feature/14596-automated-tests-for-ASP-gui-on-stable
| * Test suite: update picture (refs: #14754)intrigeri2018-12-081-0/+0
| | | | | | | | | | This text is not bold anymore since iuk.git:267db7d253830625a4f3cf8562640cf53dc935fc.
| * Test suite: check for "Upgrading the system" and adjust to "Upgrade ↵intrigeri2018-11-203-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | successfully downloaded" new UI (#14754, #15282) First, let's test that the "Upgrading the system" dialog is displayed while applying an incremental upgrade. This test would have helped us notice earlier (instead of months, if not years, too late) that this dialog was not displayed anymore. Hopefully Sikuli is fast enough to catch it reliably: the IUK we're applying in the test suite is pretty small so this dialog is displayed only for a very short time. Second, take into account that we now prompt the user before applying the downloaded IUK. Based on work done by anonym <anonym@riseup.net> in commit:6e6798b5d037ac41012b08f786c488884c19c88a
* | Merge remote-tracking branch 'origin/stable' into ↵bertagaz2018-11-159-0/+0
|\ \ | |/ | | | | feature/14596-automated-tests-for-ASP-gui-on-stable
| * Merge branch 'stable' into test/14471-veracryptintrigeri2018-10-311-0/+0
| |\
| * | VeraCrypt test suite: give up on unmounting/locking via GNOME Files.intrigeri2018-09-141-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It is way too fragile. Nautilus will sometimes fire up a "Unable to eject 105 MB Volume" "Cannot eject drive in use: Encrypted device /dev/sda is unlocked" error dialog while according to the Journal, everything is correctly unmounted and locked by udisksd. There is probably a bug in Nautilus, GVfs, udisks, or the way they talk to each other. I've occasionally seen it for years with LUKS devices too, so this is not specific to VeraCrypt and outside of the scope of this project. So let's use udisksctl to unmount and lock VeraCrypt volumes instead. And as a consequence, no notification is displayed so instead of looking for one, let's verify that the volume was correctly unmounted (which we did already) and locked (which we did not do, we were believing the desktop notification).
| * | VeraCrypt test suite (file container): implement GNOME Disks scenarios ↵intrigeri2018-09-131-0/+0
| | | | | | | | | | | | | | | | | | (refs: #14471, #15239). Let's rename the file container to .img in order to simplify these tests.
| * | VeraCrypt test suite (USB drive): implement GNOME Disks scenarios (refs: ↵intrigeri2018-09-133-0/+0
| | | | | | | | | | | | #14471, #15238).
| * | VeraCrypt test suite (file container): implement steps for the initial ↵intrigeri2018-09-132-0/+0
| | | | | | | | | | | | scenario (refs: #15239).
| * | VeraCrypt test suite (USB drive): implement unlocking with Unlock VeraCrypt ↵intrigeri2018-09-135-0/+0
| | | | | | | | | | | | Volumes (refs: #15238).
* | | Merge remote-tracking branch 'origin/stable' into ↵bertagaz2018-10-231-0/+0
|\ \ \ | | |/ | |/| | | | feature/14596-automated-tests-for-ASP-gui-on-stable
| * | Don't break the test suite when changing the headline of /home (Will-fix: ↵sajolida2018-10-101-0/+0
| |/ | | | | | | | | | | | | | | | | | | | | | | #12156) The test suite needs a stable <title> but ikiwiki uses [[!meta title]] for both <title> and the page headline. This commit overwrites <title> using JavaScript. Using "Tails" as <title> is generic enough to make sense while preventing to have to handle translations.
* | Test suite: Add missing documentation step in ASP feature. (refs: #14596)bertagaz2018-09-101-0/+0
| | | | | | | | | | | | Catching the doucmentation window in the browser did not work for some reason, so it uses a screenshot to detect the right page has been opened.
* | Test suite: Add a step to the second scenario and fill some pending ones.bertagaz2018-09-101-0/+0
|/ | | | Refs: #14596
* Test suite: delete unused images.intrigeri2018-08-1930-0/+0
|
* Test suite: adjust to the fact "New Circuit for this Site" is now in the ↵intrigeri2018-08-192-0/+0
| | | | site information and not under the Torbutton anymore (refs: #15803).
* Merge remote-tracking branch 'origin/devel' into feature/14594-asp-guiintrigeri2018-08-1535-0/+0
|\
| * Merge branch 'test/15771-use-reliable-gnupg-key+force-all-tests' into devel ↵intrigeri2018-08-151-0/+0
| |\ | | | | | | | | | (Fix-committed: #15771)
| | * Test suite: use hopefully more reliable public GnuPG key (refs: #15771)intrigeri2018-08-081-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | So far we were using anonym's key, on the ground that he would maintain it and worst case, if he fails to keep it up-to-date, notice if automated tests start failing. This did not work: his key has expired a couple days ago. So let's switch to dkg's key and hope he'll maintain it better :) While I'm at it, let's use the full fingerprint instead of a short ID when feasible (dkg actually has published another key with the same short ID, most likely for demonstration purposes). But Seahorse does not support fetching keys by fingerprint so the corresponding steps keep using the short ID and I'm updating the expected picture to match the non-revoked one of these two keys.
| * | Test suite: fix the "Unsafe Browser can be used in all languages supported ↵intrigeri2018-08-094-0/+0
| | | | | | | | | | | | in Tails" test for locales that have a translated homepage (refs: #11711).
| * | Test suite: update Torbutton icon for Tor Browser 8 (refs: #15023)intrigeri2018-07-071-0/+0
| | |
| * | Test suite: make the audio test more robust (refs: #15023)intrigeri2018-07-051-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | I did not manage to make it robust enough with Firefox 60 and this test was never meant to exercise the HTML5 player: it was introduced (commit:136db50c290dd2c13392f3493ad518e6c969fa56) to ensure our AppArmor confinement for Tor Browser did not break audio playback, so let's do this and not more, just like we're doing for the video test as well.
| * | Test suite: update Unsafe Browser proxy tests for Firefox 60 (refs: #15023)intrigeri2018-07-0515-0/+0
| | | | | | | | | | | | … and factorize a bunch of lines in passing.
| * | Test suite: update image for Tor Browser 8 (refs: #15023)intrigeri2018-07-051-0/+0
| | |
| * | Test suite: handle the fact that the browser address bar is initialized ↵intrigeri2018-07-051-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | lazily (refs: #15023) Initially it says "Search or enter address" and after some actions it says "Search with DuckDuckGo or enter address", both in Tor Browser, Unsafe Browser, and Tor Browser 8.0a9 outside of Tails.
| * | Test suite: adapt file saving dialog to Firefox 60 (refs: #15023)intrigeri2018-07-033-0/+0
| | | | | | | | | | | | … and incidentally, this image can be used by future tests of other GTK3 apps.
| * | Test suite: make image reusable.intrigeri2018-07-031-0/+0
| | | | | | | | | | | | That's the standard GTK3 print button, not a specific Evince one.
| * | Test suite: try to make "I open the address" more robust.intrigeri2018-07-032-0/+0
| | | | | | | | | | | | | | | | | | I see it succeed too fast, presumably because the Reload button is displayed for a little bit, after pressing Enter, before it's replaced by the Stop button while the page is loaded, and finally reappears.
| * | Test suite: make image reusable.intrigeri2018-07-031-0/+0
| | | | | | | | | | | | | | | It's actually the same dialog for all GTK3 apps and e.g. Tor Browser 8 can now reuse it.
| * | Test suite: update images for Firefox 60 (refs: #15023)intrigeri2018-07-033-0/+0
| | |
| * | Test suite: take into account that the Reload button now looks different in ↵intrigeri2018-07-032-0/+0
| | | | | | | | | | | | | | | | | | the Unsafe Browser than in Tor Browser (refs: #15023) It has the red theme applied.
| * | Test suite: update image for Firefox 60 (refs: #15023)intrigeri2018-07-031-0/+0
| |/
* | Merge remote-tracking branch 'origin/feature/15554-linux-4.15.0-3' into ↵sajolida2018-04-282-0/+0
|\ \ | |/ | | | | feature/14594-asp-gui
| * Test suite: delete unused image (refs: #15336)intrigeri2018-04-141-0/+0
| | | | | | | | | | The last use case for this image was removed in commit:0cf89c9d04b4d73436b9ed1cff730d0faa520393.
| * Merge remote-tracking branch 'origin/stable' into ↵anonym2018-04-0612-0/+0
| |\ | | | | | | | | | test/14935-dogtailify-tor-browser
| * | Test suite: use Dogtail instead of image.anonym2018-02-201-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This image was invalidated during our Donation campaign was running, and then by a Tor Browser bug (#14962). Bumping images is boring so let's rely on Dogtail instead. To make this scenario more robust we also switch to something else than the start page, and restart the browser between save/open in order to prevent Dogtail e.g. finding the old page that we just saved instead of the saved version we just opened. Refs: #14935, #14962
* | | WIP: update test suite for new Persistent Wizard UI (refs: #6485, #15259, ↵intrigeri2018-03-041-0/+0
| |/ |/| | | | | | | | | | | | | | | | | #15314). The tails-persistence-setup UI has changed in a number of ways: - some setting lines now have a "Configure" button - custom widgets were replaced with standard GNOME ones - a "preset" can now map to N lines in persistence.conf
* | Merge remote-tracking branch 'origin/feature/15022-electrum-3.0.6' into develanonym2018-02-289-0/+0
|\ \ | | | | | | | | | Fix-committed: #15022
| * | Test suite: dogtailify electrum.feature.anonym2018-02-269-0/+0
| |/ | | | | | | | | | | | | | | Upgrading to 3.x requires non-trivial modifications, so I took the (slight) extra time to make us less dependent on future changes (and possibly solving robustness issues for free). Refs: #15022, #10475, #11697
* | Test suite: Dogtailify.anonym2018-02-203-0/+0
|/
* Test suite: adapt for Tor Launcher 0.2.14.3.anonym2018-01-206-0/+0
| | | | | | I.e. the one shipped with Tor Browser 7.5. Will-fix: #15064
* Test suite: bump TailsHomepage.png.anonym2017-12-081-0/+0
| | | | | Looks like a slight font change, probably related to anti-aliasing, was introduced when we imported Tor Browser 7.0.10-build2.
* Test suite: bump the Unsafe Browser's start page image.anonym2017-12-081-0/+0
| | | | Will-fix: #15006
* Test suite: de-duplicate step and test suite image.anonym2017-12-081-0/+0
|