From a5d56e3b5443263b53b0487c81125123411bd0cf Mon Sep 17 00:00:00 2001 From: Philip Hands Date: Wed, 11 May 2016 17:11:01 +0200 Subject: move cucumber things under cucumber/ --- features/DebianLive/apt.feature | 14 - features/README-sikuli-cucumber | 13 - features/apt.feature | 36 - features/build.feature | 212 ---- features/checks.feature | 107 -- features/config/defaults.yml | 36 - features/dhcp.feature | 22 - features/domains/default.xml | 59 -- features/domains/default_net.xml | 13 - features/domains/disk.xml | 5 - features/domains/fs_share.xml | 6 - features/domains/storage_pool.xml | 6 - features/domains/volume.xml | 14 - features/electrum.feature | 34 - features/encryption.feature | 35 - features/evince.feature | 66 -- features/icedove.feature | 39 - .../images/DebianInstallerCountrySelection.png | Bin 5303 -> 0 bytes features/images/DebianInstallerDomainPrompt.png | Bin 2225 -> 0 bytes features/images/DebianInstallerHostnamePrompt.png | Bin 5643 -> 0 bytes features/images/DebianInstallerHttpProxy.png | Bin 485 -> 0 bytes .../images/DebianInstallerInstallingBaseSystem.png | Bin 3554 -> 0 bytes features/images/DebianInstallerMirrorCountry.png | Bin 3769 -> 0 bytes features/images/DebianInstallerNameOfUser.png | Bin 3792 -> 0 bytes features/images/DebianInstallerNoDiskFound.png | Bin 4005 -> 0 bytes .../images/DebianInstallerPartitioningMethod.png | Bin 13953 -> 0 bytes .../images/DebianInstallerPartitioningScheme.png | Bin 2879 -> 0 bytes features/images/DebianInstallerRootPassword.png | Bin 3226 -> 0 bytes .../DebianInstallerSelectDiskToPartition.png | Bin 5403 -> 0 bytes .../images/DebianInstallerSelectLangEnglish.png | Bin 7229 -> 0 bytes .../images/DebianInstallerSelectLangEnglishUK.png | Bin 4853 -> 0 bytes features/images/DebianInstallerUserPassword.png | Bin 4892 -> 0 bytes features/images/DebianLive7BootSplash.png | Bin 13399 -> 0 bytes features/images/DebianLive7BootSplashTabMsg.png | Bin 4260 -> 0 bytes features/images/DebianLive7Greeter.png | Bin 3166 -> 0 bytes features/images/DebianLiveBootSplash.png | Bin 1569 -> 0 bytes features/images/DebianLiveBootSplashTabMsg.png | Bin 790 -> 0 bytes features/images/DebianLoginPromptVT.png | Bin 7466 -> 0 bytes features/images/d-i8_bootsplash.png | Bin 9930 -> 0 bytes features/images/d-i_ArchiveMirror.png | Bin 2908 -> 0 bytes features/images/d-i_ChooseSoftware.png | Bin 4204 -> 0 bytes features/images/d-i_DesktopTask_No.png | Bin 7161 -> 0 bytes features/images/d-i_DesktopTask_Yes.png | Bin 4152 -> 0 bytes features/images/d-i_F12BootMenu.png | Bin 482 -> 0 bytes features/images/d-i_FinishPartitioning.png | Bin 8734 -> 0 bytes features/images/d-i_GRUBEnterDev.png | Bin 2490 -> 0 bytes features/images/d-i_GRUB_Debian.png | Bin 387 -> 0 bytes features/images/d-i_GRUBdev.png | Bin 1765 -> 0 bytes features/images/d-i_HttpProxy.png | Bin 5324 -> 0 bytes features/images/d-i_InstallComplete.png | Bin 2740 -> 0 bytes features/images/d-i_InstallGRUB.png | Bin 6367 -> 0 bytes features/images/d-i_No.png | Bin 995 -> 0 bytes features/images/d-i_ScanCD.png | Bin 3216 -> 0 bytes features/images/d-i_SelectBootDev.png | Bin 559 -> 0 bytes features/images/d-i_UseNetMirror.png | Bin 2975 -> 0 bytes features/images/d-i_Yes.png | Bin 1163 -> 0 bytes features/images/d-i_popcon.png | Bin 3894 -> 0 bytes features/localization.feature | 19 - features/mac_spoofing.feature | 71 -- features/mat.feature | 13 - features/misc_files/sample.pdf | Bin 22347 -> 0 bytes features/misc_files/sample.tex | 8 - features/persistence.feature | 55 - features/pidgin.feature | 135 --- features/po.feature | 9 - features/root_access_control.feature | 33 - features/scripts/otr-bot.py | 206 ---- features/scripts/vm-execute | 52 - features/ssh.feature | 31 - features/step_definitions/apt.rb | 56 - features/step_definitions/browser.rb | 195 ---- features/step_definitions/build.rb | 115 --- features/step_definitions/checks.rb | 252 ----- features/step_definitions/common_steps.rb | 1086 -------------------- features/step_definitions/dhcp.rb | 19 - features/step_definitions/electrum.rb | 52 - features/step_definitions/encryption.rb | 133 --- features/step_definitions/evince.rb | 25 - features/step_definitions/firewall_leaks.rb | 56 - features/step_definitions/git.rb | 6 - features/step_definitions/icedove.rb | 94 -- features/step_definitions/mac_spoofing.rb | 108 -- features/step_definitions/pidgin.rb | 467 --------- features/step_definitions/po.rb | 8 - features/step_definitions/root_access_control.rb | 42 - features/step_definitions/snapshots.rb | 257 ----- features/step_definitions/ssh.rb | 122 --- features/step_definitions/time_syncing.rb | 86 -- features/step_definitions/tor.rb | 402 -------- features/step_definitions/torified_browsing.rb | 5 - features/step_definitions/torified_gnupg.rb | 208 ---- features/step_definitions/torified_misc.rb | 41 - features/step_definitions/totem.rb | 43 - features/step_definitions/unsafe_browser.rb | 189 ---- features/step_definitions/untrusted_partitions.rb | 61 -- features/step_definitions/usb.rb | 596 ----------- features/support/config.rb | 100 -- features/support/env.rb | 90 -- features/support/extra_hooks.rb | 165 --- features/support/helpers/chatbot_helper.rb | 59 -- features/support/helpers/ctcp_helper.rb | 126 --- features/support/helpers/display_helper.rb | 48 - features/support/helpers/exec_helper.rb | 79 -- features/support/helpers/firewall_helper.rb | 121 --- features/support/helpers/misc_helpers.rb | 253 ----- features/support/helpers/sikuli_helper.rb | 213 ---- features/support/helpers/sniffing_helper.rb | 43 - features/support/helpers/sshd_helper.rb | 67 -- features/support/helpers/storage_helper.rb | 216 ---- features/support/helpers/vm_helper.rb | 676 ------------ features/support/hooks.rb | 280 ----- features/time_syncing.feature | 129 --- features/tor_bridges.feature | 36 - features/tor_enforcement.feature | 76 -- features/tor_stream_isolation.feature | 62 -- features/torified_browsing.feature | 172 ---- features/torified_git.feature | 31 - features/torified_gnupg.feature | 53 - features/torified_misc.feature | 24 - features/totem.feature | 70 -- features/unsafe_browser.feature | 73 -- features/untrusted_partitions.feature | 80 -- features/usb_install.feature | 107 -- features/usb_upgrade.feature | 164 --- 124 files changed, 9686 deletions(-) delete mode 100644 features/DebianLive/apt.feature delete mode 100644 features/README-sikuli-cucumber delete mode 100644 features/apt.feature delete mode 100644 features/build.feature delete mode 100644 features/checks.feature delete mode 100644 features/config/defaults.yml delete mode 100644 features/dhcp.feature delete mode 100644 features/domains/default.xml delete mode 100644 features/domains/default_net.xml delete mode 100644 features/domains/disk.xml delete mode 100644 features/domains/fs_share.xml delete mode 100644 features/domains/storage_pool.xml delete mode 100644 features/domains/volume.xml delete mode 100644 features/electrum.feature delete mode 100644 features/encryption.feature delete mode 100644 features/evince.feature delete mode 100644 features/icedove.feature delete mode 100644 features/images/DebianInstallerCountrySelection.png delete mode 100644 features/images/DebianInstallerDomainPrompt.png delete mode 100644 features/images/DebianInstallerHostnamePrompt.png delete mode 100644 features/images/DebianInstallerHttpProxy.png delete mode 100644 features/images/DebianInstallerInstallingBaseSystem.png delete mode 100644 features/images/DebianInstallerMirrorCountry.png delete mode 100644 features/images/DebianInstallerNameOfUser.png delete mode 100644 features/images/DebianInstallerNoDiskFound.png delete mode 100644 features/images/DebianInstallerPartitioningMethod.png delete mode 100644 features/images/DebianInstallerPartitioningScheme.png delete mode 100644 features/images/DebianInstallerRootPassword.png delete mode 100644 features/images/DebianInstallerSelectDiskToPartition.png delete mode 100644 features/images/DebianInstallerSelectLangEnglish.png delete mode 100644 features/images/DebianInstallerSelectLangEnglishUK.png delete mode 100644 features/images/DebianInstallerUserPassword.png delete mode 100644 features/images/DebianLive7BootSplash.png delete mode 100644 features/images/DebianLive7BootSplashTabMsg.png delete mode 100644 features/images/DebianLive7Greeter.png delete mode 100644 features/images/DebianLiveBootSplash.png delete mode 100644 features/images/DebianLiveBootSplashTabMsg.png delete mode 100644 features/images/DebianLoginPromptVT.png delete mode 100644 features/images/d-i8_bootsplash.png delete mode 100644 features/images/d-i_ArchiveMirror.png delete mode 100644 features/images/d-i_ChooseSoftware.png delete mode 100644 features/images/d-i_DesktopTask_No.png delete mode 100644 features/images/d-i_DesktopTask_Yes.png delete mode 100644 features/images/d-i_F12BootMenu.png delete mode 100644 features/images/d-i_FinishPartitioning.png delete mode 100644 features/images/d-i_GRUBEnterDev.png delete mode 100644 features/images/d-i_GRUB_Debian.png delete mode 100644 features/images/d-i_GRUBdev.png delete mode 100644 features/images/d-i_HttpProxy.png delete mode 100644 features/images/d-i_InstallComplete.png delete mode 100644 features/images/d-i_InstallGRUB.png delete mode 100644 features/images/d-i_No.png delete mode 100644 features/images/d-i_ScanCD.png delete mode 100644 features/images/d-i_SelectBootDev.png delete mode 100644 features/images/d-i_UseNetMirror.png delete mode 100644 features/images/d-i_Yes.png delete mode 100644 features/images/d-i_popcon.png delete mode 100644 features/localization.feature delete mode 100644 features/mac_spoofing.feature delete mode 100644 features/mat.feature delete mode 100644 features/misc_files/sample.pdf delete mode 100644 features/misc_files/sample.tex delete mode 100644 features/persistence.feature delete mode 100644 features/pidgin.feature delete mode 100644 features/po.feature delete mode 100644 features/root_access_control.feature delete mode 100755 features/scripts/otr-bot.py delete mode 100755 features/scripts/vm-execute delete mode 100644 features/ssh.feature delete mode 100644 features/step_definitions/apt.rb delete mode 100644 features/step_definitions/browser.rb delete mode 100644 features/step_definitions/build.rb delete mode 100644 features/step_definitions/checks.rb delete mode 100644 features/step_definitions/common_steps.rb delete mode 100644 features/step_definitions/dhcp.rb delete mode 100644 features/step_definitions/electrum.rb delete mode 100644 features/step_definitions/encryption.rb delete mode 100644 features/step_definitions/evince.rb delete mode 100644 features/step_definitions/firewall_leaks.rb delete mode 100644 features/step_definitions/git.rb delete mode 100644 features/step_definitions/icedove.rb delete mode 100644 features/step_definitions/mac_spoofing.rb delete mode 100644 features/step_definitions/pidgin.rb delete mode 100644 features/step_definitions/po.rb delete mode 100644 features/step_definitions/root_access_control.rb delete mode 100644 features/step_definitions/snapshots.rb delete mode 100644 features/step_definitions/ssh.rb delete mode 100644 features/step_definitions/time_syncing.rb delete mode 100644 features/step_definitions/tor.rb delete mode 100644 features/step_definitions/torified_browsing.rb delete mode 100644 features/step_definitions/torified_gnupg.rb delete mode 100644 features/step_definitions/torified_misc.rb delete mode 100644 features/step_definitions/totem.rb delete mode 100644 features/step_definitions/unsafe_browser.rb delete mode 100644 features/step_definitions/untrusted_partitions.rb delete mode 100644 features/step_definitions/usb.rb delete mode 100644 features/support/config.rb delete mode 100644 features/support/env.rb delete mode 100644 features/support/extra_hooks.rb delete mode 100644 features/support/helpers/chatbot_helper.rb delete mode 100644 features/support/helpers/ctcp_helper.rb delete mode 100644 features/support/helpers/display_helper.rb delete mode 100644 features/support/helpers/exec_helper.rb delete mode 100644 features/support/helpers/firewall_helper.rb delete mode 100644 features/support/helpers/misc_helpers.rb delete mode 100644 features/support/helpers/sikuli_helper.rb delete mode 100644 features/support/helpers/sniffing_helper.rb delete mode 100644 features/support/helpers/sshd_helper.rb delete mode 100644 features/support/helpers/storage_helper.rb delete mode 100644 features/support/helpers/vm_helper.rb delete mode 100644 features/support/hooks.rb delete mode 100644 features/time_syncing.feature delete mode 100644 features/tor_bridges.feature delete mode 100644 features/tor_enforcement.feature delete mode 100644 features/tor_stream_isolation.feature delete mode 100644 features/torified_browsing.feature delete mode 100644 features/torified_git.feature delete mode 100644 features/torified_gnupg.feature delete mode 100644 features/torified_misc.feature delete mode 100644 features/totem.feature delete mode 100644 features/unsafe_browser.feature delete mode 100644 features/untrusted_partitions.feature delete mode 100644 features/usb_install.feature delete mode 100644 features/usb_upgrade.feature (limited to 'features') diff --git a/features/DebianLive/apt.feature b/features/DebianLive/apt.feature deleted file mode 100644 index 3b71b6c2..00000000 --- a/features/DebianLive/apt.feature +++ /dev/null @@ -1,14 +0,0 @@ -@product -Feature: Doing a trivial d-i install - As a normal user - I should be able to do a text-mode install - - Scenario Outline: Install Debian and boot to login prompt - Given I have installed Debian - And I start the computer - Then I wait for a Login Prompt - - Examples: - | type | - | Minimal | - | Gnome Desktop | diff --git a/features/README-sikuli-cucumber b/features/README-sikuli-cucumber deleted file mode 100644 index 24d90aaf..00000000 --- a/features/README-sikuli-cucumber +++ /dev/null @@ -1,13 +0,0 @@ -Key names: - - http://doc.sikuli.org/keys.html - -Running the thing by hand: - - ./bin/lvc/run_test_suite --view --iso /var/lib/libvirt/images/debian-8.3.0-amd64-i386-netinst.iso --old-iso /var/lib/libvirt/images/debian-8.3.0-amd64-i386-netinst.iso DebianLive/apt.feature - -FIXME - I added a git repo to: - - /var/lib/jenkins/workspace/lvc_debian-installer_jessie_standard_apt - -in order to shut-up Tail's script that looks for git repos to populate some variables -- need to strip that out, or make it overridable. diff --git a/features/apt.feature b/features/apt.feature deleted file mode 100644 index ac778c26..00000000 --- a/features/apt.feature +++ /dev/null @@ -1,36 +0,0 @@ -#10497: wait_until_tor_is_working -@product @fragile -Feature: Installing packages through APT - As a Tails user - when I set an administration password in Tails Greeter - I should be able to install packages using APT and Synaptic - and all Internet traffic should flow only through Tor. - - Background: - Given a computer - And I capture all network traffic - And I start the computer - And the computer boots DebianLive7 - And I set sudo password "asdf" - And I log in to a new session - And GNOME has started - And Tor is ready - And all notifications have disappeared - And available upgrades have been checked - And I save the state so the background can be restored next scenario - - Scenario: APT sources are configured correctly - Then the only hosts in APT sources are "ftp.us.debian.org,http.debian.net,ftp.debian.org,security.debian.org" - - #10496: apt-get scenarios are fragile - @check_tor_leaks @fragile - Scenario: Install packages using apt - When I update APT using apt - Then I should be able to install a package using apt - - #10441: Synaptic test is fragile - @check_tor_leaks @fragile - Scenario: Install packages using Synaptic - When I start Synaptic - And I update APT using Synaptic - Then I should be able to install a package using Synaptic diff --git a/features/build.feature b/features/build.feature deleted file mode 100644 index 74d314de..00000000 --- a/features/build.feature +++ /dev/null @@ -1,212 +0,0 @@ -@source -Feature: custom APT sources to build branches - As a Tails developer, when I build Tails, I'd be happy if - the proper APT sources were automatically picked depending - on which Git branch I am working on. - - Scenario: build from an untagged stable branch where the config/APT_overlays.d directory is empty - Given I am working on the stable base branch - And the last version mentioned in debian/changelog is 1.0 - And Tails 1.0 has not been released yet - And the config/APT_overlays.d directory is empty - When I successfully run tails-custom-apt-sources - Then I should see only the 'stable' suite - - Scenario: build from an untagged stable branch where config/APT_overlays.d is not empty - Given I am working on the stable base branch - And the last version mentioned in debian/changelog is 1.0 - And Tails 1.0 has not been released yet - And config/APT_overlays.d contains 'feature-foo' - And config/APT_overlays.d contains 'bugfix-bar' - When I successfully run tails-custom-apt-sources - Then I should see the 'stable' suite - And I should see the 'feature-foo' suite - And I should see the 'bugfix-bar' suite - But I should not see the '1.0' suite - - Scenario: build from a tagged stable branch where the config/APT_overlays.d directory is empty - Given Tails 0.10 has been released - And the last version mentioned in debian/changelog is 0.10 - And I am working on the stable base branch - And the config/APT_overlays.d directory is empty - When I successfully run tails-custom-apt-sources - Then I should see only the '0.10' suite - - Scenario: build from a tagged stable branch where config/APT_overlays.d is not empty - Given Tails 0.10 has been released - And the last version mentioned in debian/changelog is 0.10 - And I am working on the stable base branch - And config/APT_overlays.d contains 'feature-foo' - When I run tails-custom-apt-sources - Then it should fail - - Scenario: build from a bugfix branch without overlays for a stable release - Given Tails 0.10 has been released - And the last version mentioned in debian/changelog is 0.10.1 - And Tails 0.10.1 has not been released yet - And I am working on the bugfix/disable_gdomap branch based on stable - And the config/APT_overlays.d directory is empty - When I successfully run tails-custom-apt-sources - Then I should see only the 'stable' suite - - Scenario: build from a bugfix branch with overlays for a stable release - Given Tails 0.10 has been released - And the last version mentioned in debian/changelog is 0.10.1 - And Tails 0.10.1 has not been released yet - And I am working on the bugfix/disable_gdomap branch based on stable - And config/APT_overlays.d contains 'bugfix-disable-gdomap' - And config/APT_overlays.d contains 'bugfix-bar' - When I successfully run tails-custom-apt-sources - Then I should see the 'stable' suite - And I should see the 'bugfix-disable-gdomap' suite - And I should see the 'bugfix-bar' suite - But I should not see the '0.10' suite - - Scenario: build from an untagged testing branch where the config/APT_overlays.d directory is empty - Given I am working on the testing base branch - And the last version mentioned in debian/changelog is 0.11 - And Tails 0.11 has not been released yet - And the config/APT_overlays.d directory is empty - When I successfully run tails-custom-apt-sources - Then I should see the 'testing' suite - And I should not see the '0.11' suite - And I should not see the 'feature-foo' suite - And I should not see the 'bugfix-bar' suite - - Scenario: build from an untagged testing branch where config/APT_overlays.d is not empty - Given I am working on the testing base branch - And the last version mentioned in debian/changelog is 0.11 - And Tails 0.11 has not been released yet - And config/APT_overlays.d contains 'feature-foo' - And config/APT_overlays.d contains 'bugfix-bar' - When I successfully run tails-custom-apt-sources - Then I should see the 'testing' suite - And I should see the 'feature-foo' suite - And I should see the 'bugfix-bar' suite - But I should not see the '0.11' suite - - Scenario: build from a tagged testing branch where the config/APT_overlays.d directory is empty - Given I am working on the testing base branch - And the last version mentioned in debian/changelog is 0.11 - And Tails 0.11 has been released - And the config/APT_overlays.d directory is empty - When I successfully run tails-custom-apt-sources - Then I should see only the '0.11' suite - - Scenario: build from a tagged testing branch where config/APT_overlays.d is not empty - Given I am working on the testing base branch - And the last version mentioned in debian/changelog is 0.11 - And Tails 0.11 has been released - And config/APT_overlays.d contains 'feature-foo' - When I run tails-custom-apt-sources - Then it should fail - - Scenario: build a release candidate from a tagged testing branch - Given I am working on the testing base branch - And Tails 0.11 has been released - And the last version mentioned in debian/changelog is 0.12~rc1 - And Tails 0.12-rc1 has been tagged - And the config/APT_overlays.d directory is empty - When I successfully run tails-custom-apt-sources - Then I should see only the '0.12-rc1' suite - - Scenario: build a release candidate from a tagged testing branch where config/APT_overlays.d is not empty - Given I am working on the testing base branch - And Tails 0.11 has been released - And the last version mentioned in debian/changelog is 0.12~rc1 - And Tails 0.12-rc1 has been tagged - And config/APT_overlays.d contains 'bugfix-bar' - When I run tails-custom-apt-sources - Then it should fail - - Scenario: build from the devel branch without overlays - Given I am working on the devel base branch - And the config/APT_overlays.d directory is empty - When I successfully run tails-custom-apt-sources - Then I should see only the 'devel' suite - - Scenario: build from the devel branch with overlays - Given I am working on the devel base branch - And config/APT_overlays.d contains 'feature-foo' - And config/APT_overlays.d contains 'bugfix-bar' - When I successfully run tails-custom-apt-sources - Then I should see the 'devel' suite - And I should see the 'feature-foo' suite - And I should see the 'bugfix-bar' suite - - Scenario: build from the feature/jessie branch without overlays - Given I am working on the feature/jessie base branch - And the config/APT_overlays.d directory is empty - When I successfully run tails-custom-apt-sources - Then I should see only the 'feature-jessie' suite - - Scenario: build from the feature/jessie branch with overlays - Given I am working on the feature/jessie base branch - And config/APT_overlays.d contains 'feature-7756-reintroduce-whisperback' - When I successfully run tails-custom-apt-sources - Then I should see the 'feature-jessie' suite - And I should see the 'feature-7756-reintroduce-whisperback' suite - - Scenario: build from the experimental branch - Given I am working on the experimental branch based on devel - And config/APT_overlays.d contains 'feature-foo' - And config/APT_overlays.d contains 'bugfix-bar' - When I successfully run tails-custom-apt-sources - Then I should see the 'devel' suite - And I should see the 'feature-foo' suite - And I should see the 'bugfix-bar' suite - - Scenario: build from a feature branch with overlays based on devel - Given I am working on the feature/icedove branch based on devel - And config/APT_overlays.d contains 'feature-icedove' - And config/APT_overlays.d contains 'bugfix-bar' - When I successfully run tails-custom-apt-sources - Then I should see the 'devel' suite - And I should see the 'feature-icedove' suite - And I should see the 'bugfix-bar' suite - - Scenario: build from a feature branch without overlays based on devel - Given I am working on the feature/icedove branch based on devel - And the config/APT_overlays.d directory is empty - When I successfully run tails-custom-apt-sources - Then I should see only the 'devel' suite - - Scenario: build from a feature branch with overlays based on feature/jessie - Given I am working on the feature/7756-reintroduce-whisperback branch based on feature/jessie - And config/APT_overlays.d contains 'feature-7756-reintroduce-whisperback' - And config/APT_overlays.d contains 'bugfix-bar' - When I successfully run tails-custom-apt-sources - Then I should see the 'feature-jessie' suite - And I should see the 'feature-7756-reintroduce-whisperback' suite - And I should see the 'bugfix-bar' suite - - Scenario: build from a feature branch without overlays based on feature/jessie - Given I am working on the feature/icedove branch based on feature/jessie - And the config/APT_overlays.d directory is empty - When I successfully run tails-custom-apt-sources - Then I should see only the 'feature-jessie' suite - - Scenario: build from a feature branch based on devel with dots in its name - Given I am working on the feature/live-boot-3.x branch based on devel - And config/APT_overlays.d contains 'feature-live-boot-3.x' - When I successfully run tails-custom-apt-sources - Then I should see the 'devel' suite - And I should see the 'feature-live-boot-3.x' suite - - Scenario: build from a branch that has no config/APT_overlays.d directory - Given I am working on the stable base branch - And the config/APT_overlays.d directory does not exist - When I run tails-custom-apt-sources - Then it should fail - - Scenario: build from a branch that has no config/base_branch file - Given I am working on the stable base branch - And the config/base_branch file does not exist - When I run tails-custom-apt-sources - Then it should fail - - Scenario: build from a branch where config/base_branch is empty - Given I am working on the stable base branch - And the config/base_branch file is empty - When I run tails-custom-apt-sources - Then it should fail diff --git a/features/checks.feature b/features/checks.feature deleted file mode 100644 index 24d35943..00000000 --- a/features/checks.feature +++ /dev/null @@ -1,107 +0,0 @@ -@product -Feature: Various checks - - Scenario: AppArmor is enabled and has enforced profiles - Given I have started Tails from DVD without network and logged in - Then AppArmor is enabled - And some AppArmor profiles are enforced - - Scenario: A screenshot is taken when the PRINTSCREEN key is pressed - Given I have started Tails from DVD without network and logged in - And there is no screenshot in the live user's Pictures directory - When I press the "PRINTSCREEN" key - Then a screenshot is saved to the live user's Pictures directory - - Scenario: VirtualBox guest modules are available - Given I have started Tails from DVD without network and logged in - When Tails has booted a 64-bit kernel - Then the VirtualBox guest modules are available - - Scenario: The shipped Tails OpenPGP keys are up-to-date - Given I have started Tails from DVD without network and logged in - Then the OpenPGP keys shipped with Tails will be valid for the next 3 months - - Scenario: The Tails Debian repository key is up-to-date - Given I have started Tails from DVD without network and logged in - Then the shipped Debian repository key will be valid for the next 3 months - - @doc @fragile - Scenario: The "Report an Error" launcher will open the support documentation - Given I have started Tails from DVD without network and logged in - And the network is plugged - And Tor is ready - And all notifications have disappeared - When I double-click the Report an Error launcher on the desktop - Then the support documentation page opens in Tor Browser - - Scenario: The live user is setup correctly - Given I have started Tails from DVD without network and logged in - Then the live user has been setup by live-boot - And the live user is a member of only its own group and "audio cdrom dialout floppy video plugdev netdev scanner lp lpadmin vboxsf" - And the live user owns its home dir and it has normal permissions - - @fragile - Scenario: No initial network - Given I have started Tails from DVD without network and logged in - And I wait between 30 and 60 seconds - Then the Tor Status icon tells me that Tor is not usable - When the network is plugged - Then Tor is ready - And the Tor Status icon tells me that Tor is usable - And all notifications have disappeared - And the time has synced - - @fragile - Scenario: The 'Tor is ready' notification is shown when Tor has bootstrapped - Given I have started Tails from DVD without network and logged in - And the network is plugged - When I see the 'Tor is ready' notification - Then Tor is ready - - @fragile - Scenario: The tor process should be confined with Seccomp - Given I have started Tails from DVD without network and logged in - And the network is plugged - And Tor is ready - Then the running process "tor" is confined with Seccomp in filter mode - - @fragile - Scenario: No unexpected network services - Given I have started Tails from DVD without network and logged in - When the network is plugged - And Tor is ready - Then no unexpected services are listening for network connections - - Scenario: The emergency shutdown applet can shutdown Tails - Given I have started Tails from DVD without network and logged in - When I request a shutdown using the emergency shutdown applet - Then Tails eventually shuts down - - Scenario: The emergency shutdown applet can reboot Tails - Given I have started Tails from DVD without network and logged in - When I request a reboot using the emergency shutdown applet - Then Tails eventually restarts - - Scenario: tails-debugging-info does not leak information - Given I have started Tails from DVD without network and logged in - Then tails-debugging-info is not susceptible to symlink attacks - - Scenario: Tails shuts down on DVD boot medium removal - Given I have started Tails from DVD without network and logged in - When I eject the boot medium - Then Tails eventually shuts down - - #10720 - @fragile - Scenario: Tails shuts down on USB boot medium removal - Given I have started Tails without network from a USB drive without a persistent partition and logged in - When I eject the boot medium - Then Tails eventually shuts down - - Scenario: The Tails Greeter "disable all networking" option disables networking within Tails - Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen - And I enable more Tails Greeter options - And I disable all networking in the Tails Greeter - And I log in to a new session - And the Tails desktop is ready - Then no network interfaces are enabled diff --git a/features/config/defaults.yml b/features/config/defaults.yml deleted file mode 100644 index 9c312146..00000000 --- a/features/config/defaults.yml +++ /dev/null @@ -1,36 +0,0 @@ -CAPTURE: false -CAPTURE_ALL: false -MAX_NEW_TOR_CIRCUIT_RETRIES: 10 -PAUSE_ON_FAIL: false -SIKULI_RETRY_FINDFAILED: false -TMPDIR: "/tmp/DebianToaster" - -Unsafe_SSH_private_key: | - -----BEGIN RSA PRIVATE KEY----- - MIIEowIBAAKCAQEAvMUNgUUM/kyuo26m+Xw7igG6zgGFMFbS3u8m5StGsJOn7zLi - J8P5Mml/R+4tdOS6owVU4RaZTPsNZZK/ClYmOPhmNvJ04pVChk2DZ8AARg/TANj3 - qjKs3D+MeKbk1bt6EsA55kgGsTUky5Ti8cc2Wna25jqjagIiyM822PGG9mmI6/zL - YR6QLUizNaciXrRM3Q4R4sQkEreVlHeonPEiGUs9zx0swCpLtPM5UIYte1PVHgkw - ePsU6vM8UqVTK/VwtLLgLanXnsMFuzq7DTAXPq49+XSFNq4JlxbEF6+PQXZvYZ5N - eW00Gq7NSpPP8uoHr6f1J+mMxxnM85jzYtRx+QIDAQABAoIBAA8Bs1MlhCTrP67q - awfGYo1UGd+qq0XugREL/hGV4SbEdkNDzkrO/46MaHv1aVOzo0q2b8r9Gu7NvoDm - q51Mv/kjdizEFZq1tvYqT1n+H4dyVpnopbe4E5nmy2oECokbQFchRPkTnMSVrvko - OupxpdaHPX8MBlW1GcLRBlE00j/gfK1SXX5rcxkF5EHVND1b6iHddTPearDbU8yr - wga1XO6WeohAYzqmGtMD0zk6lOk0LmnTNG6WvHiFTAc/0yTiKub6rNOIEMS/82+V - l437H0hKcIN/7/mf6FpqRNPJTuhOVFf+L4G/ZQ8zHoMGVIbhuTiIPqZ/KMu3NaUF - R634jckCgYEA+jJ31hom/d65LfxWPkmiSkNTEOTfjbfcgpfc7sS3enPsYnfnmn5L - O3JJzAKShSVP8NVuPN5Mg5FGp9QLKrN3kV6QWQ3EnqeW748DXMU6zKGJQ5wo7ZVm - w2DhJ/3PAuBTL/5X4mjPQL+dr86Aq2JBDC7LHJs40I8O7UbhnsdMxKcCgYEAwSXc - 3znAkAX8o2g37RiAl36HdONgxr2eaGK7OExp03pbKmoISw6bFbVpicBy6eTytn0A - 2PuFcBKJRfKrViHyiE8UfAJ31JbUaxpg4bFF6UEszN4CmgKS8fnwEe1aX0qSjvkE - NQSuhN5AfykXY/1WVIaWuC500uB7Ow6M16RDyF8CgYEAqFTeNYlg5Hs+Acd9SukF - rItBTuN92P5z+NUtyuNFQrjNuK5Nf68q9LL/Hag5ZiVldHZUddVmizpp3C6Y2MDo - WEDUQ2Y0/D1rGoAQ1hDIb7bbAEcHblmPSzJaKirkZV4B+g9Yl7bGghypfggkn6o6 - c3TkKLnybrdhZpjC4a3bY48CgYBnWRYdD27c4Ycz/GDoaZLs/NQIFF5FGVL4cdPR - pPl/IdpEEKZNWwxaik5lWedjBZFlWe+pKrRUqmZvWhCZruJyUzYXwM5Tnz0b7epm - +Q76Z1hMaoKj27q65UyymvkfQey3ucCpic7D45RJNjiA1R5rbfSZqqnx6BGoIPn1 - rLxkKwKBgDXiWeUKJCydj0NfHryGBkQvaDahDE3Yigcma63b8vMZPBrJSC4SGAHJ - NWema+bArbaF0rKVJpwvpkZWGcr6qRn94Ts0kJAzR+VIVTOjB9sVwdxjadwWHRs5 - kKnpY0tnSF7hyVRwN7GOsNDJEaFjCW7k4+55D2ZNBy2iN3beW8CZ - -----END RSA PRIVATE KEY----- -Unsafe_SSH_public_key: = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC8xQ2BRQz+TK6jbqb5fDuKAbrOAYUwVtLe7yblK0awk6fvMuInw/kyaX9H7i105LqjBVThFplM+w1lkr8KViY4+GY28nTilUKGTYNnwABGD9MA2PeqMqzcP4x4puTVu3oSwDnmSAaxNSTLlOLxxzZadrbmOqNqAiLIzzbY8Yb2aYjr/MthHpAtSLM1pyJetEzdDhHixCQSt5WUd6ic8SIZSz3PHSzAKku08zlQhi17U9UeCTB4+xTq8zxSpVMr9XC0suAtqdeewwW7OrsNMBc+rj35dIU2rgmXFsQXr49Bdm9hnk15bTQars1Kk8/y6gevp/Un6YzHGczzmPNi1HH5 amnesia@amnesia" diff --git a/features/dhcp.feature b/features/dhcp.feature deleted file mode 100644 index 18874dbf..00000000 --- a/features/dhcp.feature +++ /dev/null @@ -1,22 +0,0 @@ -@product @fragile -Feature: Getting a DHCP lease without leaking too much information - As a Tails user - when I connect to a network with a DHCP server - I should be able to connect to the Internet - and the hostname should not have been leaked on the network. - - Background: - Given I have started Tails from DVD without network and logged in - And I capture all network traffic - And the network is plugged - And Tor is ready - And all notifications have disappeared - And available upgrades have been checked - - Scenario: Getting a DHCP lease with the default NetworkManager connection - Then the hostname should not have been leaked on the network - - Scenario: Getting a DHCP lease with a manually configured NetworkManager connection - When I add a wired DHCP NetworkManager connection called "manually-added-con" - And I switch to the "manually-added-con" NetworkManager connection - Then the hostname should not have been leaked on the network diff --git a/features/domains/default.xml b/features/domains/default.xml deleted file mode 100644 index f1004dcf..00000000 --- a/features/domains/default.xml +++ /dev/null @@ -1,59 +0,0 @@ - - DebianToaster - 1310720 - 1310720 - 1 - - hvm - - - - - - - - - - destroy - restart - restart - - /usr/bin/qemu-system-x86_64 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -