I've automated once telnet communication using Python's telnetlib it is very
easy, it does require QTP.


On Tue, Jun 28, 2011 at 2:04 PM, Jimmie Parson <[email protected]> wrote:

> No just exploring the issue right now and looking for any workable
> solution. I went down this path a little in the past but due to what
> we were trying to test Putty was not working very well without lots of
> work. With QTP 11 add-in it records and I can get runs to almost work.
> If you have an example of how you used descriptive programing to solve
> your problem that would be great. If not I will start to look into
> that method as one of my next steps.
>
>
> Thanks,
>
>
> Jim
>
> On Jun 28, 1:29 pm, Ganesh muralidharan <[email protected]> wrote:
> > did you try with descriptive?
> >
> > I had faced a similar issue but at that time there were multiple reusable
> > actions which were using different addins and the driver was calling
> these
> > reusable actions.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Tue, Jun 28, 2011 at 1:18 PM, Jimmie Parson <[email protected]>
> wrote:
> > > To all,
> >
> > > I am using QTP 11 and PuTTY along with the TE add-in record some
> > > tests. The telnet server I am connecting to is not compatable to the
> > > hllapi standard. It is connecting with the VT100 protocol. I have set
> > > the QTP TE add-in to use the PRconfigured PuTTY settings. As I am
> > > recording text only I have the following 2 object types to work with:
> >
> > > TeWindow("TeWindow")
> > > TeTextScreen("TeTextScreen
> >
> > > The problem I am having is that I am able to record the tests but upon
> > > trying to run the tests after the initial appearence of the telnet
> > > screen QTP will not recognize the
> > > TeWindow("TeWindow").TeTextScreen("TeTextScreen" object as being in
> > > the OR. I have checked and it is there and nothing changes even if I
> > > add the object again. I have looked for any other people having this
> > > problem and only found one other instance that is similar to my
> > > problem but it is on another forum and had no answer given.
> >
> > > The issue only occurs in the first couple lines of the code if I stop
> > > the test and re-run in the debug from step mode the object is
> > > identified and the test seems to proceed normally.
> >
> > > Has anyone else had a similar issue or can anyone point me in the
> > > correct direction to find the help I need.
> >
> > > Thanks,
> >
> > > Jim
> >
> > > --
> > > 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
> >
> > --
> > Regards,
> >
> > Ganesh Muralidharan
> > 'God Never Forgets'
>
> --
> 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

Reply via email to