...

How We Compare

Assential has all of the key features any software testing professional could need to accomplish his testing goals. We have done our best to help future users of Ascential feel comfortable that they have done a thorough evaluation of their key features, costs and service requirements.

Did we get something wrong? Submit anonymous feedback!

AscentialTest

Integrated Test Planning:

Yes

Object Recognition:

Advanced

Object Repository:

Yes, AscentialTest collapses object hierarchy. Objects inherit path from parents which makes maintaining object locators much more robust

Test Frameworks (Productivity):

No framework needed. AscentialTest builds automatically as tests created

Foreign Language UX:

Yes

Supported Platforms:

Web Apps: 

Windows MFC: 

.Net Winforms: 

.Net WPF: 

PowerBuilder: 

PowerServer: 

PowerClient: 

OMNIS: 

Delphi: 

Java Swing: 

Terminal: 

CEF/Electron: 

MS Webview2: 

PDF: 

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes

Drag Generation of Actions:

Yes

Reusable Steps:

Yes

Scripting:

Visual and manual scripting

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

Yes

Manual Testing:

Yes

Test Management:

Yes

Test Execution Mgmt:

Yes

Integrated Version Control:

Yes

Integrated Test Management:

Yes, built-in with full data typing

AscentialTest

Integrated Test Planning:

Yes

Object Recognition:

Advanced

Object Repository:

Yes, AscentialTest collapses object hierarchy. Objects inherit path from parents which makes maintaining object locators much more robust

Test Frameworks (Productivity):

No framework needed. AscentialTest builds automatically as tests created

Foreign Language UX:

Yes

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Yes
.Net WPF: Yes
PowerBuilder: Yes
PowerServer: Yes
PowerClient: Yes
OMNIS: Yes
Delphi: Yes
Java Swing: Yes
Terminal: Yes
CEF/Electron: Yes
MS Webview 2: Yes
PDF: Yes

Drag Generation of Actions:

Yes

Reusable Steps:

Yes

Scripting:

Visual and manual scripting

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

Yes

Manual Testing:

Yes

Test Management:

Yes

Test Execution Mgmt:

Yes

Integrated Version Control:

Yes

Integrated Test Management:

Yes, built-in with full data typing

Ranorex Studio

Integrated Test Planning:

No

Object Recognition:

Each element has full path, fragile over time and time consuming to generate, poor recognition of complex objects like treeview, table or grid

Object Repository:

Yes, but there is not object hierarchy so if the depth of the hierarchy changes, many object paths might need to be updated

Test Frameworks (Productivity):

Framework takes a long time to build

Foreign Language UX:

Unmentioned

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Yes
.Net WPF: Yes
PowerBuilder: Unmentioned
PowerServer: No
PowerClient: No
OMNIS: No
Delphi: Yes
Java Swing: Yes
Terminal: No
CEF/Electron: Yes
MS Webview 2: No
PDF: No

Drag Generation of Actions:

Yes

Reusable Steps:

Yes

Scripting:

Manual scripting and limited visual scripting

Parallel Execution:

No

Integrated Defect Tracking:

Partial

Test Localization:

Partial

Test Portability:

No

Manual Testing:

No

Test Management:

No

Test Execution Mgmt:

No

Integrated Version Control:

Partial

Integrated Test Management:

Partial, uses underlying Excel of AceOleDB

AscentialTest

Integrated Test Planning:

Yes

Object Recognition:

Advanced

Object Repository:

Yes, AscentialTest collapses object hierarchy. Objects inherit path from parents which makes maintaining object locators much more robust

Test Frameworks (Productivity):

No framework needed. AscentialTest builds automatically as tests created

Foreign Language UX:

Yes

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Yes
.Net WPF: Yes
PowerBuilder: Yes
PowerServer: Yes
PowerClient: Yes
OMNIS: Yes
Delphi: Yes
Java Swing: Yes
Terminal: Yes
CEF/Electron: Yes
MS Webview 2: Yes
PDF: Yes

