use this sample code ..

pass the string as parameter in Check_PDF method.
Parameter whichever string you want to
retrive/display/verification.
 
Check_Pdf("aaaa")

[-] Check_PDF(LIST OF STRING lspdfcheckpoint)
	[ ] WaitForControl(Gold_Orders.ViewOrderForm)
	[ ] // main window - Gold_orders
	[ ] // OrderForm - Pdf form 
	[ ] Gold_Orders.ViewOrderForm.Click()
	[ ] 
	[-] if (OrderForm.Exists())
		[ ] WaitForControl(OrderForm)
		[ ] 
		[ ] STRING Items
		[ ]
		[ ] Clipboard.SetText({""})
		[ ] OrderForm.TypeKeys("<Ctrl-a><Ctrl-Insert>")
		[ ] LIST OF STRING OrderForm_Order = Clipboard.GetText()
		[ ] STRING Line
		[ ] BOOLEAN Found = FALSE
		[-] for each Line in OrderForm_Order
			[-] for each Items in lspdfcheckpoint
				[ ] 
				[-] if MatchStr("*" +Items + "*", Line)
					[ ] Found = TRUE 
					[-] if (Found)
						[ ] Print ("PASS:" +Items + "Item found on the OrderForm")
						[ ] Print("String Verification : "+Items)
					[-] else
						[ ] LogError ("FAIL:" +Items + "Item not found on the
OrderForm")
					[ ] //Close SRF
	[ ] OrderForm.TypeKeys("<Alt-F4>")

GetCaption.- Returns the text associated with the object.
-> To Retrive content/Text from an object.

STRING sImgText 

	sImgText = Object.GetCaption ()
        Print("Image Text:" + sImgText)

Silk Test Has In-built OCR lib (.inc), which is a 3rd party integrated, using these function we can get the text from bmp files.

If <Condition>
statement
else
statement

with the following systax ,you can get the total number of 
rows in the table.
WindowName.TableName.getRowCount() 
It returns the integer(Row Count)value

I think, you should use additional application (Adobe 
Reader 7.0 )and than from this application you can take 
information about pdf file

Use this method to parse - notepad and Pdf.

[-] Check_PDF(LIST OF STRING lspdfcheckpoint)
	[ ] WaitForControl(Gold_Orders.ViewOrderForm)
	[ ] // main window - Gold_orders
	[ ] // ViewOrderForm - Pdf form 
	[ ] Gold_Orders.ViewOrderForm.Click()
	[ ] 
	[-] if (OrderForm.Exists())
		[ ] WaitForControl(OrderForm)
		[ ] 
		[ ] STRING Items
		[ ] 
		[ ] Clipboard.SetText({""})
		[ ] OrderForm.TypeKeys("<Ctrl-a><Ctrl-Insert>")
		[ ] LIST OF STRING OrderForm_Order = Clipboard.GetText()
		[ ] STRING Line
		[ ] BOOLEAN Found = FALSE
		[-] for each Line in OrderForm_Order
			[-] for each Items in lspdfcheckpoint
				[ ] 
				[-] if MatchStr("*" +Items + "*", Line)
					[ ] Found = TRUE 
					[-] if (Found)
						[ ] Print ("PASS:" +Items + "Item found on the OrderForm")
					[-] else
						[ ] LogError ("FAIL:" +Items + "Item not found on the
OrderForm")
					[ ] // 31. Close SRF
	[ ] OrderForm.TypeKeys("<Alt-F4>")

Winrunner has default GUI objects like Windows, 
PushButton , Check box etc., these objects are called as 
standard objects. This objects can automatically learn by 
winrunner from our application.
 
Some applications use new objects other than winrunner 
standard objects. Those are called as custom objects. These 
should be mapped to the comparable standard GUI objects by 
using GUI map configuration to identify by winrunner.

To treat bitmap objects as push button(GUI object) , we 
have to define that bitmap as a virtual object by using 
virtual object wizard. Then this bitmap is calles virtual 
push button. Like wise we can create virtual radio button , 
lists , tables etc.

This answer is correct for WR
This Question is For SilkTest.Please tell me the answer for
this question.

Most of the development environments has their built-in set 
of GUI controls, these are called as standard objects. For 
most of the standard controls of supported technologies 
SilkTest has mapped classes. While developing any 
application developer may create a new GUI control these 
controls are called as custom object. As it is a user 
created control SilkTest do not have a mapped class for it, 
therefore these type of controls will be identified as 
Custom window (Custom objects) by SilkTest.

Do you mean for manual testing..?? if so...this is the 
process.

1. Test analysis

2. Test plan.

3. Test case Design.

4. Test case execution on the build.

5. Test reporting.

6. Regression Testing.

7. Test closure.

Kumar.rnv@gmail.com
Broadridge

Manual Testing:_
Usecase document
Functional point document
Master test case document
Test data document
Defect profile document

QTP testing process:_
Recording
Editing
Running
Analysing the results
Bug reporting

Hi,
    PEER Review is nothing but interchanging the test cases 
with in the team to know whether all the test cases has 
covered the SRS document or not.

A peer review is conducted by project personnel, who is
responsible to validate his counterpart(like his code or
whatever work he has done). Generally Peer Reviews are come
under static testing (white box testing) technique.

Desk Checking, Round Robin Reviews, Walk-throughs and
Inspections are the examples of Peer Reviews.

Desk Checking: The author of the code, himself validates his
code. It is informal method and the output completely relies
on the author.

Round-Robin Reviews: An informal method, with 4-6 members
discuss and commenting on the author's code and make note of
 changes and modifications according.

Walk-Throughs: Which is similar to Round Robin, but with a
formal meeting. 

Inspections: Which is formal and group oriented function.
Each and every point of the review are monitored and
documented. The author intimates his agenda and distributes
the documents before the scheduled meeting time. All the
members of the review team should prepare for that meeting
and show their outputs. The author will collect all these
oupputs from the review and need to take actions on the code.

Formal Reviews are different from Peer Reviews.
Formal Reviews are conducted at each stage of the project
development life cycle means after requirements, analysis,
design etc... where most of the the project management
people will involve.

It is not quite true question.
Writting of scripts - it is complex process, which consist 
of many steps (e.g.): 
1) Capturing of application dialogs
2) Description this dialog (addition some functions, 
methods...)
and then you will be able to start writing of scripts...

