Forum Discussion

bduncan's avatar
bduncan
Contributor
15 years ago

Problems using VirtualBox

Hi,



I'm currently testing to see if I can move my TestComplete system to a virtual machine but I'm having problems running TestComplete in a virtual environment.  TestComplete is version 7.5x running in VirtualBox 3.2.10.  Host is 64bit Windows 7 Professional and Guest is Windows XP service pack 3 (same as my real test machine).



A script will run for 5 - 10 minutes then it will Blue Screen the Host system so no logs on the virtual are created and no Events show up in Event Viewer on the XP Guest.



Should there be any problem running TestComplete on a virtual machine?



Thanks,

William
  • AlexKaras's avatar
    AlexKaras
    Champion Level 3
    Hi William,



    TestComplete runs without problems on MS VPC, Hyper-V and VMWare virtual machines. So this might be some incompatibility between TC and VirtualBox.

    What if you try to use another version of VirtualBox?
  • That's one consideration that we had made.  It seems to be a problem primarily in scripts that access printer drivers.  When we "print" in scripts we print to screen so we can capture an image and do comparisons.  When I run one of the few scripts that I have that don't access print functions there doesn't seem to be a problem.



    I'm going to look at MS VPC first and see if we have any luck with that.



    Thanks for the response and I will post my findings so you will know whether it is an issue with VirtualBox





    Thanks

    William
  • AlexKaras's avatar
    AlexKaras
    Champion Level 3
    Hi William,



    Your approach with 'printing' to screen sounds interesting as it might be an option to verify printouts in the .pdf format and the like. Problems with verification of .pdf files were discussed here quite often but the general solution so far was to convert original document into text format (losing formatting and the most of layout) and then compare just a textual part.

    Are you using some system drivers (never heard about them) that print directly to (some window on the) desktop or some third-party software like SnagIt that installs its own printer driver that can be used to print to the SnagIt application?



    Anyway, I agree that your assumption about the root of the problems most probably is the right one.