Because if smart identification mechanism is enabled then QTP will itself try many permutation and combination to find Unique object ,and you will never know how QTP idendified object (i mean by applying which combinations ) . And only idendifying object does not solve your problem you need to know which object properties QTP used to identify particular object uniquely .
Thus by using Smart object idendification you are making your script dependent on qtp mechanism , which may not work on every machine thus making your script non-portable .This is the only reason why smart object mechanism is disabled by default . Correct me if i am wrong . Even i am new to QTP ..... just giving it a try Experienced person need to pitch in now .. :) Thanks, Chintan On Tue, Jan 19, 2010 at 11:22 PM, sorabh chadha <[email protected]> wrote: > Hi Group > Please provide your input that Why Smart Identification is not > considered as good practice in Recording? > > -- > You received this message because you are subscribed to the Google > "QTP - HP Quick Test Professional - Automated Software Testing" > group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<mercuryqtp%[email protected]> > For more options, visit this group at > http://groups.google.com/group/MercuryQTP?hl=en >
-- You received this message because you are subscribed to the Google "QTP - HP Quick Test Professional - Automated Software Testing" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/MercuryQTP?hl=en
