GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||||||||||||||||||||||||||||||||||
GeezerVison is showing github.com — NativeVersionControlPlugins/Test at master · Unity-Technologies/NativeVersionControlPlugins Expand file tree/ Copy pathTest/Directory actionsMore optionsMore optionsDirectory actionsMore optionsMore options/ Copy pathTest/Folders and files
Integration Tests ----------------- This will start a version control server, checkout a working copy and exercise the plugins using command files (e.g. Test/Perforce/04_Status.txt) A command file consists of a request section followed by a response section delimited by "--". Possibly followed by more request/response sections: As an example for getting the status of a file: c:status 1 ./testfile.txt 0 -- o1:-1 o1:./testfile.txt o1:42 d1:end of list r1:end of response -- Some macros are supported that can be put in the command files: <absroot> The absolute path to the workspace e.g. /Users/foobar/VersionControlPlugins/Test/tmp/testclient <ignore> Placed at the start of a line to ignore it when matching responses <include [path]> Include another command file at this point. e.g. <include ./Test/Perforce/02_Configure.txt> | |||||||||||||||||||||||||||||||||||||||||||||||||||
| You are visitor 01402520 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. | |||||||||||||||||||||||||||||||||||||||||||||||||||