Project Number Date
test_Tails_ISO_disable-thunderbird-telemetry 6 15 Nov 2024, 22:46

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:31.827 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:18.531
Before features/support/hooks.rb:269 0.006
Given a computer 0.200
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.617
When I start Tails from USB drive "old" with network unplugged 1:40.581
Then the boot device has safe access rights 3.078
And Tails is running from USB drive "old" 0.308
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.096
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:326 3.569
After features/support/hooks.rb:100 0.008
Tags: @product
2:5.529
Before features/support/hooks.rb:269 0.005
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:24.257
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 31.620
And I take note of which tps features are available 1.955
Then a Tails persistence partition exists on USB drive "old" 0.757
And I shutdown Tails and wait for the computer to power off 6.351
After features/support/hooks.rb:326 0.161
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.357
Before features/support/hooks.rb:269 0.005
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.516
Then Tails is running from USB drive "old" 0.311
And all tps features are active 2.372
When I write some files expected to persist 1.916
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.454
And I take note of which tps features are available 0.534
And I shutdown Tails and wait for the computer to power off 4.799
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.602
After features/support/hooks.rb:326 0.118
After features/support/hooks.rb:100 0.007
Tags: @product
3:3.164
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 29.561
And I log in to a new session 19.669
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.484
And I plug USB drive "to_upgrade" 2.492
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.893
Then the running Tails is installed on USB drive "to_upgrade" 25.633
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:326 3.645
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.670
Before features/support/hooks.rb:269 0.006
Given a computer 0.312
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.563
Then all tps features from the old Tails version are active 1.691
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 3.608
And the expected persistent files created with the old Tails version are present in the filesystem 1.620
And all persistent directories from the old Tails version have safe access rights 2.536
After features/support/hooks.rb:326 0.915
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:41.792
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 14.961
And no SquashFS delta is installed 0.308
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.308
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.310
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.439
When the network is plugged 0.097
And Tor is ready 24.060
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.878
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.760
Given I shutdown Tails and wait for the computer to power off 11.211
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.177
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.359
And the file system changes introduced in version 6.2~testoverlayfs are present 0.329
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.348
# 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.281
When the network is plugged 0.148
And Tor is ready 17.781
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.677
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.364
Given I shutdown Tails and wait for the computer to power off 4.282
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.047
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.274
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
And only the 6.3~testoverlayfs SquashFS delta is installed 0.134
# 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.368
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.369
When the network is plugged 0.075
And Tor is ready 17.390
Then the Upgrader considers the system as up-to-date 0.300
# 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 14.959
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.103
After features/support/hooks.rb:326 0.734
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
1:2.779
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.504
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.603
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.886
But a current signing key is available on our website 0.000
When the network is plugged 0.177
And Tor is ready 48.926
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.606
After features/support/hooks.rb:326 0.662
After features/support/hooks.rb:100 0.000