IBM RFT Interview Questions: Q. 81 to 90
Q. 81: What regular expressions are used in RFT?
We can replace a recognition property with a regular expression or a numeric range to allow for a pattern-based recognition.
The pattern allows for more flexibility in the object recognition. We can convert properties to regular expressions and numeric ranges from within the Verification Point Editor or the object map.
We can undo any regular expression or numeric range.
<<<<<< =================== >>>>>>
Q. 82: What is the purpose of Regular Expression Evaluator?
Regular Expression Evaluator is used to test a regular expression while editing an object property.
Regular Expression Evaluator has the following controls:
1) Pattern: This field contains the current value when we convert to a regular expression. This field is used to edit the expression.
2) Perform Case Sensitive Match: This check box controls case sensitivity. It is set to “on” by default, and matching is case-sensitive.
3) Match Against Value: This field contains the current value when we convert to a regular expression. The pattern we edit must match this expression because it reflects the property value in the application.
4) Result: When we click Evaluate, this field contains the result. If the patterns matches, we see MATCH in green letters. If the pattern does not match, we see NOT A MATCH in red letters. If we use an illegal character in the pattern, this field indicates an exception.
5) Matching String: If the pattern matches, we see the matching string. If we use an illegal character in the pattern, this field gives you the error. For example, “Missing close paren” indicates that you have an open parentheses but not a closing parentheses in the regular expression.
6) Evaluation Button: Edit the value in the Pattern field, and click this button to test it. Click OK to save the expression when satisfied with it.
7) Examples Button: Used for examples of regular expression syntax and use cases.
<<<<<< =================== >>>>>>
Q. 83: What is software configuration management?
Software configuration management (SCM) referrs to source control, change management, and version control.
SCM systems are commonly used in software development groups in which several developers are concurrently working on a common set of files.
If two developers change the same file, that file might be overwritten and critical code changes lost. Software configuration management systems are designed to avoid this inherent problem with sharing files in a multiuser environment.
All SCM systems creates a central repository to facilitate file sharing. Each file to be shared must be added to the central repository to create the first version of the file. After a file is part of the central repository, users can access and update it, creating new versions.
A checkout operation creates a local copy of the file in which you can make changes. When user gets satisfied with the work, he checks in the file to create a new version. The original file version always exists.
<<<<<< =================== >>>>>>
Q. 84: What is Merge feature of software configuration management system?
In a multiuser environment many users can check out the same file at the same time. Thus the special “Merge” feature of the software configuration management system becomes helpful.
“Merge” feature combines multiple changes to a single file.
The first user to check in the file creates the new version. The second user to check in the file must merge her changes into that version. If the SCM system can combine the changes, they are merged into a new version of the file. If the changes conflict or cannot be resolved by the software configuration management system, the conflicts must be resolved manually.
<<<<<< =================== >>>>>>
Q. 85: What are the benefits of software configuration management system?
Test automation is a software development effort. Every time a test script is created, whether through recording or coding, a file is generated which contains the code. This code becomes a valuable test asset when created, developed or edited.
A team environment presents the risk of losing functioning code or breaking test scripts by overwriting files. A software configuration management system offers a way to overcome this risk. Every time a file changes, a new version is created and the original file is preserved.
<<<<<< =================== >>>>>>
Q. 86: Which software configuration management tool is used by RFT?
RFT comes seamlessly integrated with ClearCase a source control management tool, for versioning of RFT’s test assets.
ClearCase integration is specialized for RFT, hence some of its operations cannot be performed outside RFT.
If someone tries to perform file operations on RFT files outside the RFT user interface, scripts can become out of sync with their related files and become corrupt or unusable.
<<<<<< =================== >>>>>>
Q. 87: How do we share a RFT project using ClearCase source control management tool?
While using ClearCase, we need to create the RFT project in a ClearCase snapshot or dynamic view to share a project.
We can add the project to ClearCase after we create a project, as long as we create the project in a ClearCase view. To share a project move the project to a ClearCase view and then add the project to source control.
<<<<<< =================== >>>>>>
Q. 88: How do we use RFT and ClearCase to manage test assets?
ClearCase allows us to share projects, scripts, script templates, test datapools, and object maps across the testing team. We can manage following type of changes in test assets stored in the RFT project and in software system development right from requirements to release.
1) Check out a test script in RFT. ClearCase checks out the script and all supporting RFT files if we check them out from RFT.
2) Edit a checked out copy of the script or any of the supporting files using RFT.
3) Check in a test script in RFT to create a new version of the script.
ClearCase stores the version permanently in the VOB and checks in all supporting RFT files.
<<<<<< =================== >>>>>>
Q. 89: What is an element related to the test project?
An element is an object in a VOB, a database that stores your project’s files.
An element can be a RFT script, a RFT project, an object map, a test datapool, or a Java file.
If we use ClearCase for source control of test assets in RFT, all elements shall get stored with version history and comments in ClearCase. we can view the element type, the element name, the date of the revisions, the first few characters of the comment, the user who made the change, and the nature of the change for a test script or other element in ClearCase.
<<<<<< =================== >>>>>>
Q. 90: What is the importance of having latest version of various elements in tests?
While using the snapshot view we must ensure to get the latest files from the VOB on a regular basis. Otherwise changes checked in by others can break the script.
Updating the files once a day may be adequate, depending on the needs of particular team.
ClearCase integrated with RFT, copies the latest version of elements from the VOB to the snapshot view.
Continue to Next Part : Q 91 to 100
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.