Project Number Date
test_Tails_ISO_devel 3558 21 Oct 2024, 20:20

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 18:45.358 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:0.331
Before features/support/hooks.rb:269 0.006
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 31.187
When I start Tails from USB drive "old" with network unplugged 1:23.616
Then the boot device has safe access rights 3.113
And Tails is running from USB drive "old" 0.382
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.353
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:326 6.987
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.531
Before features/support/hooks.rb:269 0.006
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:23.138
Then Tails is running from USB drive "old" 0.374
And I create a persistent partition 32.020
And I take note of which tps features are available 1.656
Then a Tails persistence partition exists on USB drive "old" 0.919
And I shutdown Tails and wait for the computer to power off 8.211
After features/support/hooks.rb:326 0.187
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.488
Before features/support/hooks.rb:269 0.007
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.757
Then Tails is running from USB drive "old" 0.916
And all tps features are active 2.111
When I write some files expected to persist 2.487
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.426
And all persistent directories from the old Tails version have safe access rights 2.647
And I take note of which tps features are available 0.668
And I shutdown Tails and wait for the computer to power off 4.382
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.691
After features/support/hooks.rb:326 0.114
After features/support/hooks.rb:100 0.010
Tags: @product
2:33.149
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.482
And I log in to a new session 18.885
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.636
And I plug USB drive "to_upgrade" 2.446
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.373
Then the running Tails is installed on USB drive "to_upgrade" 24.877
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:326 2.166
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.550
Before features/support/hooks.rb:269 0.007
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.764
Then all tps features from the old Tails version are active 1.936
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.373
And the expected persistent files created with the old Tails version are present in the filesystem 1.367
And all persistent directories from the old Tails version have safe access rights 2.560
After features/support/hooks.rb:326 0.642
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:20.059
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 13.863
And no SquashFS delta is installed 0.128
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.361
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.424
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.484
When the network is plugged 0.086
And Tor is ready 24.292
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.509
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.327
Given I shutdown Tails and wait for the computer to power off 10.845
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.252
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.396
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.339
# 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.263
When the network is plugged 0.064
And Tor is ready 18.291
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.149
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.030
Given I shutdown Tails and wait for the computer to power off 4.309
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.495
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.191
And the file system changes introduced in version 6.3~testoverlayfs are present 0.505
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.282
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.250
When the network is plugged 0.110
And Tor is ready 19.290
Then the Upgrader considers the system as up-to-date 0.348
# 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.674
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.958
After features/support/hooks.rb:326 1.011
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.246
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 10.509
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.370
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the signing key used by the Upgrader is outdated 0.842
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 18.972
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.371
After features/support/hooks.rb:326 0.807
After features/support/hooks.rb:100 0.000