Project Number Date
test_Tails_ISO_devel 3467 07 Aug 2024, 15: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:20.274 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:7.363
Before features/support/hooks.rb:269 0.007
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.057
And I write an old version of the Tails USB image to disk "old" 32.196
When I start Tails from USB drive "old" with network unplugged 1:29.958
Then the boot device has safe access rights 2.988
And Tails is running from USB drive "old" 0.295
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.300
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:326 8.423
After features/support/hooks.rb:100 0.010
Tags: @product
2:9.740
Before features/support/hooks.rb:269 0.011
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login 1:21.771
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 36.604
And I take note of which tps features are available 1.392
Then a Tails persistence partition exists on USB drive "old" 0.848
And I shutdown Tails and wait for the computer to power off 8.571
After features/support/hooks.rb:326 0.210
After features/support/hooks.rb:100 0.014
Tags: @product
2:56.008
Before features/support/hooks.rb:269 0.007
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.000
Then Tails is running from USB drive "old" 0.383
And all tps features are active 1.995
When I write some files expected to persist 1.687
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.548
And all persistent directories from the old Tails version have safe access rights 2.605
And I take note of which tps features are available 0.393
And I shutdown Tails and wait for the computer to power off 4.414
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.605
After features/support/hooks.rb:326 0.131
After features/support/hooks.rb:100 0.011
Tags: @product
2:30.075
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 11.309
And I log in to a new session 18.312
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.597
And I plug USB drive "to_upgrade" 2.444
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.771
Then the running Tails is installed on USB drive "to_upgrade" 20.217
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.206
After features/support/hooks.rb:326 2.298
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.197
Before features/support/hooks.rb:269 0.006
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.966
Then all tps features from the old Tails version are active 1.707
And Tails is running from USB drive "to_upgrade" 0.319
And the boot device has safe access rights 3.186
And the expected persistent files created with the old Tails version are present in the filesystem 1.452
And all persistent directories from the old Tails version have safe access rights 2.363
After features/support/hooks.rb:326 0.663
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:49.903
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 24.876
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.534
When the network is plugged 0.069
And Tor is ready 21.256
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.927
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.285
Given I shutdown Tails and wait for the computer to power off 8.771
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.615
Then Tails is running version 6.2~testoverlayfs 0.040
And all tps features are active 2.880
And the file system changes introduced in version 6.2~testoverlayfs are present 0.284
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.345
# 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.328
When the network is plugged 0.551
And Tor is ready 18.949
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.519
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.032
Given I shutdown Tails and wait for the computer to power off 4.475
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.680
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.220
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.146
# 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.470
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.393
When the network is plugged 0.063
And Tor is ready 18.390
Then the Upgrader considers the system as up-to-date 0.350
# 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.041
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.981
After features/support/hooks.rb:326 0.767
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
36.983
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 10.933
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.477
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.890
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 17.624
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.921
After features/support/hooks.rb:326 0.836
After features/support/hooks.rb:100 0.000