Drag Generation of Actions:

Yes

Reusable Steps:

Yes

Scripting:

Visual and manual scripting

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

Yes

Manual Testing:

Yes

Test Management:

Yes

Test Execution Mgmt:

Yes

Integrated Version Control:

Yes

Integrated Test Management:

Yes, built-in with full data typing

TestComplete

Integrated Test Planning:

Yes

Object Recognition:

Test Complete comes closest to AscentialTest in object recognition. Without the snapshot, it takes more time to test and maintain object definitions

Object Repository:

Similar to Selenium. No object hierarchy. Each object is identified from top to bottom. Alias permits shorter names but it doesn’t resolve issue of object hierarchy changing in future.

Test Frameworks (Productivity):

Does not appear to have appstates, some framework creation appears to be needed

Foreign Language UX:

Unmentioned

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Yes
.Net WPF: Yes
PowerBuilder: Yes (no test API)
PowerServer: Yes (no test API)
PowerClient: Yes (no test API)
OMNIS: No
Delphi: Yes
Java Swing: Yes
Terminal: No
CEF/Electron: Yes
MS Webview 2: No
PDF: Unmentioned

Drag Generation of Actions:

via Recording

Reusable Steps:

Yes

Scripting:

Assisted scripting with autocomplete

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

Unmentioned

Manual Testing:

No

Test Management:

Yes

Test Execution Mgmt:

Yes

Integrated Version Control:

Yes

Integrated Test Management:

Some, Parameters and Variables are stored at project level, Data is accessed from spreadsheets, external files and databases. They do not have built-in datatables, the mapping to data sources for data driven tests is really tedious and time consuming

AscentialTest

Integrated Test Planning:

Yes

Object Recognition:

Advanced

Object Repository:

Yes, AscentialTest collapses object hierarchy. Objects inherit path from parents which makes maintaining object locators much more robust

Test Frameworks (Productivity):

No framework needed. AscentialTest builds automatically as tests created

Foreign Language UX:

Yes

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Yes
.Net WPF: Yes
PowerBuilder: Yes
PowerServer: Yes
PowerClient: Yes
OMNIS: Yes
Delphi: Yes
Java Swing: Yes
Terminal: Yes
CEF/Electron: Yes
MS Webview 2: Yes
PDF: Yes

Drag Generation of Actions:

Yes

Reusable Steps:

Yes

Scripting:

Visual and manual scripting

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

Yes

Manual Testing:

Yes

Test Management:

Yes

Test Execution Mgmt:

Yes

Integrated Version Control:

Yes

Integrated Test Management:

Yes, built-in with full data typing

Eggplant

Integrated Test Planning:

No

Object Recognition:

Object recognition is based on images and OCR

Object Repository:

There is no concept of an object repository

Test Frameworks (Productivity):

For simple tests, it appears to be a quick and easy process

Foreign Language UX:

Unmentioned

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Yes
.Net WPF: Yes
PowerBuilder: Yes
PowerServer: Yes
PowerClient: Yes
OMNIS: Yes
Delphi: Yes
Java Swing: Yes
Terminal: Yes
CEF/Electron: Yes
MS Webview 2: Yes
PDF: No

Drag Generation of Actions:

via Recording

Reusable Steps:

Yes

Scripting:

Yes, assisted scripting with autocomplete

Parallel Execution:

No

Integrated Defect Tracking:

Possibly

Test Localization:

Possibly

Test Portability:

No

Manual Testing:

No

Test Management:

Additional product required

Test Execution Mgmt:

Additional product required

Integrated Version Control:

No

Integrated Test Management:

None

AscentialTest

Integrated Test Planning:

Yes

Object Recognition:

Advanced

Object Repository:

Yes, AscentialTest collapses object hierarchy. Objects inherit path from parents which makes maintaining object locators much more robust

Test Frameworks (Productivity):

No framework needed. AscentialTest builds automatically as tests created

Foreign Language UX:

