Well, after searching high and low for automation tools that support WinCE/PocketPC (Windows Mobile) I've only come across 3 tools.
Only one of those tools is a comprehensive automation tool, so as soon as the Capital expenditure is approved, we'll be getting the vendor "TestQuest" in for a proof of concept, evaluation period, and if all goes well, purchase.
I don't know if anyone else in this group works with mobile devices, but just in case, I'll make posts on our progress. Up until now, our automation on Mobile devices has been limited to test harnesses we write ourselves.
On the Desktop side of things, We just got SilkTest. We don't do a whole lot of desktop development, so automation will be a new thing on that front as well. I'm sure that once we start ramping up to use it, I'll be posting questions - so please be ready to help. We went with SilkTest because they support .NET application testing, and we're moving that way with our Windows development.
Comments? Suggestions on ways to make implementation go smoothly? I'm all ears!
Joe,
We have been using TestQuest for 4 years. It is an excellent choice
for non obtrusive testing on "non standard" operating systems like
WinCE and Linux and QNX. I would be happy to try to answer TestQuest
questions if they arise.
Paul
Paul Hallowell
Validation Lab Supervisor
AMD - Personal Connectivity Solutions Group
(303)774-5277 office
(303)774-5801 fax
(720)352-0533 cell
paul.hallow...@amd.com
http://www.amd.com/embeddedprocessors
On 5/19/05, Joe Vincent <joej...@hotmail.com> wrote:
> Well, after searching high and low for automation tools that support
> WinCE/PocketPC (Windows Mobile) I've only come across 3 tools.
> Only one of those tools is a comprehensive automation tool, so as soon
> as the Capital expenditure is approved, we'll be getting the vendor
> "TestQuest" in for a proof of concept, evaluation period, and if all
> goes well, purchase.
> I don't know if anyone else in this group works with mobile devices,
> but just in case, I'll make posts on our progress. Up until now, our
> automation on Mobile devices has been limited to test harnesses we
> write ourselves.
> On the Desktop side of things, We just got SilkTest. We don't do a
> whole lot of desktop development, so automation will be a new thing on
> that front as well. I'm sure that once we start ramping up to use it,
> I'll be posting questions - so please be ready to help. We went with
> SilkTest because they support .NET application testing, and we're
> moving that way with our Windows development.
> Comments? Suggestions on ways to make implementation go smoothly?
> I'm all ears!
I'm also new to TestQuest. We're preparing to use it for a WinCE-based embedded system. I'm going through the manual and playing around with Script Recorder, Fuction Administrator, etc.
So far, it seems to me that you can (1) record scripts, (2) write scripts, (3) complile scripts as DLLs, and (4) import DLL-based functions into scripts. Have I missed anything? What is the 'best' way to use TQ for a fairly large project?
|
