Tester segmentation
TestPartner:
- Scripting experienced.
CodedUI: -
Programming(C#, VB.Net) experienced.
Language support
TestPartner:
- VBA (Visual Basic for Application)
CodedUI: - C#,
VB.Net.
Intent aware recording – Recording testers intents
in the form of comments
TestPartner:
- Rich Comments while recording. Commenting is configurable to on/off.
CodedUI: - Same as
TestPartner
Usage of .Net Framework
TestPartner:
- Only through the .Net Interops available viz.
system.tlb, system.windows.forms.tlb
CodedUI: - Based on
.Net framework. In facts Coded UI Classes are extended from Unit Test
How are UI actions taken
TestPartner:
- TPOSI Library built into tool which inturn hooks
into the UI via MSAA or Win32API
CodedUI: - UI Actions
taken on Control via UIAutomation Namespace classes
which is next gen to MSAA
Wait For Ready (WFR) and auto wait and Auto
scroll
TestPartner:
- Testers need to code (script) for UI object being ready for action, Auto
wait is available as tool option. Auto scroll to bring control in focus is a
drawback.
CodedUI: - Strong WFR,
Auto wait and Auto Scroll
Object Maps
TestPartner:
- Flat Object Maps i.e. no DOM followed hence faster search of controls.
CodedUI: - Object
Maps are nothing but UI Map Class
Storage of Scripts
TestPartner:
- In SQL Server or MS Access Database.
CodedUI: - On File
System.
IE6 Support/ Browser Support
TestPartner:
- IE6 onwards supported, other browsers supported too.
CodedUI: - Support
for IE6 using extensibility packages. Only IE is supported as of this
writing.
Wait For Ready (WFR) and auto wait and Auto
scroll
TestPartner:
- Testers need to code (script) for UI object being ready for action, Auto
wait is available as tool option. Auto scroll to bring control in focus is a
drawback.
CodedUI: - Strong WFR,
Auto wait and Auto Scroll
Support for SAP
TestPartner:
- Strong.
CodedUI: - None. Not
on the roadmap either.
Support for Java Applications
TestPartner:
- Yes a reasonably good support.Also come with AOR(Active Object Recognition) for Java Aplets.
CodedUI: - None.
Available References (dlls)
TestPartner:
- Only COM and .Net
CodedUI: - All.COM,.NET and Web References.
Extensibility of Tool /Framework
TestPartner:
- Tool cannot be extended. Its only that by adding
.Net References one could make use of .Net assemblies of your application
under test.
CodedUI: - Has well
defined extensibility framework ready.
Checkpoints and parameterization support
TestPartner:
- well defined checkpoints available. Parameterization can be done using handwritten
code or wizards.
CodedUI: - Checkpoints
(Assertions) available. parameterization needs to be
handcoded.
In built Keyword or Visual test View?
TestPartner:
- Yes.
CodedUI: - It’s a Coders
tool so no visual test available out of box.
One place for developers
and testers?
TestPartner:
- definitely not. TestPartner has its own IDE.
CodedUI: - yes. All
done in one place VS 2010
Learning curve
TestPartner:
- Short. VBS testers can easily migrate to VBA
CodedUI: - Would
require Testers to grasp OOP and either or C# or VB.Net
|
You need to be a member of Quality Testing to add comments!
Join Quality Testing