summaryrefslogtreecommitdiff
path: root/source4/script/tests/win/vm_get_ip.pl
AgeCommit message (Collapse)AuthorFilesLines
2007-10-10r21475: Updated vm_get_ip.pl to read the name of the environment variable ↵Brad Henry1-1/+1
containing the VM path from the command line. wintest_2k3_dc.sh is a new script which will run a group of tests against a Windows 2003 DC. The group of tests to run should be passed in on the command line. These tests were taken from the source/script/tests/test_win2k3.sh script. tests_win2k3_dc.sh is a new script intended to be called by 'make wintest_dc' (patch to source/main.mk forthcoming). This is intended to provide the basis for Windows 2003 DC testing in the build farm. In order to use these tests, you should have a DC setup as a VM in VMware server. This process is not automated yet, but can be done by following a few steps: 1. Prepare a Windows 2003 VM in VMware Server by downloading and extracting: svn://svn.samba.org/home/svn/samba/branches/SOC/bnh/vm_setup.tar.gz and following the instructions in the README file. 2. Copying the following file onto the filesystem of the VM configured in step 1: svn://svn.samba.org/home/svn/samba/branches/SOC/bnh/dcpromo_2k3dc_newdomain.answerfile.txt and use it to promote the VM. For example: "dcpromo /answer:<path to answerfile>" 3. On the system you are testing from, set the environment variable WINTESTCONF, and SRCDIR. WINTESTCONF should point to the path of a test_win.conf file modified for your environment. There's a default copy in source/script/tests/win/test_win.conf. SRCDIR should point to the base of your Samba 4 source tree. At that point, you should be able to run wintest_2k3_dc.sh by passing a group of tests at the command line. For example: source/script/tests/win/wintest_2k3_dc.sh RPC-DRSUAPI Sorry for the long-winded commit message! (This used to be commit a0d1c690de2e58eddf5517eb974e09c2bba23605)
2007-10-10r17768: This merges in the current version of Brad Henry's windows testingAndrew Tridgell1-0/+48
framework patch. There are some issues with the patch that I will discuss in a separate email to the list, but given the low (zero?) impact of the patch as it is, I think its better to integrate it now, then let Brad send some minor update patches later (This used to be commit 7232da0436ff1d84e419d268fee31a095bbb88b7)