EmmaQuinn
New Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: Last Ran Date/Time
Hi mgroen2. I would like to see it on the 'View > Organise Tests > Test Items' screen. I only keep the last 10 log files and have a large number of tests that I run at different times depending on what is changing. the last column on this screen is called 'Description' which I am currently using to keep track of it, for example I input 'Last Ran 21/11/2016 - 2.5 hours'1.7KViews0likes0CommentsLast Ran Date/Time
It would be incredibly useful to have the last run date and start/end time, perhaps even duration shown for keyword tests. I currently use the description field on the organise tests>Test Items screen for this but have to remember to update it each time I run a batch of tests1.8KViews1like4CommentsVariables - Find Unused / show where used
I have created 100s of variables over the last couple of years and have no way of knowing if they are now redundant / where I am using them It would be useful to be able to see a list of variables that are not used in any tests and to see a list of tests that variables are used in.5.9KViews15likes3CommentsRe: Unable to launch a remote instance of TestComplete (TestExecute)
Hi, Thanks for your response. The only way I can find to set a timeout on the network suite is in the scheduled job. I have set it to /Timeout:300000 which has reduced the frequency but it still occurs. Is there somewhere else I can set it? Emma1.7KViews0likes1CommentUnable to launch a remote instance of TestComplete (TestExecute)
Hi, I have been running tests over virtual machines using TestExecute for a couple of years now and in the last couple of weeks have started getting failures with the message 'Unable to launch a remote instance of TestComplete (TextExecute)' followed by 'Unable to connect to the remote instance of TestComplete (TestExecute). I don't get any additional information and am struggling to work out what is causing this. The failures appear to occur randomly but happen on almost every run. For example if my run includes 4 jobs, it might fail on the first one, the third one, the last one. There doesn't appear to be any pattern to it. Last night I turned on the 'Collect Test Visualizer data during test run', hoping that I would get a screen shot that would give me a clue as to what is happening, but the failure didn't occur (this is the first time in weeks that is has not occurred). I suspect this may be a coincidence rather than the cause. Has anyone else had this issue / suggest anything I can do to try and find out what is causing it? Many Thanks Emma1.8KViews0likes3Comments