Happy to answer a SeeTest Automation tool related question, have been working with the tool for almost 2 years now.
I agree with you on SeeTest Automation being a wonderful tool , but I would say a No-No to just doing record and code export.
Well the good thing here is you have just started the project and I believe you haven’t put efforts on creating test scripts (now if you have put in lots of efforts, am sorry you might want to put some rework into it).
Now, if you have seen SeeTest scripts there are many lines of code which are repetitive like creating a ‘Client’ variable instance, setting device, setting android version, setting device speed and many more. Now each of your script needn’t do all these start-up tasks, may be you separate it out and place in a class file and use it wherever required.
Code exports usually contains lots of locators with xpath, you might want to reduce that wherever possible. Xpath are known to cause performance issues and creates flaky test scripts.
Abstraction is an important concept while creating your test scripts; I feel you should use Page Object Model Pattern, may be separate out all app functions into a different class say a Function Library class, this way of creating multiple layers of classes and spreading data across them will reduce maintenance work which will kick in once your project plans a new release.
So, to conclude I would suggest you to use code export wisely, there are scenarios where recording is useful like:
- Locating few tricky elements.
- Simulating complex user actions on Mobile Apps like Swipe, Pinch or few others.
Use code export but do a code refactoring (as mentioned above) once you put in the IDE.
Hope this helps.