Yes

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Yes
.Net WPF: Yes
PowerBuilder: Yes
PowerServer: Yes
PowerClient: Yes
OMNIS: Yes
Delphi: Yes
Java Swing: Yes
Terminal: Yes
CEF/Electron: Yes
MS Webview 2: Yes
PDF: Yes

Drag Generation of Actions:

Yes

Reusable Steps:

Yes

Scripting:

Visual and manual scripting

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

Yes

Manual Testing:

Yes

Test Management:

Yes

Test Execution Mgmt:

Yes

Integrated Version Control:

Yes

Integrated Test Management:

Yes, built-in with full data typing

Tosca

Integrated Test Planning:

No

Object Recognition:

Each element has full path, fragile over time and time consuming to generate, poor recognition of complex objects like treeview, table or grid

Object Repository:

Their solution is most similar to Selenium. There is no object hierarchy. Each object is identified from top to bottom.

Test Frameworks (Productivity):

Lots of dialogs and user steps to get work done. Not efficient

Foreign Language UX:

Unmentioned

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Unmentioned
.Net WPF: Unmentioned
PowerBuilder: Yes (out of date)
PowerServer: No
PowerClient: No
OMNIS: No
Delphi: Unmentioned
Java Swing: Unmentioned
Terminal: Claimed
CEF/Electron: Unmentioned
MS Webview 2: No
PDF: No

Drag Generation of Actions:

via Dropdowns

Reusable Steps:

Yes

Scripting:

Not described

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

No

Manual Testing:

No

Test Management:

Additional product required

Test Execution Mgmt:

No

Integrated Version Control:

No

Integrated Test Management:

Yes

Ranorex Studio

Integrated Test Planning:

No

Object Recognition:

Each element has full path, fragile over time and time consuming to generate, poor recognition of complex objects like treeview, table or grid

Object Repository:

Yes, but there is not object hierarchy so if the depth of the hierarchy changes, many object paths might need to be updated

Test Frameworks (Productivity):

Framework takes a long time to build

Foreign Language UX:

Unmentioned

Supported Platforms:

Web Apps: 

Windows MFC: 

.Net Winforms: 

.Net WPF: 

PowerBuilder: 

PowerServer: 

PowerClient: 

OMNIS: 

Delphi: 

Java Swing: 

Terminal: 

CEF/Electron: 

MS Webview2: 

PDF: 

Yes
Yes
Yes
Yes
Unmentioned
No
No
No
Yes
Yes
No
Yes
No
No

Drag Generation of Actions:

Yes

Reusable Steps:

Yes

Scripting:

Manual scripting and limited visual scripting

Parallel Execution:

No

Integrated Defect Tracking:

Partial

Test Localization:

Partial

Test Portability:

No

Manual Testing:

No

Test Management:

No

Test Execution Mgmt:

No

Integrated Version Control:

Partial

Integrated Test Management:

Partial, uses underlying Excel of AceOleDB

AscentialTest

Integrated Test Planning:

Yes

Object Recognition:

Advanced

Object Repository:

Yes, AscentialTest collapses object hierarchy. Objects inherit path from parents which makes maintaining object locators much more robust

Test Frameworks (Productivity):

No framework needed. AscentialTest builds automatically as tests created

Foreign Language UX:

Yes

Supported Platforms:

Web Apps: 

Windows MFC: 

.Net Winforms: 

.Net WPF: 

PowerBuilder: 

PowerServer: 

PowerClient: 

OMNIS: 

Delphi: 

Java Swing: 

Terminal: 

CEF/Electron: 

MS Webview2: 

PDF: 

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes

Drag Generation of Actions:

Yes

Reusable Steps:

Yes

Scripting:

Visual and manual scripting

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

Yes

Manual Testing:

Yes

Test Management:

Yes

Test Execution Mgmt:

Yes

Integrated Version Control:

Yes

Integrated Test Management:

Yes, built-in with full data typing

TestComplete

Integrated Test Planning:

Yes

Object Recognition:

