2018 up to now | 2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007

(older archive entries before 2007 are not shown here, but included in the onsite-search)

Mailing List - Entries of 2007

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[QF-Test] GUI test productivity

  • Subject: [QF-Test] GUI test productivity
  • From: Hans Schwaebli <hans_schwaebli@?.com>
  • Date: Fri, 11 May 2007 07:30:05 -0700 (PDT)

How long does it take to implement a GUI test? I mean the rule of the thumb.
If programming a part of the software (server and client) took X man hours, how long does it take to implement the GUI test for it?
Currently it seems that my bosses want very quick results, forcing me to use the pattern "copy and paste and do not change", which in the long run is not productive.
GUI tests are seen more as a cost than as a valuable investment right now in my company.
Any helpful ideas on this?

Got a little couch potato?
Check out fun summer activities for kids.