• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: [Wonder-disc] ERSelenium without ERExtensions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Wonder-disc] ERSelenium without ERExtensions


  • Subject: Re: [Wonder-disc] ERSelenium without ERExtensions
  • From: Denis Frolov <email@hidden>
  • Date: Sat, 30 Jun 2007 15:01:22 +0400

Hi Chuck,

On Jun 27, 2007, at 10:58 PM, Chuck Hill wrote:

On Jun 27, 2007, at 5:53 AM, Michael Bushkov wrote:

Chuck Hill wrote:
One of my goals is to _not_ be the person who writes and maintains
the functional tests.  Because of this, it is important to keep the
tests separate from the applications and frameworks that it tests.

We think of selenium tests as about useful addition to Unit tests -
and
therefore we use different approach - the person who writes a part of
the applications should prepare tests for this part. And that's why we
treat selenium tests as a part of the application and store them in
the
application's folder.

Yes, that is different from my use / intention. I try to keep my UI components very simple. So simple that they don't need tests. Obviously, using D2W, you have very different concerns and very different test needs. I have never worked on automated testing for a D2W app, I can see that would be quite a challenge.

I don't really think that there is any difference between testing D2W or non-D2W apps since we focus on testing user scenarios and not components. One can easily break non-D2W app by renaming an attribute of an entity and you really want an easy way to check for broken bindings even if all of your unit tests are ok. Also, it is you as a developer (not QA team) who needs to check the scenarios right after refactoring and before commiting.


Another thing is that tests maintainence leads to additional work so we try to write as few tests as possible and check only things that tend to break or are mission-critical. In our practice this helps discovering 90% bugs with 10% effort. Remaining 10% are normally discovered via log4j email error alerts or customer bug reports. And since these 10% bugs are not mission-critical our customers are still happy and we don't have to spend much time mainaining tests.

--
Denis
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Re: [Wonder-disc] ERSelenium without ERExtensions (From: Chuck Hill <email@hidden>)
 >Re: [Wonder-disc] ERSelenium without ERExtensions (From: Steven Mark McCraw <email@hidden>)
 >Re: [Wonder-disc] ERSelenium without ERExtensions (From: Chuck Hill <email@hidden>)
 >Re: [Wonder-disc] ERSelenium without ERExtensions (From: Michael Bushkov <email@hidden>)
 >Re: [Wonder-disc] ERSelenium without ERExtensions (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: Blank page after LongResponse !!! :-(
  • Next by Date: Re: [Wonder-disc] ERSelenium without ERExtensions
  • Previous by thread: Re: [Wonder-disc] ERSelenium without ERExtensions
  • Next by thread: Re: [Wonder-disc] ERSelenium without ERExtensions
  • Index(es):
    • Date
    • Thread