DotNetKick.com is an open-source project. Please report any bugs and let us know your great suggestions. Currently running svn revision 620 (rss)

Kick Spy!, Kick Zeitgeist and Kick Widgets

13
kicks
published 1 year ago, submitted by gojko 1 year ago

gojko.net — User interface tests are a bit tricky – it is easy to get carried away and waste quite a lot of time, without getting any real benefits. However, if planned properly, automated UI tests can have a great effect on the project. Here are a few tips on how to make the most of automated user-interface tests.

tags: | tag it

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:

Comments:
Summary: "UI testing is hard, but sometimes it's a good idea--if only to prevent yourself from looking bad." More of a ramble than anything new or informative about testing. The bottom line for me on UI testing is that it's really damned hard to do, let alone to do it right. You will spend a LOT of time coding custom control testers if you have the least bit customized GUI. Most frameworks can turn into a black hole for your valuable development hours. Time is almost always better spent unit testing your business logic after you've properly separated it from your UI classes. Even the author admits that there are usually a limited number of end-to-end scenarios that need full UI testing. Write a script and have someone on your team run through it during key milestones...or do it yourself.
posted by jesse 1 year ago



information Login or create an account to comment on this story
 

Sponsored Link: www.carlist.ie

Search:

Ads via The Lounge