mbeecham
Occasional Contributor
Joined 13 years ago
User Profile
User Widgets
Contributions
Re: "Verification Failed... (user) is not logged in on the slave computer" - anyone seen this before?
After further experimentation, I have now found the answer: On one connection, the Verification was working fine... so working through the "Distributed Testing - Requirements" pages in the TestComplete Help, I compared all the settings between the working connection and the not-working connection. The Restrict each user to one session option on the Terminal Services Configuration was set to Yes on the working connection, but was set to No on the not-working connection. I changed it to Yes... and the verify then works! The "...is not logged in on the slave computer" error is not mentioned on the "Message - Verification Failed" help page so perhaps that could be tweaked to point towards checking the Restrict each user to one session detail? (Since I sorted it out, I have now also been able to run Jobs in a Distributed Test style... Everything is working well.)1KViews0likes0CommentsRe: Will a mix of Scripting Languages in a Project SUITE allow Distributed Testing to work?
Here's a reply I had via email from a SmartBear engineer, so I'll share it here for anyone else who's interested... “The info Robert Martin provided on the forum is correct - the master can call other slaves that are written in other languages. However, I'd suggest they standardize on one language for maintainability's sake. If they have one person who writes all their tests in JScript and the rest write in VBScript, for example, and then that JScript person leaves the company, it will be much harder for the other members of the team to modify/update those tests.” Thanks to the engineer, and also to Robert for his early reply!1.1KViews0likes0CommentsRe: Will a mix of Scripting Languages in a Project SUITE allow Distributed Testing to work?
Hi Robert We have not yet started on creating the projects and writing the scripts. The only reason why we might mix languages is due to user knowledge - I have experience with VBScript while a colleague has Java experience and so is more comfortable with JScript. There's no technical reason for it. I thought it best to ask now whether it's possible, before we get started, to avoid going down a path which might turn into a dead-end. Yes, it is the intention for the Master Project to simply be for control of executing the distributed tests. Thanks for your swift reply... I'm interested to hear what SmartBear themselves have to say about it.1.1KViews0likes0CommentsWill a mix of Scripting Languages in a Project SUITE allow Distributed Testing to work?
A Happy New Year to all. We run a distributed application where different parts of the system run on separate machines – one part runs on machine A, another part runs on machine B, etc. With further parts also involved, there are around 10 (ten) parts to the whole system. Before we buy floating licences and get too far into the scripting, here’s a scenario and questions: We’re aware that for a particular project, you select a script language and then the whole of that particular project remains using that language. However, we might choose for each part of our system to have a project of its own, with all the 10 projects then sat within a parent Project Suite. If we have some of the projects with scripts written in VBScript and other projects with scripts written in Jscript, would we be able to use them within a distributed running, with synchronization points, of the whole project suite? OR do we have to have all the projects using the same scripting language? (asking this now, before we get started!) Thanks.15KViews0likes4Comments"Verification Failed... (user) is not logged in on the slave computer" - anyone seen this before?
I am trying to setup Distributed Testing and so have added detail in the Hosts section of Network Suite. When I try to verify the connection, I get a message including “Verification failed… The user … is not logged in on the slave computer”. The details entered into Host are all correct. I have worked through the checks on the “Message – Verification Failed” section of the TestComplete Help. The same details will launch and allow use of a Remote Desktop connection between the Master machine and the Slave. If I alter the details (user/password) to something NOT correct, I get a different message so that confirms that the details used are correct. I have tried it with the same user logged in on the slave, and without any user logged in on the slave. I have Test Complete and Test Execute both installed on the Slave machine. If I start them up directly, they pick up their licencing from Licence Manager located on the Master machine; so that seems to prove the network connectivity is there. The Master is a physical machine running Windows Server 2003 (64 bit, SP2), while the Slave is a VM (VMWare) running Windows Server 2008 (32bit, SP2)12KViews0likes3Comments