software:testing
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
software:testing [2016/05/10 02:57] – superwizard | software:testing [2016/05/10 03:04] (current) – superwizard | ||
---|---|---|---|
Line 29: | Line 29: | ||
< | < | ||
AccUnit provides unit testing experience for the serious VBA developer. | AccUnit provides unit testing experience for the serious VBA developer. | ||
+ | </ | ||
+ | |||
+ | ====== SmartBear TestComplete 11 ====== | ||
+ | |||
+ | |||
+ | From: https:// | ||
+ | |||
+ | |||
+ | < | ||
+ | Before you start simulating user actions, you have to obtain access to the desired UI forms and | ||
+ | elements. If you explore a Microsoft Access database or project in the Object Browser (for | ||
+ | instance, the sample Northwind database shipped with Microsoft Access), you can see that by | ||
+ | default TestComplete can access application forms, but it does not have access to form elements. | ||
+ | You need a way to make the form elements visible to TestComplete in order to simulate actions | ||
+ | over them. | ||
+ | </ | ||
+ | |||
+ | |||
+ | ====== VBUnit3 ====== | ||
+ | |||
+ | From: http:// | ||
+ | |||
+ | < | ||
+ | Single User License EUR 99.00 | ||
</ | </ |
software/testing.1462849034.txt.gz · Last modified: 2016/05/10 02:57 by superwizard