Test Complete comes closest to AscentialTest in object recognition. Without the snapshot, it takes more time to test and maintain object definitions

Object Repository:

Similar to Selenium. No object hierarchy. Each object is identified from top to bottom. Alias permits shorter names but it doesn’t resolve issue of object hierarchy changing in future.

Test Frameworks (Productivity):

Does not appear to have appstates, some framework creation appears to be needed

Foreign Language UX:

Unmentioned

Supported Platforms:

Web Apps: 

Windows MFC: 

.Net Winforms: 

.Net WPF: 

PowerBuilder: 

PowerServer: 

PowerClient: 

OMNIS: 

Delphi: 

Java Swing: 

Terminal: 

CEF/Electron: 

MS Webview2: 

PDF: 

Yes
Yes
Yes
Yes
Yes (no test API)
Yes (no test API)
Yes (no test API)
No
Yes
Yes
No
Yes
No
Unmentioned

Drag Generation of Actions:

via Recording

Reusable Steps:

Yes

Scripting:

Assisted scripting with autocomplete

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

Unmentioned

Manual Testing:

No

Test Management:

Yes

Test Execution Mgmt:

Yes

Integrated Version Control:

Yes

Integrated Test Management:

Some, Parameters and Variables are stored at project level, Data is accessed from spreadsheets, external files and databases. They do not have built-in datatables, the mapping to data sources for data driven tests is really tedious and time consuming

AscentialTest

Integrated Test Planning:

Yes

Object Recognition:

Advanced

Object Repository:

Yes, AscentialTest collapses object hierarchy. Objects inherit path from parents which makes maintaining object locators much more robust

Test Frameworks (Productivity):

No framework needed. AscentialTest builds automatically as tests created

Foreign Language UX:

Yes

Supported Platforms:

Web Apps: 

Windows MFC: 

.Net Winforms: 

.Net WPF: 

PowerBuilder: 

PowerServer: 

PowerClient: 

OMNIS: 

Delphi: 

Java Swing: 

Terminal: 

CEF/Electron: 

MS Webview2: 

PDF: 

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes

Drag Generation of Actions:

Yes

Reusable Steps:

Yes

Scripting:

Visual and manual scripting

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

Yes

Manual Testing:

Yes

Test Management:

Yes

Test Execution Mgmt:

Yes

Integrated Version Control:

Yes

Integrated Test Management:

Yes, built-in with full data typing

Eggplant

Integrated Test Planning:

No

Object Recognition:

Object recognition is based on images and OCR

Object Repository:

There is no concept of an object repository

Test Frameworks (Productivity):

For simple tests, it appears to be a quick and easy process

Foreign Language UX:

Unmentioned

Supported Platforms:

Web Apps: 

Windows MFC: 

.Net Winforms: 

.Net WPF: 

PowerBuilder: 

PowerServer: 

PowerClient: 

OMNIS: 

Delphi: 

Java Swing: 

Terminal: 

CEF/Electron: 

MS Webview2: 

PDF: 

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No

Drag Generation of Actions:

via Recording

Reusable Steps:

Yes

Scripting:

Yes, assisted scripting with autocomplete

Parallel Execution:

No

Integrated Defect Tracking:

Possibly

Test Localization:

Possibly

Test Portability:

No

Manual Testing:

No

Test Management:

Additional product required

Test Execution Mgmt:

Additional product required

Integrated Version Control:

No

Integrated Test Management:

None

AscentialTest

Integrated Test Planning:

Yes

Object Recognition:

Advanced

Object Repository:

Yes, AscentialTest collapses object hierarchy. Objects inherit path from parents which makes maintaining object locators much more robust

Test Frameworks (Productivity):

No framework needed. AscentialTest builds automatically as tests created

Foreign Language UX:

Yes

Supported Platforms:

Web Apps: 

Windows MFC: 

.Net Winforms: 

.Net WPF: 

PowerBuilder: 

PowerServer: 

PowerClient: 

OMNIS: 

