add integration-test scope

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: Artifacts and Repositories
  • Labels:
    None

Issue Links

relates to

Improvement - An improvement or enhancement to an existing feature or task. MNG-591 Integration tests lifecycle

  • Blocker - Blocks development and/or testing work, production could not run
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
John Casey added a comment -

how is providing integration-test phase dependencies any different than providing an <integrationTestSourceDirectory/>?

In other words, if we're leaving the source directory to be specified by cactus, etc. (because they may need different sources, or none), then why can we assume that all integration tests will have the same dependency needs?

Show
John Casey added a comment - how is providing integration-test phase dependencies any different than providing an <integrationTestSourceDirectory/>? In other words, if we're leaving the source directory to be specified by cactus, etc. (because they may need different sources, or none), then why can we assume that all integration tests will have the same dependency needs?
Hide
Permalink
John Casey added a comment -

just trying to collect all itest-related stuff, and since I've got this one on my radar, this is as good of a focal point as any.

Show
John Casey added a comment - just trying to collect all itest-related stuff, and since I've got this one on my radar, this is as good of a focal point as any.
Hide
Permalink
Brett Porter added a comment -

superseded by MNG-591

Show
Brett Porter added a comment - superseded by MNG-591

People

  • Assignee:
    John Casey
    Reporter:
    Brett Porter
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: