Contributions
Re: Unable to access (Verify/Execute) a VM for parallel testing
Unfortunately not so. The Banner is displaed as soon as any machine on our network boots up. You first get to accept the policies mentioned on the Banner by pressing that OK button. Once that is pressed, you get the Credentials screen.506Views0likes1CommentRe: Unable to access (Verify/Execute) a VM for parallel testing
We cannot remove the policy pushed by Global Server Ops team or Network Security team. Its strictly against the policies. There has to be some other way out as data is extremely critical and no security breach is tolerated.2.7KViews0likes0CommentsRe: Unable to access (Verify/Execute) a VM for parallel testing
Alex, Thanks for all your time on this. 1. The issue is, our organization has very strict policies regarding servers and client data. The security team has approved only a 24 hours slot for the removal of this'Warning Banner' so that we can verify the postulate, that this is the only hurdle which is keeping TestComplete from performing the job. So, it might not be possble for us to carry out parallel executions on VM. 2. What i had on mind was: a. Create multiple VMs on cloud. b. Setup 'TestExecute' on each VM. c. Whenever required, fetch the latest code from repo on the VM machine. d. Start the VM and perform auto-logon whenever a test execution is needed. e. Shutdown the VM when job is done and logs are uploaded. But this Security Warning Banner will block it. Am afraid that we will have to look for other options :( Thanks again for all your time and help. Ill update you in case any progress is made. Best regards2.7KViews1like3CommentsRe: Unable to access (Verify/Execute) a VM for parallel testing
Hey Alex, Sorry for the late reply. I have filed an RFC. The security team will consider removing the Welcome Banner for a day (24 hours max). But, the company policy wont let us remove that banner for ever. If this fixes the issue (and now i am sure its the pain point) we still wont be able to use this in long terms. Is there a way, TestComplete may develop a feature to solve such hurdles? Best regards, Obaid Shirwani2.8KViews0likes7CommentsUnable to access (Verify/Execute) a VM for parallel testing
Hi, I am facing a situation where am not able to decide, where the problem lies. Consider the following situation: 1. Happy Case: I am able to access a VM machine and execute test cases on it using TestCompelte successfully. This VM (created using Oracle Virtual Box) is hosted on a local server. 2. Issue Case: The GSO (Global Server Ops) team has provided me a VM and TestCompelte is not able to access this machine. I am attaching a screenshot. I have tried accessing this machine using both Local and Network user. I am manually able to Remote Desktop this machine using both users. Where is the issue? Regards, Obaid ShirwaniSolved3.3KViews0likes11CommentsRe: Previously working code w.r.t Sys.OleObject("Excel.Application") not working with 12.42
Shankar, I am not using any macros. The problem is beyond file enabled or disabled for editing. However as pointed out in message three in this thread above, i too doubt that this seems to be related to some version conflicts. I have provided details for all related software I am using. The issue at hand still stands that why is TestComplete trying to open the excel file during Code Development and why is it throwing the wrong message at code execution? The workbook is getting opened by code and object get returned successfully and file gets locked for manual manipulation, The error message 'book.Sheets is not a function' is wrong as I can see this property in the workbook object. I have the shot attached in above posts.2.1KViews0likes1CommentRe: Previously working code w.r.t Sys.OleObject("Excel.Application") not working with 12.42
Hy Shankar, I am unable to access 'book.Sheets' alone... it crashes here. How am i supposed to get past it? Please view the attached images in previous posts and read the text again under "//Issue 02 (Intellisense popup)". Thanks & regards, Shirwani2.1KViews0likes3CommentsRe: Previously working code w.r.t Sys.OleObject("Excel.Application") not working with 12.42
Hi Martin, I had obviously checked that before posting. The returned Workbooks object holds the number of Sheets available in the file. So i think that is not the issue. I am attaching the screenshot for the object returned. The visible class is throwing error. I assume it might be some version conflict or the driver issue. Best regards, Shirwani2.1KViews0likes5Comments