Project Number Date
test_Tails_ISO_stable 5431 29 Jan 2025, 14:24

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 19:5.503 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
1:57.424
Before features/support/hooks.rb:269 0.005
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 29.599
When I start Tails from USB drive "old" with network unplugged 1:22.299
Then the boot device has safe access rights 3.075
And Tails is running from USB drive "old" 0.412
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.351
And I unplug USB drive "old" 0.233
After features/support/hooks.rb:326 7.091
After features/support/hooks.rb:100 0.011
Tags: @product
2:12.715
Before features/support/hooks.rb:269 0.007
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:26.591
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 34.557
And I take note of which tps features are available 1.829
Then a Tails persistence partition exists on USB drive "old" 0.804
And I shutdown Tails and wait for the computer to power off 8.403
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.009
Tags: @product
3:1.128
Before features/support/hooks.rb:269 0.005
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:22.795
Then Tails is running from USB drive "old" 0.352
And all tps features are active 2.122
When I write some files expected to persist 1.649
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.272
And all persistence configuration files have safe access rights 0.354
And all persistent directories from the old Tails version have safe access rights 2.372
And I take note of which tps features are available 0.438
And I shutdown Tails and wait for the computer to power off 6.413
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.164
After features/support/hooks.rb:326 0.137
After features/support/hooks.rb:100 0.010
Tags: @product
2:30.142
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.098
And I log in to a new session 20.828
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.679
And I plug USB drive "to_upgrade" 2.480
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.006
Then the running Tails is installed on USB drive "to_upgrade" 20.587
And I unplug USB drive "to_upgrade" 0.252
And I unplug USB drive "__internal" 0.210
After features/support/hooks.rb:326 2.549
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.443
Before features/support/hooks.rb:269 0.006
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.301
Then all tps features from the old Tails version are active 1.642
And Tails is running from USB drive "to_upgrade" 0.356
And the boot device has safe access rights 3.773
And the expected persistent files created with the old Tails version are present in the filesystem 1.642
And all persistent directories from the old Tails version have safe access rights 2.506
After features/support/hooks.rb:326 0.825
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:34.439
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.661
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.690
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
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.463
When the network is plugged 0.067
And Tor is ready 17.629
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.874
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.848
Given I shutdown Tails and wait for the computer to power off 8.713
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.922
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.205
And the file system changes introduced in version 6.2~testoverlayfs are present 0.304
And only the 6.2~testoverlayfs SquashFS delta is installed 0.118
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.309
# 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.299
When the network is plugged 0.081
And Tor is ready 21.790
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.067
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.390
Given I shutdown Tails and wait for the computer to power off 4.383
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.511
Then Tails is running version 6.3~testoverlayfs 0.062
And all tps features are active 2.256
And the file system changes introduced in version 6.3~testoverlayfs are present 0.593
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.308
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.375
When the network is plugged 0.096
And Tor is ready 17.288
Then the Upgrader considers the system as up-to-date 10.764
# 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 15.705
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.050
After features/support/hooks.rb:326 0.829
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
33.207
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 9.345
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.635
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.099
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 16.411
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.575
After features/support/hooks.rb:326 0.707
After features/support/hooks.rb:100 0.000