Re: [cosmos-dev] Junits or test steps not available

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [cosmos-dev] Junits or test steps not available

From: David Whiteman <David_Whiteman@xxxxxxxxxx>
Date: Wed, 16 Jan 2008 10:20:32 -0500
Delivered-to: cosmos-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/listinfo/cosmos-dev>
List-help: <mailto:cosmos-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/cosmos-dev>, <mailto:cosmos-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/cosmos-dev>, <mailto:cosmos-dev-request@eclipse.org?subject=unsubscribe>

Shivvy,

Some of these are not ERs, but are defects. I don't think QA is responsible for verifying defects, only ERs (i.e. only bugzilla entries that have Severity = enhancement). My understanding is that defects should be verified by the person (developer) who opened the defect.

David

cosmos-dev-bounces@xxxxxxxxxxx wrote on 01/16/2008 10:02:51 AM: > There are no Junits or test steps available on the i8 ERs 210438, 209227, 209569, 208584, > 209226, 209223, 208603, 214547, 209367, 209244, 209224
> Regards
> Shivashankari

Follow-Ups:
- [cosmos-dev] i8 ERs where JUnits or unit test steps not available
  - From: Mohsin, Jimmy

References:
- [cosmos-dev] Junits or test steps not available
  - From: N, Shivashankari

Prev by Date: [cosmos-dev] Junits or test steps not available
Next by Date: [cosmos-dev] COSMOS use casereview to preempt Standing Conference Call on COSMOSData Reporting for 17-Jan
Previous by thread: [cosmos-dev] Junits or test steps not available
Next by thread: [cosmos-dev] i8 ERs where JUnits or unit test steps not available
Index(es):
- Date
- Thread

Breadcrumbs