NativeVersionControlPlugins/Test
Daniel Hompanera 115a5253c3 Port triggers script to PowerShell so it can be run from Windows 2022-07-26 17:37:43 +02:00
..
Perforce Port triggers script to PowerShell so it can be run from Windows 2022-07-26 17:37:43 +02:00
Plugin run p4 VCS tests from specified directory 2016-06-10 14:19:44 +01:00
Source Add -test flag to recognize we are in testing mode inside PerforcePlugin 2022-07-21 18:58:15 +02:00
TestServer Add dependencies for API v19.1 2022-05-16 14:44:17 +02:00
Readme updated docs 2016-06-08 10:56:37 +01:00
VCSTest.pm Remove the rest of subversion mentions 2019-09-20 14:14:57 +03:00
run_tests.bat Starting compliance test framework. Mac only for now. 2013-06-25 14:51:08 +02:00
run_tests.sh Baseline handling 2013-07-05 09:59:47 +02:00

Readme

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>