Test the new build¶

Before submitting a merge proposal to add the merged package to the Archive, test it to ensure there are no regressions.

Merging series

The article series provides guidance on performing package merges.

Process overview:

Extra:

Run package tests¶

Create and start a new LXD container to test in:

$ lxc launch ubuntu-daily:ubuntu/<ubuntu-codename> tester && lxc exec tester bash

Install the currently available version of the package you’ve been working on:
```
$ apt update && apt dist-upgrade -y && apt install -y at
```

Run the test:

echo "echo xyz > test.txt" | at now + 1 minute && sleep 1m && cat test.txt && rm test.txt

Add your PPA to the virtual system to upgrade the package to the version you want to test:
```
$ sudo add-apt-repository -y ppa:kstenerud/at-merge-lp1802914
```
If the Ubuntu release for which you’ve built the package is not yet available, modify the source list entry. For example:
```
$ vi /etc/apt/sources.list.d/kstenerud-ubuntu-at-merge-lp1802914-cosmic.list
* change cosmic to disco
```
Upgrade to the new version of the package from your PPA:
```
$ apt update && apt dist-upgrade -y
```

Test the upgraded version:

$ echo "echo abc > test.txt" | at now + 1 minute && sleep 1m && cat test.txt && rm test.txt

Create and start a new LXD container to test in:

$ lxc launch ubuntu-daily:ubuntu/<ubuntu-codename> tester && lxc exec tester bash

Add your PPA to the virtual system to upgrade the package to the version you want to test:
```
$ sudo add-apt-repository -y ppa:kstenerud/at-merge-lp1802914
```

Install the new version of the package from your PPA:

$ apt update && apt dist-upgrade -y && apt install -y at

Run the test:

echo "echo xyz > test.txt" | at now + 1 minute && sleep 1m && cat test.txt && rm test.txt

Run various basic commands.
Run regression tests.
For a package that Build-Depends on itself (openjdk, jruby, kotlin, etc.), build it using the new version.