Delphi: 

Java Swing: 

Terminal: 

CEF/Electron: 

MS Webview2: 

PDF: 

Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes

Drag Generation of Actions:

Yes

Reusable Steps:

Yes

Scripting:

Visual and manual scripting

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

Yes

Manual Testing:

Yes

Test Management:

Yes

Test Execution Mgmt:

Yes

Integrated Version Control:

Yes

Integrated Test Management:

Yes, built-in with full data typing

Tosca

Integrated Test Planning:

No

Object Recognition:

Each element has full path, fragile over time and time consuming to generate, poor recognition of complex objects like treeview, table or grid

Object Repository:

Their solution is most similar to Selenium. There is no object hierarchy. Each object is identified from top to bottom.

Test Frameworks (Productivity):

Lots of dialogs and user steps to get work done. Not efficient

Foreign Language UX:

Unmentioned

Supported Platforms:

Web Apps: 

Windows MFC: 

.Net Winforms: 

.Net WPF: 

PowerBuilder: 

PowerServer: 

PowerClient: 

OMNIS: 

Delphi: 

Java Swing: 

Terminal: 

CEF/Electron: 

MS Webview2: 

PDF: 

Yes
Yes
Unmentioned
Unmentioned
Yes (out of date)
No
No
No
Unmentioned
Unmentioned
Claimed
Unmentioned
No
No

Drag Generation of Actions:

via Dropdowns

Reusable Steps:

Yes

Scripting:

Not described

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

No

Manual Testing:

No

Test Management:

Additional product required

Test Execution Mgmt:

No

Integrated Version Control:

No

Integrated Test Management:

Yes

AscentialTest

Integrated Test Planning:

Yes

Object Recognition:

Advanced

Object Repository:

Yes, AscentialTest collapses object hierarchy. Objects inherit path from parents which makes maintaining object locators much more robust

Test Frameworks (Productivity):

No framework needed. AscentialTest builds automatically as tests created

Foreign Language UX:

Yes

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Yes
.Net WPF: Yes
PowerBuilder: Yes
PowerServer: Yes
PowerClient: Yes
OMNIS: Yes
Delphi: Yes
Java Swing: Yes
Terminal: Yes
CEF/Electron: Yes
MS Webview 2: Yes
PDF: Yes

Drag Generation of Actions:

Yes

Reusable Steps:

Yes

Scripting:

Visual and manual scripting

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

Yes

Manual Testing:

Yes

Test Management:

Yes

Test Execution Mgmt:

Yes

Integrated Version Control:

Yes

Integrated Test Management:

Yes, built-in with full data typing

Eggplant

Integrated Test Planning:

No

Object Recognition:

Object recognition is based on images and OCR

Object Repository:

There is no concept of an object repository

Test Frameworks (Productivity):

For simple tests, it appears to be a quick and easy process

Foreign Language UX:

Unmentioned

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Yes
.Net WPF: Yes
PowerBuilder: Yes
PowerServer: Yes
PowerClient: Yes
OMNIS: Yes
Delphi: Yes
Java Swing: Yes
Terminal: Yes
CEF/Electron: Yes
MS Webview 2: Yes
PDF: No

Drag Generation of Actions:

via Recording

Reusable Steps:

Yes

Scripting:

Yes, assisted scripting with autocomplete

Parallel Execution:

No

Integrated Defect Tracking:

Possibly

Test Localization:

Possibly

Test Portability:

No

Manual Testing:

No

Test Management:

Additional product required

Test Execution Mgmt:

Additional product required

Integrated Version Control:

No

Integrated Test Management:

None

TestComplete

Integrated Test Planning:

Yes

Object Recognition:

Test Complete comes closest to AscentialTest in object recognition. Without the snapshot, it takes more time to test and maintain object definitions

Object Repository:

Similar to Selenium. No object hierarchy. Each object is identified from top to bottom. Alias permits shorter names but it doesn’t resolve issue of object hierarchy changing in future.

Test Frameworks (Productivity):

