Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate testing repo #5189

Merged
merged 1 commit into from
Oct 20, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
51 changes: 51 additions & 0 deletions .github/workflows/desktop-e2e.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
name: Desktop - End-to-end tests
on:
schedule:
- cron: '0 0 * * *'
workflow_dispatch:
jobs:
e2e-test-linux:
name: Linux end-to-end tests
runs-on: [self-hosted, desktop-test, Linux] # app-test-linux
timeout-minutes: 240
strategy:
fail-fast: false
matrix:
os: [debian11, debian12, ubuntu2004, ubuntu2204, ubuntu2304, fedora38, fedora37, fedora36]
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Run end-to-end tests
shell: bash -ieo pipefail {0}
run: |
./test/ci-runtests.sh ${{ matrix.os }}
e2e-test-windows:
name: Windows end-to-end tests
runs-on: [self-hosted, desktop-test, Linux] # app-test-linux
timeout-minutes: 240
strategy:
fail-fast: false
matrix:
os: [windows10, windows11]
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Run end-to-end tests
shell: bash -ieo pipefail {0}
run: |
./test/ci-runtests.sh ${{ matrix.os }}
e2e-test-macos:
name: macOS end-to-end tests
runs-on: [self-hosted, desktop-test, macOS] # app-test-macos-arm
timeout-minutes: 240
strategy:
fail-fast: false
matrix:
os: [macos-14, macos-13, macos-12]
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Run end-to-end tests
shell: bash -ieo pipefail {0}
run: |
./test/ci-runtests.sh ${{ matrix.os }}
2 changes: 2 additions & 0 deletions talpid-platform-metadata/src/lib.rs
Original file line number Diff line number Diff line change
Expand Up @@ -14,4 +14,6 @@ mod imp;
#[path = "android.rs"]
mod imp;

#[cfg(windows)]
pub use self::imp::WindowsVersion;
pub use self::imp::{extra_metadata, short_version, version};
2 changes: 1 addition & 1 deletion talpid-platform-metadata/src/windows.rs
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ pub fn extra_metadata() -> impl Iterator<Item = (String, String)> {
std::iter::empty()
}

