Scripts and visual tests are similar in that both assets automate manual user actions such as selecting menu items and entering data in a test application. The difference between these two assets is how the user actions are represented in the asset. A script uses a scripting language, Microsoft's Visual Basic running in the Microsoft .NET framework, whereas, a visual test uses steps generated by the point-and-click interface of the Visual Navigator.
With either asset you can create powerful and flexible automated tests that run independently of each other. The choice of asset is dependent on your needs and preferences. You can also use each asset in conjunction with the other. For example, you can create a script that performs a specialized task, and then insert a step in a visual test that plays back the script. In this way, you can leverage the power of the scripting language used in scripts to supplement your visual tests.
When scripts are played back from a visual test, they are the equivalent of a function that you can call whenever you need to perform a repetitive and specialized testing task. This approach is helpful in a team testing environment, where an experienced tester can create a library of scripts that perform common testing functions from which a novice developer can select from when creating a visual test.