From 51680b6ebb645d37ebdfcd122ca163b3a638aefa Mon Sep 17 00:00:00 2001 From: Tails developers Date: Fri, 19 Dec 2014 00:40:08 +0100 Subject: files copied from https://git-tails.immerda.ch/tails - many thanks to the tails developers for their nice work and documentation of it - these files have been released under the GNU General Public License version 3 or (at your option) any later version features/images has been omitted --- features/build.feature | 75 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 75 insertions(+) create mode 100644 features/build.feature (limited to 'features/build.feature') diff --git a/features/build.feature b/features/build.feature new file mode 100644 index 00000000..4cc0b650 --- /dev/null +++ b/features/build.feature @@ -0,0 +1,75 @@ +@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 + Given I am working on the stable branch + And last released version mentioned in debian/changelog is 1.0 + And Tails 1.0 has not been released yet + When I run tails-custom-apt-sources + Then I should see the 'stable' suite + Then I should not see the '1.0' suite + + Scenario: build from a tagged stable branch + Given Tails 0.10 has been released + And last released version mentioned in debian/changelog is 0.10 + And I am working on the stable branch + When I run tails-custom-apt-sources + Then I should see the '0.10' suite + + Scenario: build from a bugfix branch for a stable release + Given Tails 0.10 has been released + And last released version mentioned in debian/changelog is 0.10 + And I am working on the bugfix/disable_gdomap branch based on 0.10 + When I run tails-custom-apt-sources + Then I should see the '0.10' suite + And I should see the 'bugfix-disable-gdomap' suite + + Scenario: build from an untagged testing branch + Given I am working on the testing branch + And last released version mentioned in debian/changelog is 0.11 + And Tails 0.11 has not been released yet + When I run tails-custom-apt-sources + Then I should see the 'testing' suite + And I should not see the '0.11' suite + + Scenario: build from a tagged testing branch + Given I am working on the testing branch + And last released version mentioned in debian/changelog is 0.11 + And Tails 0.11 has been released + When I run tails-custom-apt-sources + Then I should see the '0.11' suite + And I should not see the 'testing' suite + + Scenario: build a release candidate from a tagged testing branch + Given I am working on the testing branch + And Tails 0.11 has been released + And last released version mentioned in debian/changelog is 0.12~rc1 + And Tails 0.12-rc1 has been tagged + When I run tails-custom-apt-sources + Then I should see the '0.12-rc1' suite + And I should not see the 'testing' suite + + Scenario: build from the devel branch + Given I am working on the devel branch + When I run tails-custom-apt-sources + Then I should see the 'devel' suite + + Scenario: build from the experimental branch + Given I am working on the experimental branch + When I run tails-custom-apt-sources + Then I should see the 'experimental' suite + + Scenario: build from a feature branch based on devel + Given I am working on the feature/icedove branch based on devel + When I run tails-custom-apt-sources + Then I should see the 'devel' suite + And I should see the 'feature-icedove' 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 + When I run tails-custom-apt-sources + Then I should see the 'devel' suite + And I should see the 'feature-live-boot-3.x' suite -- cgit v1.2.3-70-g09d2