struct WindowsVersion {
pub struct WindowsVersion {
inner: RTL_OSVERSIONINFOEXW,
}

Expand Down
2 changes: 2 additions & 0 deletions test/.cargo/config.toml
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
[target.'cfg(target_os = "windows")']
rustflags = ["-Ctarget-feature=+crt-static"]
6 changes: 6 additions & 0 deletions test/.gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
/target
/packages
/os-images
/testrunner-images
/.ci-logs
/config.json
237 changes: 237 additions & 0 deletions test/BUILD_OS_IMAGE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,237 @@
This document explains how to create base OS images and run test runners on them.

For macOS, the host machine must be macOS. All other platforms assume that the host is Linux.

# Configuring a user in the image

`test-manager` assumes that a dedicated user named `test` (with password `test`) is configured in any guest system which it should control.
Also, it is strongly recommended that a new image should have passwordless `sudo` set up and `sshd` running on boot,
since this will greatly simplify the bootstrapping of `test-runner` and all needed binary artifacts (MullvadVPN App, GUI tests ..).
The legacy method of pre-building a test-runner image is detailed [further down in this document](#).

# Creating a base Linux image

These instructions use Debian, but the process is pretty much the same for any other distribution.

On the host, start by creating a disk image and installing Debian on it:

```
wget https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-11.5.0-amd64-netinst.iso
mkdir -p os-images
qemu-img create -f qcow2 ./os-images/debian.qcow2 5G
qemu-system-x86_64 -cpu host -accel kvm -m 4096 -smp 2 -cdrom debian-11.5.0-amd64-netinst.iso -drive file=./os-images/debian.qcow2
```

## Dependencies to install in the image

`xvfb` must be installed on the guest system. You will also need
`wireguard-tools` and some additional libraries. They are likely already
installed if gnome is installed.

### Debian/Ubuntu

```bash
apt install libnss3 libgbm1 libasound2 libatk1.0-0 libatk-bridge2.0-0 libcups2 libgtk-3-0 wireguard-tools xvfb
```

### Fedora

```bash
dnf install libnss3 libgbm1 libasound2 libatk1.0-0 libatk-bridge2.0-0 libcups2 libgtk-3-0 wireguard-tools xorg-x11-server-Xvfb
```

# Creating a base Windows image

## Windows 10

* Download a Windows 10 ISO: https://www.microsoft.com/software-download/windows10

* On the host, create a new disk image and install Windows on it:

```
mkdir -p os-images
qemu-img create -f qcow2 ./os-images/windows10.qcow2 32G
qemu-system-x86_64 -cpu host -accel kvm -m 4096 -smp 2 -cdrom <YOUR ISO HERE> -drive file=./os-images/windows10.qcow2
```

(For Windows 11, see the notes below.)

## Windows 11

* Download an ISO: https://www.microsoft.com/software-download/windows11

* Create a disk image with at least 64GB of space:

```
mkdir -p os-images
qemu-img create -f qcow2 ./os-images/windows11.qcow2 64G
```

* Windows 11 requires a TPM as well as secure boot to be enabled (and thus UEFI). For TPM, use the
emulator SWTPM:

```
mkdir -p .tpm
swtpm socket -t --ctrl type=unixio,path=".tpm/tpmsock" --tpmstate ".tpm" --tpm2 -d
```

* For UEFI, use OVMF, which is available in the `edk2-ovmf` package.

`OVMF_VARS` is used writeable UEFI variables. Copy it to the root directory:

```
cp /usr/share/OVMF/OVMF_VARS.secboot.fd .
```

* Launch the VM and install Windows:

```
qemu-system-x86_64 -cpu host -accel kvm -m 4096 -smp 2 -cdrom <YOUR ISO HERE> -drive file=./os-images/windows11.qcow2 \
-tpmdev emulator,id=tpm0,chardev=chrtpm -chardev socket,id=chrtpm,path=".tpm/tpmsock" -device tpm-tis,tpmdev=tpm0 \
-global driver=cfi.pflash01,property=secure,value=on \
-drive if=pflash,format=raw,unit=0,file=/usr/share/OVMF/OVMF_CODE.secboot.fd,readonly=on \
-drive if=pflash,format=raw,unit=1,file=./OVMF_VARS.secboot.fd \
-machine q35,smm=on
```

## Notes on local accounts

Logging in on a Microsoft account should not be necessary. A local account is sufficient.

If you are asked to log in and there is no option to create a local account, try to disconnect
from the network before trying again:

1. Press shift-F10 to open a command prompt.
1. Type `ipconfig /release` and press enter.

If you are forced to connect to a network during the install, and cannot opt to use a local account,
do the following:

1. Press shift-F10 to open a command prompt.
1. Type `oobe\BypassNRO` and press enter.

# Creating a testrunner image (Legacy method)

The [build-runner-image.sh](./scripts/build-runner-image.sh) script produces a
virtual disk containing the test runner binaries, which must be mounted when
starting the guest OS. They are used `build-runner-image.sh` assumes that an environment
variable `$TARGET` is set to one of the following values:
`x86_64-unknown-linux-gnu`, `x86_64-pc-windows-gnu` depending on which platform
you want to build a testrunner-image for.

## Bootstrapping test runner (Legacy method)

### Linux

The testing image needs to be mounted to `/opt/testing`, and the test runner needs to be started on
boot.

* In the guest, create a mount point for the runner: `mkdir -p /opt/testing`.

* Add an entry to `/etc/fstab`:

```
# Mount testing image
/dev/sdb /opt/testing ext4 defaults 0 1
```

* Create a systemd service that starts the test runner, `/etc/systemd/system/testrunner.service`:

```
[Unit]
Description=Mullvad Test Runner

[Service]
ExecStart=/opt/testing/test-runner /dev/ttyS0 serve

[Install]
WantedBy=multi-user.target
```

* Enable the service: `systemctl enable testrunner.service`.

### Note about SELinux (Fedora)

SELinux prevents services from executing files that do not have the `bin_t` attribute set. Building
the test runner image stripts extended file attributes, and `e2tools` does not yet support setting
these. As a workaround, we currently need to reapply these on each boot.

First, set `bin_t` for all files in `/opt/testing`:

```
semanage fcontext -a -t bin_t "/opt/testing/.*"
```

Secondly, update the systemd unit file to run `restorecon` before the `test-runner`, using the
`ExecStartPre` option:

```
[Unit]
Description=Mullvad Test Runner

[Service]
ExecStartPre=restorecon -v "/opt/testing/*"
ExecStart=/opt/testing/test-runner /dev/ttyS0 serve

[Install]
WantedBy=multi-user.target
```

### Windows

The test runner needs to be started on boot, with the test runner image mounted at `E:`.
This can be achieved as follows:

* Restart the VM:

```
qemu-system-x86_64 -cpu host -accel kvm -m 4096 -smp 2 -drive file="./os-images/windows10.qcow2"
```

* In the guest admin `cmd`, add the test runner as a scheduled task:

```
schtasks /create /tn "Mullvad Test Runner" /sc onlogon /tr "\"E:\test-runner.exe\" \\.\COM1 serve" /rl highest
```

Further changes might be required to prevent the task from stopping unexpectedly. In the
Task Scheduler (`taskschd.msc`), change the following settings for the runner task:

* Disable "Start the task only if the computer is on AC power".
* Disable "Stop task if it runs longer than ...".
* Enable "Run task as soon as possible after a scheduled start is missed".
* Enable "If the task fails, restart every: 1 minute".

* In the guest, disable Windows Update.

* Open `services.msc`.

* Open the properties for `Windows Update`.

* Set "Startup type" to "Disabled". Also, click "stop".

* In the guest, disable SmartScreen.

* Go to "Reputation-based protection settings" under
Start > Settings > Update & Security > Windows Security > App & browser control.

* Set "Check apps and files" to off.

* (Windows 11) In the guest, disable Smart App Control

* Go to "Smart App Control" under
Start > Settings > Privacy & security > Windows Security > App & browser control.

* Set it to off.

* Enable autologon by creating or editing the following registry values (all of type REG_SZ):

* Set the current user in
`HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\DefaultUserName`.

* Set the password in
`HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\DefaultPassword`.

* Set `HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\AutoAdminLogon` to 1.

* Shut down.
Loading
Loading