Naming Convention - Verification points

Coding standards for Rational Robot

(Continued from previous question...)

Naming Convention - Verification points

Description
In functional testing, you need to verify that the objects in the application-under-test look and work as designed from build to build. To accomplish this, you can establish verification points also known as checkpoints or the objects. Because verification points are not very flexible when it comes to changes in the AUT it is wise to prefer Robot's
SQAGetProperty...- commands to verify whether expected behavior is met or not.

Syntax
[vp]+[FEATURE]+ [FUNCTION]

Examples
· vpAURA_ImageUploaded
· vpAURA_CaseInserted

(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