Scripts and libraries - How to deal both scripts and libs

Coding standards for Rational Robot

(Continued from previous question...)

Scripts and libraries - How to deal both scripts and libs

Although it is possible to chain scripts by using the “CallScript” command it is not recommended to use it (or even exhaust) too much unless successful script execution of the called script does not depend on the prior executed script or if the chain is not too long and if a script is preceded by an initiating script followed by a script that brings the AUT back into a defined state.

Functionality or a business-case that is used very often such as the login-operation should not be placed in a script but in a function library because scripts don’t allow for parameter passing, ie. a login-script is unable to be reused with different usernames and passwords.
All functions within libraries and/or scripts need explanatory headers where one describes the purpose of the function.

(Continued on next question...)

Other Interview Questions

• Rational Robot's Coding Standards
• Naming Convention - Local scope variables
• Naming Convention - Module-level variables ("member-vars")
• Naming Convention - Arrays
• Naming Convention - Globals
• Naming Convention - Constants
• Naming Convention - Functions
• Naming Convention - Scripts
• Naming Convention - Libraries
• Naming Convention - Verification points
• Functions - Introduction
• Functions - Parameters
• Functions - Indention
• Functions - Return value
• Functions - Error handling
• Functions - Size
• Scripts and libraries - Introduction
• Scripts and libraries - How to deal both scripts and libs
• Scripts and libraries - Size
• Documentation - Introduction
• Documentation - Functions
• Documentation - Scripts
• Documentation - Module level variables
• Documentation - Libraries