Enforcement of "covered_by"

• How tests are added to “Other tests” ?

  • When someone adds a link to Test Definition from a Milestone artifact with “covered by” nature

    • Eg. In “Release 1.0”, I add “Ensure page is loaded” test with “covered_by” nature.

  • When, in a campaign associated with a Milestone, an existing Test, not already linked to a Backlog Item of this milestone is added.

    • Eg. In “Release 1.0”, I created “Validation RC1” campaign.

    • In “Validation RC1” campaign, I select “Load test with 100 users”. This test is not linked with a story of “Release 1.0”

    • Then “Load test with 100 users” is added to the campaign

    • And “Load test with 100 users” is linked to “Release 1.0” with “covered_by” nature

  • Extension of previous point: it also works when one creates a new test directly in the campaign.

• When an “Other test” is linked to a Backlog Item of a Milestone, the link between Milestone and test is removed

  • Given “Load test with 100 users” was added to “Other tests”

  • When I link “Load test with 100 users” to “Fix performance issue” bug of “Release 1.0”

  • Then “Load test with 100 users” is removed from “Release 1.0” linked tests.

  • And “Load test with 100 users” is no longer displayed in “Other tests”

• Places where we need to check the link consistencies and update/create links

  • Create new “test_execution” route (from a campaign, when associated with a Milestone)

  • When a Backlog Item has a new link “covered_by” (regardless of the source)

    • Need to check when Backlog Item is present in several Milestones

• When a test, not attached to any Backlog Items, is removed from the last campaign, it must be removed from the “Other tests” as well.

Management of display:

• “Other tests” lists Test Definitions that are linked by the milestone with “covered_by” nature

• Need new REST route to get all tests that covers a milestone

• Creation of a new campaign from “Milestone tests” should also take “Other tests”