JLHedges
Junior Member
Reged: 07/03/01
Posts: 102
Loc: USA
|
|
I've got a TestPartner test that I'm executing remotely via QADirector. The test takes roughly 2 1/2 hours to execute, and it runs successfully when I log into the machine, open TP and execute. However, when I execute the same test via QADirector, it dies after about an hour's execution.
Is something timing out? Is this test too long for execution through QADirector? The test is driven by a (relatively) large active data set that I'd prefer not to break apart.
Any suggestions?
--------------------
TP 6.3
AUT: Web app - Java/SQL
Using TestPartner since 2008
Using QTP since 2002
|
DSquared
Moderator
Reged: 04/02/03
Posts: 4546
Loc: Wisconsin, USA
|
|
There is a time out in QAD that is set at about an hour. I had the same kind of issue.
I don't remember exactly where it is (job execution, maybe?), because it has been well over a year since I have actively run a job in QAD. I remember it was a parameter that was available when I set the job up.
Anyone - help? Where is the parameter? I don't have QAD loaded on my current machine, so I can't go looking.
If all else fails, call tech support. That is what I did and they solved the problem in about 2 minutes.
|
JLHedges
Junior Member
Reged: 07/03/01
Posts: 102
Loc: USA
|
|
Aah... found it.
In QAD, select Tools>>User Options>>Test Information. Hope this is the solution.
--------------------
TP 6.3
AUT: Web app - Java/SQL
Using TestPartner since 2008
Using QTP since 2002
|
maximusus
Newbie
Reged: 06/22/09
Posts: 7
Loc: Poland
|
|
It will be helpfull for you
It's from Micro Focus Knowledge Base
"INSERTVALUE" timeout value times out at 60 minutes
Problem:
The timeout value set on my Test Procedure is "<INSERTVALUE> ". However, the job always times out at 60 minutes.
Resolution:
The Override TimeOut value set in the Job Description window on the Advanced tab uses the Test Procedure Timeout value set in Tools menu -->User options on the Test Information tab. If you want to increase the timeout value for a particular job, you'll need to manually increase the Override TimeOut value in the Job Description window. If you want to increase the timeout value for all jobs, you'll need to manually increase the Test Procedure Timeout value in Tools menu -->User options on the Test Information tab.
but there is a bug in QAD 6.1 that
Parameter 'Override timeout' couldn't be set permanently.
It has to be set per run
(Run ~ Advanced ~ Options {Override timeout})
The default value is 60 minutes.
I always set it to 9999 min.
Test timout: 9999 min
Override timeout (job): 9999 min
In the previous version 5.3 of the QAD we could change it in User options to 9999 once for all.
|
dwarlick
Member
Reged: 01/16/08
Posts: 131
Loc: North Carolina
|
|
When you are creating a job (Clicking Run), click the Advanced link (left side) of the Job Description window. In the Override timeout: box you can enter the max number of minutes you want the job to run before being forced to exit. This is in vrs 6.1, but I believe it is in the same place in earlier vrs. don
--------------------
don, CSTP, QAD/TP user since 06
Test Partner 6.3; QAD 6.1; QADLoad 5.9
|
Previous
Index
Next
Threaded
Edit
Reply
Quote
