The most recent content from our members.
What Files should be Checked into Source Control? When using Source control with C/C++test, make sure to have the following files checked-in: * .parasoft * .cproject * .project * All source files that are needed for the project * Test Folders or other folder(s) you use for your Test Suites * Stubs Folders or other…
Hello , we are using bitbucket as a source repository to store Parasoft SOA test .tst scripts. Can Bitbucket integrated directly with Parasoft? Currently we use some commands to checkout/check-in the code to Bitbucket. Earlier , I used TFS - Team foundation server and Rational Clear Case tools, where I can directly…
Sharing projects and test assets through source control requires checking in a .parasoft file (if present) among others, but sometimes it contains local pathnames. For a number of technical reasons, when updating that .parasoft file, C++test will dump all (internally registered) properties (with their default values, which…
.Test and source control integrationHi, I need to integrate .Test in file check-in process , i.e to verify that the file are OK after check-out/check-in. The problem is that .Test works at .Test project level or at assembly level ( while nUnit works at file level, i.e nUnit test is written per single *.cs file) How i can…
It looks like you're new here. Sign in or register to get started.