Project Number Date
test_Tails_ISO_devel 3297 26 Feb 2024, 12:47

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 22:3.687 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:39.870
Before features/support/hooks.rb:245 0.007
Given a computer 0.205
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 22.134
When I start Tails from USB drive "old" with network unplugged 1:12.182
Then the boot device has safe access rights 3.214
And Tails is running from USB drive "old" 0.357
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.283
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:291 6.747
After features/support/hooks.rb:75 0.015
Tags: @product
2:27.374
Before features/support/hooks.rb:245 0.010
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login 1:24.168
Then Tails is running from USB drive "old" 0.379
And I create a persistent partition 51.873
And I take note of which tps features are available 1.915
Then a Tails persistence partition exists on USB drive "old" 0.733
And I shutdown Tails and wait for the computer to power off 8.071
After features/support/hooks.rb:291 0.132
After features/support/hooks.rb:75 0.012
Tags: @product
3:30.613
Before features/support/hooks.rb:245 0.009
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:1.044
Then Tails is running from USB drive "old" 0.373
And all tps features are active 2.380
When I write some files expected to persist 1.657
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.362
And all persistent directories from the old Tails version have safe access rights 2.700
And I take note of which tps features are available 0.630
And I shutdown Tails and wait for the computer to power off 5.067
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.975
After features/support/hooks.rb:291 0.124
After features/support/hooks.rb:75 0.011
Tags: @product
2:45.715
Before features/support/hooks.rb:245 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 26.851
And I log in to a new session 15.960
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.447
And I plug USB drive "to_upgrade" 2.463
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.380
Then the running Tails is installed on USB drive "to_upgrade" 13.224
And I unplug USB drive "to_upgrade" 0.204
And I unplug USB drive "__internal" 0.182
After features/support/hooks.rb:291 6.766
After features/support/hooks.rb:75 0.000
Tags: @product
2:59.710
Before features/support/hooks.rb:245 0.012
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:50.050
Then all tps features from the old Tails version are active 1.776
And Tails is running from USB drive "to_upgrade" 0.314
And the boot device has safe access rights 3.333
And the expected persistent files created with the old Tails version are present in the filesystem 1.497
And all persistent directories from the old Tails version have safe access rights 2.530
After features/support/hooks.rb:291 0.758
After features/support/hooks.rb:75 0.011
8:3.160
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 15.317
And no SquashFS delta is installed 0.126
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.294
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.119
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.067
And Tor is ready 20.711
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.555
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.532
Given I shutdown Tails and wait for the computer to power off 7.499
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:47.596
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.264
And the file system changes introduced in version 6.2~testoverlayfs are present 0.341
And only the 6.2~testoverlayfs SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.394
# 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.308
When the network is plugged 0.042
And Tor is ready 17.136
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.922
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.148
Given I shutdown Tails and wait for the computer to power off 5.378
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:49.154
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 4.839
And the file system changes introduced in version 6.3~testoverlayfs are present 0.606
And only the 6.3~testoverlayfs SquashFS delta is installed 0.129
# 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.328
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.260
When the network is plugged 0.054
And Tor is ready 16.818
Then the Upgrader considers the system as up-to-date 0.278
# 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 13.932
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.132
After features/support/hooks.rb:291 0.959
After features/support/hooks.rb:75 0.024
37.240
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.375
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.537
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 17.511
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.363
After features/support/hooks.rb:291 0.677
After features/support/hooks.rb:75 0.000