Does not appear to have appstates, some framework creation appears to be needed

Foreign Language UX:

Unmentioned

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Yes
.Net WPF: Yes
PowerBuilder: Yes (no test API)
PowerServer: Yes (no test API)
PowerClient: Yes (no test API)
OMNIS: No
Delphi: Yes
Java Swing: Yes
Terminal: No
CEF/Electron: Yes
MS Webview 2: No
PDF: Unmentioned

Drag Generation of Actions:

via Recording

Reusable Steps:

Yes

Scripting:

Assisted scripting with autocomplete

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

Unmentioned

Manual Testing:

No

Test Management:

Yes

Test Execution Mgmt:

Yes

Integrated Version Control:

Yes

Integrated Test Management:

Some, Parameters and Variables are stored at project level, Data is accessed from spreadsheets, external files and databases. They do not have built-in datatables, the mapping to data sources for data driven tests is really tedious and time consuming

Tosca

Integrated Test Planning:

No

Object Recognition:

Each element has full path, fragile over time and time consuming to generate, poor recognition of complex objects like treeview, table or grid

Object Repository:

Their solution is most similar to Selenium. There is no object hierarchy. Each object is identified from top to bottom.

Test Frameworks (Productivity):

Lots of dialogs and user steps to get work done. Not efficient

Foreign Language UX:

Unmentioned

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Unmentioned
.Net WPF: Unmentioned
PowerBuilder: Yes (out of date)
PowerServer: No
PowerClient: No
OMNIS: No
Delphi: Unmentioned
Java Swing: Unmentioned
Terminal: Claimed
CEF/Electron: Unmentioned
MS Webview 2: No
PDF: No

Drag Generation of Actions:

via Dropdowns

Reusable Steps:

Yes

Scripting:

Not described

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

No

Manual Testing:

No

Test Management:

Additional product required

Test Execution Mgmt:

No

Integrated Version Control:

No

Integrated Test Management:

Yes

Ranorex Studio

Integrated Test Planning:

No

Object Recognition:

Each element has full path, fragile over time and time consuming to generate, poor recognition of complex objects like treeview, table or grid

Object Repository:

Yes, but there is not object hierarchy so if the depth of the hierarchy changes, many object paths might need to be updated

Test Frameworks (Productivity):

Framework takes a long time to build

Foreign Language UX:

Unmentioned

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Yes
.Net WPF: Yes
PowerBuilder: Unmentioned
PowerServer: No
PowerClient: No
OMNIS: No
Delphi: Yes
Java Swing: Yes
Terminal: No
CEF/Electron: Yes
MS Webview 2: No
PDF: No

Drag Generation of Actions:

Yes

Reusable Steps:

Yes

Scripting:

Manual scripting and limited visual scripting

Parallel Execution:

No

Integrated Defect Tracking:

Partial

Test Localization:

Partial

Test Portability:

No

Manual Testing:

No

Test Management:

No

Test Execution Mgmt:

No

Integrated Version Control:

Partial

Integrated Test Management:

Partial, uses underlying Excel of AceOleDB

AscentialTest

Integrated Test Planning:

Yes

Object Recognition:

Advanced

Object Repository:

Yes, AscentialTest collapses object hierarchy. Objects inherit path from parents which makes maintaining object locators much more robust

Test Frameworks (Productivity):

No framework needed. AscentialTest builds automatically as tests created

Foreign Language UX:

Yes

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Yes
.Net WPF: Yes
PowerBuilder: Yes
PowerServer: Yes
PowerClient: Yes
OMNIS: Yes
Delphi: Yes
Java Swing: Yes
Terminal: Yes
CEF/Electron: Yes
MS Webview 2: Yes
PDF: Yes

Drag Generation of Actions:

Yes

Reusable Steps:

Yes

Scripting:

Visual and manual scripting

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

Yes

Manual Testing:

Yes

Test Management:

Yes

Test Execution Mgmt:

Yes

Integrated Version Control:

