Project Number Date
test_Tails_ISO_stable 5279 20 Nov 2024, 12:45

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 20:18.208 Passed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
2:14.410
Before features/support/hooks.rb:269 0.006
Given a computer 0.243
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 32.152
When I start Tails from USB drive "old" with network unplugged 1:36.459
Then the boot device has safe access rights 3.353
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.103
And udev-watchdog is monitoring the correct device 0.326
And I unplug USB drive "old" 0.262
After features/support/hooks.rb:326 3.542
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.508
Before features/support/hooks.rb:269 0.006
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:26.742
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 32.822
And I take note of which tps features are available 1.577
Then a Tails persistence partition exists on USB drive "old" 0.843
And I shutdown Tails and wait for the computer to power off 8.946
After features/support/hooks.rb:326 0.212
After features/support/hooks.rb:100 0.007
Tags: @product
2:56.580
Before features/support/hooks.rb:269 0.004
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.227
Then Tails is running from USB drive "old" 0.503
And all tps features are active 2.013
When I write some files expected to persist 2.014
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.259
And all persistence configuration files have safe access rights 0.425
And all persistent directories from the old Tails version have safe access rights 2.800
And I take note of which tps features are available 0.489
And I shutdown Tails and wait for the computer to power off 4.187
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.439
After features/support/hooks.rb:326 0.158
After features/support/hooks.rb:100 0.008
Tags: @product
2:36.361
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.349
And I log in to a new session 21.104
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.946
And I plug USB drive "to_upgrade" 2.568
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.959
Then the running Tails is installed on USB drive "to_upgrade" 22.964
And I unplug USB drive "to_upgrade" 0.256
And I unplug USB drive "__internal" 0.212
After features/support/hooks.rb:326 2.308
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.242
Before features/support/hooks.rb:269 0.004
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.584
Then all tps features from the old Tails version are active 1.829
And Tails is running from USB drive "to_upgrade" 0.381
And the boot device has safe access rights 3.711
And the expected persistent files created with the old Tails version are present in the filesystem 1.800
And all persistent directories from the old Tails version have safe access rights 2.730
After features/support/hooks.rb:326 0.726
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:15.868
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.438
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.468
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.130
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.293
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.506
When the network is plugged 0.081
And Tor is ready 23.336
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.655
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.725
Given I shutdown Tails and wait for the computer to power off 11.252
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.068
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.341
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.384
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.316
When the network is plugged 0.074
And Tor is ready 16.871
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.153
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.528
Given I shutdown Tails and wait for the computer to power off 4.566
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.701
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.163
And the file system changes introduced in version 6.3~testoverlayfs are present 0.499
And only the 6.3~testoverlayfs SquashFS delta is installed 0.092
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.318
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.354
When the network is plugged 0.068
And Tor is ready 48.218
Then the Upgrader considers the system as up-to-date 0.361
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 16.726
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.653
After features/support/hooks.rb:326 0.763
After features/support/hooks.rb:100 0.038
Tags: @product @automatic_upgrade
44.236
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.235
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.442
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.218
And the signing key used by the Upgrader is outdated 1.049
But a current signing key is available on our website 0.000
When the network is plugged 0.080
And Tor is ready 22.048
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.160
After features/support/hooks.rb:326 0.783
After features/support/hooks.rb:100 0.000