In testing, the UI is not necessarily the best place to start. I am not
stating that testing the UI is not part of the testing process, but that
tests on your underlying code are more important, by far.
As far as UI testing, there are frameworks out there. Mercury makes a win UI
tester, for example. There are others. Most are rather pricey, which leads
back to making sure you really need to automate UI testing prior to heading
down this path. In most cases, moving most of your app code out of the UI
will eliminate the need for a full UI test framework.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog
http://gregorybeamer.spaces.live.com/lists/feed.rss
or just read it:
http://gregorybeamer.spaces.live.com/
********************************************
| Think outside the box! |
********************************************
"sherifffruitfly" <sh*************@gmail.comwrote in message
news:63**********************************@i20g2000 prf.googlegroups.com...
Hi all,
I want to write up a test automation class library for our in-house
app, which I've never done before.
The app is functionally a 2-tier GUI-datalayer one, and I basically
want to automate user processes such as:
1) entering a bit of text into one of the textboxes,
2) moving to the next gui screen (thus committing gui data to the db),
3) and then hitting the "previous screen" button, returning to the
original screen, which should update with the new data.
The app is written in C# 2.0.
Anybody have any good automation resources?
Thanks!
cdj