Yes

Integrated Test Management:

Yes, built-in with full data typing

Ranorex Studio

Integrated Test Planning:

No

Object Recognition:

Each element has full path, fragile over time and time consuming to generate, poor recognition of complex objects like treeview, table or grid

Object Repository:

Yes, but there is not object hierarchy so if the depth of the hierarchy changes, many object paths might need to be updated

Test Frameworks (Productivity):

Framework takes a long time to build

Foreign Language UX:

Unmentioned

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Yes
.Net WPF: Yes
PowerBuilder: Unmentioned
PowerServer: No
PowerClient: No
OMNIS: No
Delphi: Yes
Java Swing: Yes
Terminal: No
CEF/Electron: Yes
MS Webview 2: No
PDF: No

Drag Generation of Actions:

Yes

Reusable Steps:

Yes

Scripting:

Manual scripting and limited visual scripting

Parallel Execution:

No

Integrated Defect Tracking:

Partial

Test Localization:

Partial

Test Portability:

No

Manual Testing:

No

Test Management:

No

Test Execution Mgmt:

No

Integrated Version Control:

Partial

Integrated Test Management:

Partial, uses underlying Excel of AceOleDB

AscentialTest

Integrated Test Planning:

Yes

Object Recognition:

Advanced

Object Repository:

Yes, AscentialTest collapses object hierarchy. Objects inherit path from parents which makes maintaining object locators much more robust

Test Frameworks (Productivity):

No framework needed. AscentialTest builds automatically as tests created

Foreign Language UX:

Yes

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Yes
.Net WPF: Yes
PowerBuilder: Yes
PowerServer: Yes
PowerClient: Yes
OMNIS: Yes
Delphi: Yes
Java Swing: Yes
Terminal: Yes
CEF/Electron: Yes
MS Webview 2: Yes
PDF: Yes

Drag Generation of Actions:

Yes

Reusable Steps:

Yes

Scripting:

Visual and manual scripting

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

Yes

Manual Testing:

Yes

Test Management:

Yes

Test Execution Mgmt:

Yes

Integrated Version Control:

Yes

Integrated Test Management:

Yes, built-in with full data typing

TestComplete

Integrated Test Planning:

Yes

Object Recognition:

Test Complete comes closest to AscentialTest in object recognition. Without the snapshot, it takes more time to test and maintain object definitions

Object Repository:

Similar to Selenium. No object hierarchy. Each object is identified from top to bottom. Alias permits shorter names but it doesn’t resolve issue of object hierarchy changing in future.

Test Frameworks (Productivity):

Does not appear to have appstates, some framework creation appears to be needed

Foreign Language UX:

Unmentioned

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Yes
.Net WPF: Yes
PowerBuilder: Yes (no test API)
PowerServer: Yes (no test API)
PowerClient: Yes (no test API)
OMNIS: No
Delphi: Yes
Java Swing: Yes
Terminal: No
CEF/Electron: Yes
MS Webview 2: No
PDF: Unmentioned

Drag Generation of Actions:

via Recording

Reusable Steps:

Yes

Scripting:

Assisted scripting with autocomplete

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

Unmentioned

Manual Testing:

No

Test Management:

Yes

Test Execution Mgmt:

Yes

Integrated Version Control:

Yes

Integrated Test Management:

Some, Parameters and Variables are stored at project level, Data is accessed from spreadsheets, external files and databases. They do not have built-in datatables, the mapping to data sources for data driven tests is really tedious and time consuming

AscentialTest

Integrated Test Planning:

Yes

Object Recognition:

Advanced

Object Repository:

Yes, AscentialTest collapses object hierarchy. Objects inherit path from parents which makes maintaining object locators much more robust

Test Frameworks (Productivity):

No framework needed. AscentialTest builds automatically as tests created

Foreign Language UX:

Yes

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Yes
.Net WPF: Yes
PowerBuilder: Yes
PowerServer: Yes
PowerClient: Yes
OMNIS: Yes
Delphi: Yes
Java Swing: Yes
Terminal: Yes
CEF/Electron: Yes
MS Webview 2: Yes
PDF: Yes

