[cdt-dev] GUI testing strategy

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

[cdt-dev] GUI testing strategy

From: John Camelon <jcamelon@xxxxxxxxxx>
Date: Wed, 25 Jun 2003 13:59:15 -0400
Delivered-to: cdt-dev@xxxxxxxxxxx
List-archive: <http://dev.eclipse.org/pipermail/cdt-dev/>
List-help: <mailto:cdt-dev-request@eclipse.org?subject=help>
List-subscribe: <http://dev.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <http://dev.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=unsubscribe>

Did we ever decide what tools/approach we were going to use to automate GUI testing?
If not, is this something we can discuss @ next week's call?
If so, what decision did we arrive at?

JohnC

Follow-Ups:
- Re: [cdt-dev] GUI testing strategy
  - From: Jeremy Handcock

Prev by Date: Re: [cdt-dev] Eclipse 2.1.1 support
Next by Date: Re: [cdt-dev] GUI testing strategy
Previous by thread: [cdt-dev] Eclipse 2.1.1 support
Next by thread: Re: [cdt-dev] GUI testing strategy
Index(es):
- Date
- Thread

Breadcrumbs