Verification points are used to compare the data or object properties verified dynamically or manually with the application.
Dynamic verification points
1. User can insert the verification point object under the "Verification Points."
2. Add the test object corresponding that object .
3. Add the following lines of code to verify the verification point dynamic.
Example : vpDynamic("DynamicVP_01", TestObjectHere()).performTest();
In IBM sources are mentioned below lines of code verify the dynamically. But when I ran this code, its displaying the error.
vpDynamic("DynamicVP_01").performTest();
Manual verification points
Note : I am not sure how manual verification points will work, when try for my application its displaying the error message .
Below information sources are copied from IBM site.
Manual verification points are useful when you create the data for the verification point yourself, and you want to compare the data. For example, the data could be the result of a calculation or could come from an external source, such as a spreadsheet, data pool, database, or custom calculation.
Using the vpManual method
vpManual
("Object_01", "Check something manually.").performTest();
// or
vpManual
("ManualVP_01", "Check something manually.",
"Check something manually.").performTest();
The first time that a manual verification point is executed, if the verification point object doesn't exist, the value passed in will become the baseline value (which you can then see and edit in Rational Functional Tester, just like any other verification point). Your log file will say: Created verification point baseline.
From that point forward, any subsequent call to vpManual for that verification point will compare the actual point with the point. As Listing 5 shows, you can also call vpManual by passing in both the baseline and the actual result. In this case, the verification point object in Rational Functional Tester is ignored.
Dynamic verification points
1. User can insert the verification point object under the "Verification Points."
2. Add the test object corresponding that object .
3. Add the following lines of code to verify the verification point dynamic.
Example : vpDynamic("DynamicVP_01", TestObjectHere()).performTest();
In IBM sources are mentioned below lines of code verify the dynamically. But when I ran this code, its displaying the error.
vpDynamic("DynamicVP_01").performTest();
Manual verification points
Note : I am not sure how manual verification points will work, when try for my application its displaying the error message .
Below information sources are copied from IBM site.
Manual verification points are useful when you create the data for the verification point yourself, and you want to compare the data. For example, the data could be the result of a calculation or could come from an external source, such as a spreadsheet, data pool, database, or custom calculation.
Using the vpManual method
vpManual
("Object_01", "Check something manually.").performTest();
// or
vpManual
("ManualVP_01", "Check something manually.",
"Check something manually.").performTest();
The first time that a manual verification point is executed, if the verification point object doesn't exist, the value passed in will become the baseline value (which you can then see and edit in Rational Functional Tester, just like any other verification point). Your log file will say: Created verification point baseline.
From that point forward, any subsequent call to vpManual for that verification point will compare the actual point with the point. As Listing 5 shows, you can also call vpManual by passing in both the baseline and the actual result. In this case, the verification point object in Rational Functional Tester is ignored.
1 comment:
Excellent blog on RFT. Looking for software courses?
Salesforce Training in Chennai
Big Data Training in Chennai
Android Training in Chennai
Selenium Training in Chennai
JAVA Training in Chennai
German Classes in chennai
web designing course in chennai
web designing course in Velachery
Post a Comment