Drag Generation of Actions:

Yes

Reusable Steps:

Yes

Scripting:

Visual and manual scripting

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

Yes

Manual Testing:

Yes

Test Management:

Yes

Test Execution Mgmt:

Yes

Integrated Version Control:

Yes

Integrated Test Management:

Yes, built-in with full data typing

Eggplant

Integrated Test Planning:

No

Object Recognition:

Object recognition is based on images and OCR

Object Repository:

There is no concept of an object repository

Test Frameworks (Productivity):

For simple tests, it appears to be a quick and easy process

Foreign Language UX:

Unmentioned

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Yes
.Net WPF: Yes
PowerBuilder: Yes
PowerServer: Yes
PowerClient: Yes
OMNIS: Yes
Delphi: Yes
Java Swing: Yes
Terminal: Yes
CEF/Electron: Yes
MS Webview 2: Yes
PDF: No

Drag Generation of Actions:

via Recording

Reusable Steps:

Yes

Scripting:

Yes, assisted scripting with autocomplete

Parallel Execution:

No

Integrated Defect Tracking:

Possibly

Test Localization:

Possibly

Test Portability:

No

Manual Testing:

No

Test Management:

Additional product required

Test Execution Mgmt:

Additional product required

Integrated Version Control:

No

Integrated Test Management:

None

AscentialTest

Integrated Test Planning:

Yes

Object Recognition:

Advanced

Object Repository:

Yes, AscentialTest collapses object hierarchy. Objects inherit path from parents which makes maintaining object locators much more robust

Test Frameworks (Productivity):

No framework needed. AscentialTest builds automatically as tests created

Foreign Language UX:

Yes

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Yes
.Net WPF: Yes
PowerBuilder: Yes
PowerServer: Yes
PowerClient: Yes
OMNIS: Yes
Delphi: Yes
Java Swing: Yes
Terminal: Yes
CEF/Electron: Yes
MS Webview 2: Yes
PDF: Yes

Drag Generation of Actions:

Yes

Reusable Steps:

Yes

Scripting:

Visual and manual scripting

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

Yes

Manual Testing:

Yes

Test Management:

Yes

Test Execution Mgmt:

Yes

Integrated Version Control:

Yes

Integrated Test Management:

Yes, built-in with full data typing

Tosca

Integrated Test Planning:

No

Object Recognition:

Each element has full path, fragile over time and time consuming to generate, poor recognition of complex objects like treeview, table or grid

Object Repository:

Their solution is most similar to Selenium. There is no object hierarchy. Each object is identified from top to bottom.

Test Frameworks (Productivity):

Lots of dialogs and user steps to get work done. Not efficient

Foreign Language UX:

Unmentioned

Supported Platforms:

Webapps: Yes
Windows MFC: Yes
.Net Winforms: Unmentioned
.Net WPF: Unmentioned
PowerBuilder: Yes (out of date)
PowerServer: No
PowerClient: No
OMNIS: No
Delphi: Unmentioned
Java Swing: Unmentioned
Terminal: Claimed
CEF/Electron: Unmentioned
MS Webview 2: No
PDF: No

Drag Generation of Actions:

via Dropdowns

Reusable Steps:

Yes

Scripting:

Not described

Parallel Execution:

Yes

Integrated Defect Tracking:

Yes

Test Localization:

Yes

Test Portability:

No

Manual Testing:

No

Test Management:

Additional product required

Test Execution Mgmt:

No

Integrated Version Control:

No

Integrated Test Management:

Yes

Anonymous Feedback

Contact Support

Get Started For Free: 30 Day Trial

Thank you for submitting your inquiry!

We will get back to you ASAP.  We aim to respond to all inquiries within 24 hours.

Seraphinite AcceleratorOptimized by Seraphinite Accelerator
Turns on site high speed to be attractive for people and search engines.