Project Number Date
test_Tails_ISO_stable 5141 04 Oct 2024, 08:56

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:27.623 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:24.692
Before features/support/hooks.rb:269 0.005
Given a computer 0.222
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.062
And I write an old version of the Tails USB image to disk "old" 32.559
When I start Tails from USB drive "old" with network unplugged 1:46.397
Then the boot device has safe access rights 3.259
And Tails is running from USB drive "old" 0.438
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.328
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:326 7.230
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.854
Before features/support/hooks.rb:269 0.005
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login 1:30.318
Then Tails is running from USB drive "old" 0.373
And I create a persistent partition 32.539
And I take note of which tps features are available 1.576
Then a Tails persistence partition exists on USB drive "old" 0.880
And I shutdown Tails and wait for the computer to power off 8.937
After features/support/hooks.rb:326 0.218
After features/support/hooks.rb:100 0.010
Tags: @product
3:4.198
Before features/support/hooks.rb:269 0.004
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.730
Then Tails is running from USB drive "old" 1.542
And all tps features are active 2.503
When I write some files expected to persist 2.990
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.288
And all persistence configuration files have safe access rights 0.458
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.514
And I shutdown Tails and wait for the computer to power off 6.657
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.651
After features/support/hooks.rb:326 0.155
After features/support/hooks.rb:100 0.010
Tags: @product
2:36.845
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 12.728
And I log in to a new session 20.696
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.247
And I plug USB drive "to_upgrade" 2.507
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.419
Then the running Tails is installed on USB drive "to_upgrade" 20.828
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:326 5.684
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.239
Before features/support/hooks.rb:269 0.006
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.955
Then all tps features from the old Tails version are active 1.938
And Tails is running from USB drive "to_upgrade" 0.424
And the boot device has safe access rights 3.331
And the expected persistent files created with the old Tails version are present in the filesystem 2.892
And all persistent directories from the old Tails version have safe access rights 2.516
After features/support/hooks.rb:326 0.955
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
6:46.801
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 13.115
And no SquashFS delta is installed 0.314
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.388
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.410
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.584
When the network is plugged 0.370
And Tor is ready 23.477
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.301
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.414
Given I shutdown Tails and wait for the computer to power off 11.135
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.944
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.308
And the file system changes introduced in version 6.2~testoverlayfs are present 0.444
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.303
When the network is plugged 0.075
And Tor is ready 20.903
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.825
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.645
Given I shutdown Tails and wait for the computer to power off 4.496
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.112
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.128
And the file system changes introduced in version 6.3~testoverlayfs are present 0.513
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.356
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.532
When the network is plugged 0.213
And Tor is ready 18.440
Then the Upgrader considers the system as up-to-date 11.108
# 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.285
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.064
After features/support/hooks.rb:326 0.786
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
59.991
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.017
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.063
And the signing key used by the Upgrader is outdated 1.104
But a current signing key is available on our website 0.000
When the network is plugged 0.126
And Tor is ready 46.716
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.616
After features/support/hooks.rb:326 0.668
After features/support/hooks.rb:100 0.000