Review report is a document prepared by the test lead in 
order to have a discussion with the team.

Hi This is Sujatha.
Here mainly for Java technologies we will use this
tool.Because this script is related to java script.If you
know java language u can easily understood this script.But
it's not mandatory to know Java.
If this answer is wrong plz let me know.

Hi All,
Its not that SilkTest is related to java script....SilkTest
is based on its own proprietery language called 4Test which
is based on OOPS concept...
We can do most of the things in both the tools...one
advantage in Silk is if u have distributed applications like
your lab setup trequire to test inj 3 to 4 machines
simultaneously than u can go for Silk as it has agent concept.

silk Test is based on 4test language which is independent of
any other language or script more over the object
orientation is quite same while some syntax declaration for
methods data types functions are different.
Please go through the 4test language ......

By Using Silk test we get the 95% of result is good.

Many other feature are there in SilkTest which allows
reliability and maximum test coverage. Also 4Test is free
development environment through which we can strengthen the
framework.

actually silktest follows object oriented method of
programming we can reuse the properties of the objects
defined eg. AnyWin class can be inherited we can use the
defined classed to add more functions of our own type to
create new objects with addtional functionality use of
functions, the recovery system of silk is far better then
QTP use of appstate
inbuild support for browser pop handling browser
authentication handling

Whenever you want to identify dynamic objects, use "Index" 
(e.g. #1), "Window Location" or "Prior text". You can use 
them together using "multitag" .Generally, those properties 
dont change in dynamic objects

You can use regular expression supported in 4test
for example for a window whose tag is 
"$WelcomeXYZ"

You can make it dynamic using regular expression
by replacing the tag by
"$Welcome???" or "$Welcome*"

You can use regular expression supported in 4test
for example for a window whose tag is 
"$WelcomeXYZ"

where XYZ keeps changing depending on user login or say 
environment due to which scripts fail.
You can make it dynamic using regular expression
by replacing the tag by
"$Welcome???" or "$Welcome*"