Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 31 15 Nov 2024, 07:14

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:27.351 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:5.657
Before features/support/hooks.rb:269 0.004
Given a computer 0.427
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.125
And I write an old version of the Tails USB image to disk "old" 31.765
When I start Tails from USB drive "old" with network unplugged 1:27.877
Then the boot device has safe access rights 3.329
And Tails is running from USB drive "old" 0.389
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.105
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:326 8.008
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.962
Before features/support/hooks.rb:269 0.006
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login 1:33.520
Then Tails is running from USB drive "old" 0.378
And I create a persistent partition 31.823
And I take note of which tps features are available 1.862
Then a Tails persistence partition exists on USB drive "old" 0.805
And I shutdown Tails and wait for the computer to power off 6.337
After features/support/hooks.rb:326 0.168
After features/support/hooks.rb:100 0.007
Tags: @product
2:49.141
Before features/support/hooks.rb:269 0.004
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.626
Then Tails is running from USB drive "old" 0.338
And all tps features are active 2.562
When I write some files expected to persist 2.029
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.238
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 2.660
And I take note of which tps features are available 0.477
And I shutdown Tails and wait for the computer to power off 4.293
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.300
After features/support/hooks.rb:326 0.151
After features/support/hooks.rb:100 0.008
Tags: @product
2:37.432
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.711
And I log in to a new session 19.720
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.765
And I plug USB drive "to_upgrade" 3.843
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.966
Then the running Tails is installed on USB drive "to_upgrade" 22.973
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.225
After features/support/hooks.rb:326 3.558
After features/support/hooks.rb:100 0.000
Tags: @product
2:7.523
Before features/support/hooks.rb:269 0.004
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:57.995
Then all tps features from the old Tails version are active 1.882
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 3.336
And the expected persistent files created with the old Tails version are present in the filesystem 1.397
And all persistent directories from the old Tails version have safe access rights 2.386
After features/support/hooks.rb:326 1.471
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:55.441
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 16.219
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.673
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.803
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.527
When the network is plugged 0.081
And Tor is ready 28.689
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.142
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.545
Given I shutdown Tails and wait for the computer to power off 11.001
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.528
Then Tails is running version 6.2~testoverlayfs 0.035
And all tps features are active 2.466
And the file system changes introduced in version 6.2~testoverlayfs are present 0.628
And only the 6.2~testoverlayfs SquashFS delta is installed 0.199
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.366
# 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.490
When the network is plugged 0.084
And Tor is ready 19.921
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.346
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.245
Given I shutdown Tails and wait for the computer to power off 6.585
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.033
Then Tails is running version 6.3~testoverlayfs 0.124
And all tps features are active 2.504
And the file system changes introduced in version 6.3~testoverlayfs are present 0.974
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.361
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.424
When the network is plugged 0.082
And Tor is ready 17.913
Then the Upgrader considers the system as up-to-date 10.908
# 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 16.314
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.938
After features/support/hooks.rb:326 0.804
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
37.192
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.601
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.753
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 20.388
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.251
After features/support/hooks.rb:326 0.723
After features/support/hooks.rb:100 0.000