Project Number Date
test_Tails_ISO_stable 5563 10 Apr 2025, 10:19

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 21:41.339 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:4.708
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 31.786
When I start Tails from USB drive "old" with network unplugged 1:27.518
Then the boot device has safe access rights 3.080
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.111
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:330 7.357
After features/support/hooks.rb:100 0.010
Tags: @product
2:13.118
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.345
And I start Tails from USB drive "old" with network unplugged and I login 1:29.980
Then Tails is running from USB drive "old" 0.318
And I create a persistent partition 31.042
And I take note of which tps features are available 1.962
Then a Tails persistence partition exists on USB drive "old" 0.836
And I shutdown Tails and wait for the computer to power off 8.632
After features/support/hooks.rb:330 0.155
After features/support/hooks.rb:100 0.008
Tags: @product
2:58.942
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.554
Then Tails is running from USB drive "old" 0.352
And all tps features are active 2.462
When I write some files expected to persist 2.057
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.451
And all persistent directories from the old Tails version have safe access rights 2.346
And I take note of which tps features are available 0.517
And I shutdown Tails and wait for the computer to power off 6.402
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.372
After features/support/hooks.rb:330 0.136
After features/support/hooks.rb:100 0.010
Tags: @product
2:40.572
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 11.206
And I log in to a new session 21.166
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.589
And I plug USB drive "to_upgrade" 2.401
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.261
Then the running Tails is installed on USB drive "to_upgrade" 28.543
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:330 1.172
After features/support/hooks.rb:100 0.000
Tags: @product
2:27.588
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:17.213
Then all tps features from the old Tails version are active 1.881
And Tails is running from USB drive "to_upgrade" 0.472
And the boot device has safe access rights 3.612
And the expected persistent files created with the old Tails version are present in the filesystem 1.520
And all persistent directories from the old Tails version have safe access rights 2.682
After features/support/hooks.rb:330 2.381
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
8:40.629
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.868
And no SquashFS delta is installed 0.076
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.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.457
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.449
When the network is plugged 0.096
And Tor is ready 19.449
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.740
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 1:20.500
Given I shutdown Tails and wait for the computer to power off 9.205
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.122
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.390
And the file system changes introduced in version 6.2~testoverlayfs are present 0.463
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.412
# 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.320
When the network is plugged 0.071
And Tor is ready 15.666
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.934
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 1:2.225
Given I shutdown Tails and wait for the computer to power off 4.498
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.393
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.304
And the file system changes introduced in version 6.3~testoverlayfs are present 0.511
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.469
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.399
When the network is plugged 0.079
And Tor is ready 17.646
Then the Upgrader considers the system as up-to-date 0.372
# 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.250
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.635
After features/support/hooks.rb:330 0.799
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
35.780
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.877
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.087
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 18.658
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.699
After features/support/hooks.rb:330 0.748
After features/support/hooks.rb:100 0.000