Why do SWEA developers invent such a nonstandard SWEA programming model?
10 views
Skip to first unread message
gerz
Jan 29, 2009, 12:38:01 PM1/29/09
to SWExplorerAutomation
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...
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...
Alex Furman
Jan 29, 2009, 2:29:07 PM1/29/09
to swexplorer...@googlegroups.com
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: sadi...@mail.ru
> To: swexplorer...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages