Hi Anish, Thanks for a logical input. You are correct in saying this. I agree with this and the approach should be (my opinion) something like..once someone asks question on the forum, he/she also should give an example of "what is already tried as a solution" for the asked problem. This will give insight on the approach, so that from that point any of us can leverage the problem's soluion to a closure level.
please advise Thanks On Sat, Dec 17, 2011 at 9:17 PM, Anish Pillai <[email protected]>wrote: > Hi, > > The point you mentioned is completely valid. But I feel that there is one > more thing we should not ignore. Its about what we are actually trying to > achieve here. Are we trying to serve ready to use answers to our friends > here or do we really want to learn things by trying/exploring different > things. Well documented, executed code is very good to create a reference > library sort of thing. But can we do something which not only provides the > solution but also leaves a bit of room for us to maybe fill in the gaps and > learn something in this process? What are your thoughts on this? > > Regards, > Anish Pillai > My QTP Blog <http://automationrepository.com/> > > > -- > 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 > -- 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
