Forum Discussion
HKosova
14 years agoSmartBear Alumni (Retired)
The one of reasons I do not use object checkpoint is that we need to tracking all properties for all objects to ensure any change made by developer should based on requirements or change requirements.
Are you retrieving the expected values for the comparison from an externally maintained "requirements" file? If you are, your solution is probably the way to go. Otherwise, you could give object checkpoints a try.
Object may change from time to time and checkpoint may fail every time from regression testing perspective.
Object checkpoints are, in fact, automatically updatable. When your application changes to meet new requirements, you can run the test with the Update options enabled for the checkpoints, and TestComplete will update the checkpoint expected values from the application. This is a built-in way to keep up with changes in the tested app.
Just my 2 cents. Of course, TestComplete is just a tool, and how you leverage it is really up to you.
Related Content
- 12 years ago
Recent Discussions
Working with Visual Test
Solved2 days agoBypassing TC engine
Solved2 days ago