Project Number Date
test_Tails_ISO_stable 4565 12 Dec 2023, 17:35

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 16:35.682 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:26.108
Before features/support/hooks.rb:245 0.004
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 19.302
When I start Tails from USB drive "old" with network unplugged 1:1.488
Then the boot device has safe access rights 3.130
And Tails is running from USB drive "old" 0.303
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:291 3.551
After features/support/hooks.rb:75 0.008
Tags: @product
1:54.593
Before features/support/hooks.rb:245 0.004
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login 1:2.588
Then Tails is running from USB drive "old" 0.302
And I create a persistent partition 42.243
And I take note of which tps features are available 1.311
Then a Tails persistence partition exists on USB drive "old" 0.806
And I shutdown Tails and wait for the computer to power off 7.174
After features/support/hooks.rb:291 0.149
After features/support/hooks.rb:75 0.009
Tags: @product
2:20.550
Before features/support/hooks.rb:245 0.004
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:53.304
Then Tails is running from USB drive "old" 0.346
And all tps features are active 2.240
When I write some files expected to persist 2.015
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.284
And all persistence configuration files have safe access rights 0.668
And all persistent directories from the old Tails version have safe access rights 3.014
And I take note of which tps features are available 0.466
And I shutdown Tails and wait for the computer to power off 3.059
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.969
After features/support/hooks.rb:291 0.147
After features/support/hooks.rb:75 0.007
Tags: @product
2:30.977
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.723
And I log in to a new session 14.414
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.017
And I plug USB drive "to_upgrade" 2.446
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.061
Then the running Tails is installed on USB drive "to_upgrade" 12.934
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.173
After features/support/hooks.rb:291 3.587
After features/support/hooks.rb:75 0.000
Tags: @product
2:1.249
Before features/support/hooks.rb:245 0.006
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:50.607
Then all tps features from the old Tails version are active 1.830
And Tails is running from USB drive "to_upgrade" 0.312
And the boot device has safe access rights 4.014
And the expected persistent files created with the old Tails version are present in the filesystem 1.688
And all persistent directories from the old Tails version have safe access rights 2.606
After features/support/hooks.rb:291 0.806
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
5:53.566
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.063
And no SquashFS delta is installed 0.248
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.300
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.212
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.355
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.544
When the network is plugged 0.030
And Tor is ready 16.583
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.595
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.454
Given I shutdown Tails and wait for the computer to power off 5.427
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.384
Then Tails is running version 2.2~testoverlayfsng 0.104
And all tps features are active 2.314
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.436
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.281
# We'll really install Tails_amd64_2.0~testoverlayfsng_to_2.3~testoverlayfsng.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 2.1~testoverlayfsng was initially installed 0.271
When the network is plugged 0.033
And Tor is ready 15.038
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.807
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.601
Given I shutdown Tails and wait for the computer to power off 4.239
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.548
Then Tails is running version 2.3~testoverlayfsng 0.104
And all tps features are active 2.115
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.599
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.059
# 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.269
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.293
When the network is plugged 0.059
And Tor is ready 14.379
Then the Upgrader considers the system as up-to-date 0.283
# 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 24.773
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.667
After features/support/hooks.rb:291 0.921
After features/support/hooks.rb:75 0.017
Tags: @product @automatic_upgrade
28.638
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.678
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.345
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.068
And the signing key used by the Upgrader is outdated 0.857
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 16.093
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.550
After features/support/hooks.rb:291 0.763
After features/support/hooks.rb:75 0.000