Forum Discussion
Hi,
I think that the following approach might be helpful:
-- Plan some actions over tested application;
-- Record script (or keyword test);
-- Go through recorded code and try to understand it;
-- Try to replay generated code. Use https://support.smartbear.com/testcomplete/docs/testing-with/running/handling-errors/index.html and https://support.smartbear.com/testcomplete/docs/testing-with/running/messages/index.html help sections to resolve possible playback problems/instability;
-- Try to enhance or extend generated code (add logging, some parameterization, etc.);
-- Try to execute modified code.
Repeat the above process several times to get better understanding of how TestComplete works with tested application. Try to read for details about NameMapping and Aliases (https://support.smartbear.com/testcomplete/docs/testing-with/object-identification/name-mapping/index.html) and understand how this piece of functionality works.
Try to use the obtained knowledge to craft test code that you actually need for your real tested application. Actually, you may start with small basic steps: e.g. create test that will reliably start your tested application and another test that will reliably close it. Even with these two basic tests you may check that new build of your tested application can be started and closed as expected.
- Zels2 years agoNew Contributor
Figured it Out.
#@FirstScriptdef FirstTestScript():p = Sys.Process("Orders")w1 = p.WinFormsObject("MainForm")toolbar = w1.WinFormsObject("ToolBar")toolbar.ClickItem(1)Sys.Process("Orders").Window("#32770", "Open", 1).OpenFile("MyTable.tbl")#End of FirstScript
Related Content
- 4 years ago
- 5 years ago
- 5 years ago
- 4 years ago
Recent Discussions
- 13 hours ago
- 2 days ago