about summary refs log tree commit diff
path: root/tests/aszlig
Commit message (Collapse)AuthorAgeFilesLines
* flameshot: Rebase patch against version 11.0.0aszlig2022-02-091-2/+5
| | | | | | | | | | | | | | | | | | This is a major upstream release which deprecates a few of our options but also made our patch a little longer because the tools we remove are now defined in multiple places. The patch itself is pretty much doing the same things as before we do have one thing that is different, which is that we now create the savePath directory if it doesn't exist. I do know that this doesn't necessary need to be a directory but in the way I'm using flameshot it is, so I don't care ;-) While at it, I also disabled the checkForUpdates option, because this has annoyed me for some time and I really don't care if the version is the latest for a screenshot utility. Signed-off-by: aszlig <aszlig@nix.build>
* tests: Fix running background command for PSI testaszlig2021-11-071-1/+1
| | | | | | | | | | | | | | | | | Recently, the implementation behind Machine.execute() and thus also Machine.succeed() has been changed[1] to pipe all the command's output into base64 on the guest machine. Unfortunately this means that base64 is blocking until stdout is closed, which in turn means that we now need to make sure that whenever we run a program in background via "&" we also need to make sure to close stdout. In the PSI test, we're doing this by simply redirecting the output to stderr. [1]: https://github.com/NixOS/nixpkgs/pull/142747 Signed-off-by: aszlig <aszlig@nix.build>
* tests/psi: Work around OCR recognition failureaszlig2021-03-091-1/+1
| | | | | | | | | | | | For some reason I currently don't have time to investigate, the test has stopped to recognise the "Register new account" text, because the text extracted via OCR was "Reg ster new account" (note: without the "i"). Since we're not testing OCR in general and all we really care here in the test is whether the application starts up, I just changed the "i" to a "." (any character in regex) to make sure the detection passes. Signed-off-by: aszlig <aszlig@nix.build>
* profiles/workstation: Add Flameshotaszlig2021-02-131-0/+26
| | | | | | | | | | | So far I've almost exclusively used scrot for screenshots, but most of the time I used an image manipulation program to pixelate stuff, add descriptions or draw arrows. Flameshot combines this in a single application, so I expect that from now on I can spam-post screenshots in even a higher rate than before ;-) Signed-off-by: aszlig <aszlig@nix.build>
* tests: Switch all tests to Python test driveraszlig2020-08-292-82/+74
| | | | | | | | | | | | | | | | | | | | | Since the removal[1] of the Perl test driver, our tests will no longer run or even evaluate. Fortunately, the test API is more or less the same, so the transition to Python was not very involved. However, I did add a "# fmt: off" on top of every testScript, since formatting with black not only has issues with parameterised antiquotations but is also plain ugly to mix 2 spaces of indentation with 4 spaces of indentation. Additionally, I'd like to have a maximum line length of 79 characters in my Nix expressions while black on the other side even *insists* of using longer lines. [1]: https://github.com/NixOS/nixpkgs/commit/0620184f3f94f1bf8de014ab168 Signed-off-by: aszlig <aszlig@nix.build>
* Fix deprecated displayManager.auto.enable optionaszlig2020-02-101-2/+1
| | | | | | | | | | | | | | | | Since a while[1], the services.xserver.displayManager.auto option is deprecated. Since first of all SLiM got removed and now every display manager supports auto-login, I switched the labtops module to use the LightDM implementation. Since the common x11 test module still exposes a similar interface, we only need to use the same options from the test-support option, which should hopefully be a "sane default" suitable for tests. [1]: https://github.com/NixOS/nixpkgs/commit/c95612a5a2d4bd93011c042066c Signed-off-by: aszlig <aszlig@nix.build> Cc: @Profpatsch
* pkgs/psi: Fix Qt5 application wrappingaszlig2019-09-231-0/+26
| | | | | | | | | | | | | Qt applications are no longer implicitly wrapped since a while[1] and so we new have to use wrapQtAppsHook instead, which also makes the wrapping for Psi obsolete. To make sure we don't run into startup errors again, I added a small VM test, which checks whether the application starts up properly. [1]: https://github.com/NixOS/nixpkgs/commit/f79fd2e826dd95b3b64839d3e0bec8ae1dfab17e Signed-off-by: aszlig <aszlig@nix.build>
* tests/luks2-bcache: Wait for cache deviceaszlig2019-06-111-0/+4
| | | | | | | | | | | | | | | | | | | | | | When chomping the cache set UUID introduced in 6ae9056a5a82dd16b745188a7ee6122ed27239f0, this actually has brought a bug to surface, because when the UUID wasn't chomped the cache device hasn't been attached at all, because the resulting command looked like this: echo f994bcca-8e52-4b54-9c96-5f5af0711b55 > /sys/block/$bcache1/bcache/attach Yes, that's a newline after the echo, so it's just echoing the UUID and then writes *nothing* into /sys/block/$bcache1/bcache/attach. Chomping the UUID now results in an error, because the attach is made directly after creating the device. So all we need to do here is wait until the cache device was registered and then do the attach. Signed-off-by: aszlig <aszlig@nix.build>
* tests/luks2-bcache: Add missing chomp on $csetuuidaszlig2019-06-111-0/+1
| | | | | | | | This is just a minor nitpick and doesn't actually change a lot in functionality, but I chomped all the other occasions, so let's be consistent here as well. Signed-off-by: aszlig <aszlig@nix.build>
* machines/dnyarri: Enable bcache kernel moduleaszlig2018-12-241-0/+127
| | | | | | | | | | | | | | | Since I got a new SSD for the machine (thanks @cvdnext), I also had the opportunity to re-create my LUKS containers to LUKS2 with Argon2 key derivation alongside creating bcache backing devices. The change in order to support bcache is just a matter of adding "bcache" to availableKernelModules and we're done. However, as the storage configuration is not a very common one, I decided to add a test specific to that to make sure future NixOS updates won't prevent the machine from booting. Signed-off-by: aszlig <aszlig@nix.build>
* tests: Remove dummy test for i3aszlig2016-05-281-41/+0
| | | | | | | | | | | | We already have an "i3wm" test in upstream <nixpkgs> which is much more thorough than the unfinished test I've made here. The intention of this test however was to specifically test the Vuizvui service module. Nevertheless, it's still just a dummy test and the "i3wm" test works much better, so let's remove it until we have a more complete implementation. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* Handle all <nixpkgs> paths with nixpkgs-path.nix.aszlig2015-04-291-1/+3
| | | | | | | | | This file is just defaulting to <nixpkgs>, but we're going to substitue it by the channel generator. We also need to make sure that we don't have any other references to <nixpkgs>, but the latter can best be done on Hydra's side if we don't make <nixpkgs> available to vuizvui builds. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* tests/i3: Define a "first" test workspace.aszlig2015-04-081-1/+9
| | | | | | | | It's mainly to test whether the workspace assignment is done correctly and if not, the screenshot on the test will be showing one of the default workspaces instead. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* tests: Refactor to something similar as machines/.aszlig2015-03-181-2/+4
| | | | | | | | | Similar to callMachine, we now have callTest. The latter uses make-test.nix, so we don't need to import the file explicitly anymore and can just write our VM test by using either an attrset or a lambda function which also gets our own packages in a vuizvui namespace. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* tests: Properly namespace the VM tests.aszlig2015-03-181-0/+29
We're going to write much more tests and don't want to clutter up the tests/ directory. Signed-off-by: aszlig <aszlig@redmoonstudios.org>