Structure of Test Script
Hello, I want to know what is the best way to structure the automated test script.I am listing different approach to structure the test scripts For ex: if I have a test that contains Login, ...
Forum Discussion
There really is no "Best Way", as it depends on your needs and the application. That being said my approach that I have found works really well is very similar to " Create one Script for Login, Action1,Action2 and Logout. After than create one Keyword Test and call all this 4 script Once you do that,create a project item with the keyword test. "
I use a library of script units for Actions, Connections, Data, Utilities, Verifications, etc...
These are all shared by add existing item in all projects, then we use either KWTs or other scripts to call these with desired parameters, adding the KWT or script as a project test item.
Thanks for your reply.
"These are all shared by add existing item in all projects, then we use either KWTs or other scripts to call these with desired parameters, adding the KWT or script as a project test item"
Can you elaborate on this further?
I would like to know the folder structure for your framework and how are you handling the input of one action, which becomes the output of another.
Are you handling inside the excel sheet or using parameter of the test? if you are using the parameter of he test then let me know how exactly are you doing it.
How about managing your test results? Are you using the standard test results of TestComplete or customized one?
Sounds like you are starting from the very beginning. Lots of good information here:
https://smartbear.com/learn/software-testing/
We can give you our examples but none of us are testing exactly the same thing as anyone else so it is best if you come up with something for your product and try it. Just do a small sample layout in TestComplete and see if it makes sense. If not, you can always delete the project and start over.
