Feature #10706

Tag scenarios that rely on the shipped documentation

Added by bertagaz 2015-12-03 07:00:18 . Updated 2015-12-13 05:24:07 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Continuous Integration
Target version:
Tails_1.8
Start date:
2015-12-03
Due date:
% Done:

100%

Feature Branch:
Tails:test/10706-add-doc-tags
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Deliverable for:
267

Description

As decided in Feature #10492, we don’t want to run the whole test suite on branches that only change the Tails documentation, but only scenarios that relies on the documentation shipped within Tails.

The chosen implementation requires us to mark this kind of scenarios as @doc in order to do so.

Subtasks

Related issues

Blocks Tails - Feature #10707: Test only @doc scenarios for documentation branches Resolved 2015-12-03
Blocked by Tails - Feature #10492: Decide if Jenkins should test our documentation branches Resolved 2015-11-05

History

#1 Updated by bertagaz 2015-12-03 07:03:16

#2 Updated by bertagaz 2015-12-03 07:04:19

  • blocks Feature #10707: Test only @doc scenarios for documentation branches added

#3 Updated by bertagaz 2015-12-03 07:04:50

  • blocked by Feature #10492: Decide if Jenkins should test our documentation branches added

#4 Updated by bertagaz 2015-12-03 07:05:04

  • blocks #8668 added

#5 Updated by bertagaz 2015-12-03 07:05:43

  • Subject changed from Tag scenarios that relies on the shipped documentation to Tag scenarios that rely on the shipped documentation

#6 Updated by bertagaz 2015-12-03 07:15:41

  • Status changed from Confirmed to In Progress

Applied in changeset commit:e636c1f127c3fd5e7ab55d6a0b4557e9dbb00f56.

#7 Updated by bertagaz 2015-12-03 07:18:54

  • Assignee set to intrigeri
  • QA Check set to Ready for QA
  • Feature Branch set to Tails:test/10706-add-doc-tags

I’ve searched through the test suite for that kind of scenarios and found 4 of them that I’ve tagged in the dedicated branch. Please review and if happy merge into stable, then stable into devel.

#8 Updated by intrigeri 2015-12-05 09:43:36

  • Status changed from In Progress to Fix committed
  • % Done changed from 0 to 100

Applied in changeset commit:49c101ff2af5a86f1cf2cd3e811d44c6efac4da6.

#9 Updated by intrigeri 2015-12-05 09:49:01

  • Assignee deleted (intrigeri)
  • QA Check changed from Ready for QA to Pass
  • Starter changed from Yes to No

#10 Updated by intrigeri 2015-12-13 05:24:07

  • Status changed from Fix committed to Resolved

(I want to close Feature #10707 as resolved.)