Web Images Videos Maps News Shopping Gmail more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Why do SWEA developers invent such a nonstandard SWEA programming model?
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
gerz  
View profile  
 More options Jan 29, 12:38 pm
From: gerz <sadist...@mail.ru>
Date: Thu, 29 Jan 2009 09:38:01 -0800 (PST)
Local: Thurs, Jan 29 2009 12:38 pm
Subject: Why do SWEA developers invent such a nonstandard SWEA programming model?
The SWEA programming model consists of Scene and Controls which are
bound in runtime to IE UI elements. Could you give me the reasons for
inventing such a nonstandard architecture? Is it for making resilient
test scripts or for JavaScript/Ajax testing? For what? There are lots
of tools which allow automating web applications and I don't need to
create a file with scene and objects...

    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Alex Furman  
View profile  
 More options Jan 29, 2:29 pm
From: Alex Furman <alex_f...@hotmail.com>
Date: Thu, 29 Jan 2009 14:29:07 -0500
Local: Thurs, Jan 29 2009 2:29 pm
Subject: RE: Why do SWEA developers invent such a nonstandard SWEA programming model?

SWEA defines programming model which separates UI binding from code.  Most of the advanced UI testing tools use it.
It is simpler to visually define the UI binding using SWEA designer than to programmatically define it. It is also dramatically decreases time needed to fix it - in most cases only binding should be changed to fix broken automation script.

> Date: Thu, 29 Jan 2009 09:38:01 -0800> Subject: Why do SWEA developers invent such a nonstandard SWEA programming model?> From: sadist...@mail.ru> To: swexplorerautomation@googlegroups.com> > > The SWEA programming model consists of Scene and Controls which are> bound in runtime to IE UI elements. Could you give me the reasons for> inventing such a nonstandard architecture? Is it for making resilient> test scripts or for JavaScript/Ajax testing? For what? There are lots> of tools which allow automating web applications and I don't need to> create a file with scene and objects...> _________________________________________________________________

Windows Live™ Hotmail®:…more than just e-mail.
http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t2_hm_justgotbetter_...

    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google