670698 - Test Suites should be able to contain Test cases in any state.

Status: RESOLVED FIXED

(Mozilla QA :: Case Conductor-Platform, enhancement)

Description

[Cameron Dawson [:camd]]

When a Test Suite is added to a Test Run, only "active" cases should be added.  But a user should be able to add unapproved test cases to a test suite at time of creation.

The need is this.  If 200 new cases are added, they currently must be approved before they can be added to the test suite to which they are intended.  If they are a mishmash of cases intended for several suites, then it becomes an arduous chore to sort them out, when they could easily have been just tagged for the suite they were intended for at create time.

Test suites should be able to contain test cases in ANY state.  If a suite contains no active tests, and is added to a test run, then an error should be returned warning the user that no cases were added.

Comment 1

[Vadim]

OK, that's the way I'm planning to change it:
1. if single non active test case is being added to test run, system will throw IncludingNotActivatedEntityException;
2. if single test suite is being added to test run and all of the test cases are not active, system will throw IncludingNotActivatedEntityException. If at least one is active, then no error will be thrown;
3. if single test plan is being added to test run and all of the test cases included in all test suites are not active, system will throw IncludingNotActivatedEntityException. If at least one is active, then no error will be thrown;

I think, this should cover all the scenarios without losing consistency in behavior...