Welcome to the new Parasoft forums! We hope you will enjoy the site and try out some of the new features, like sharing an idea you may have for one of our products or following a category.

source control

New DiscussionExpand for more options.

Discussion List

  • Guide and exercise for uploading the correct artifacts for Source Control

    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…

  • Can Bitbucket source repository integrated with Parasoft ?

    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…

  • Local pathnames in the .parasoft file.

    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 integration

    .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…

New DiscussionExpand for more options.

Popular Tags