Contributions
Re: Diff viewer screen doesn't default "Before" pane to earliest revision?
Hi Charles, You can configure what revisions DiffViewer will compare in before and after panes via the Diff Viewer Default Version Comparison setting in user preferences. Most likely, your current setting is "Two most current versions" that is why it shows changes from 3 to 4. To see changes from 1 to 4 you'll need to select the "All changes" value for the setting2KViews1like1CommentRe: Code Collab - move reviews to approved state for other participants
Hello, >> Is there a way using command-line or JSON API tomark reviews and set assignment state to "Approved" for specific participants (not necessarily the account currently logged in)? Yes, command-line client allows to do so. To login with a specific account call the ccollab login command and then call theccollab admin review finish command. The later command finishes the current phase of the specified review and moves it to a subsequent phase. Once the target review is in Inspection phase and it has no defects, this command will approve the review. >>Also,for other reviewers participating in this review, we could add a note the uploaded version 'n' is only a merge/integrate operation and hence auto-approved. Command-line client allows this too. Use ccollab admin review comment create command. ccollab login https://collabserver.net servbot-user password ccollab admin review finish --until 'Any' reviewID ccollab admin review comment create reviewID "Auto-approved changes as they are merge/integrate operation"2.7KViews0likes0CommentsRe: Can defects be added while in the REWORK state? if so, does the review stay in the REWORK state?
Hi >>can a reviewer add a defect after a review has moved to the REWORK state? Yes. Reviewers can add defects in the Rework phase. >>does the review remain in the REWORK state until the Work Product Developer sends it back to INSPECTION? Yes. The review will be in Rework phase, until the author moves it to Inspection.1.6KViews1like0CommentsRe: Collaborator Client Version vs Server Version
Hello, stixbc Well those limitations are not technical, but relate to customer support policy (generally, our support team provide assistance for customers having the most latest major version or the previous major version of Collaborator). As for support for old client applications. 9.x clients will work with 11.x server without any issues. Moreover, 8.x and 7.x clients will also work. You can check theMinimum Client Build setting of Administrator Settings to find the number of the oldest stable client application. Old clients (upto build #7024) remain functional with newer servers. Obviously, they'll lack new features added to never clients, but still remain working.3.4KViews0likes0CommentsRe: From where can I install Code Collaborator plugin 8.3 for Visual Studio .
Hi, purvaj89 You can get it from the Collaborator Installers Archive. Just scroll to v8.3 build 8301 section in the list. Yet, I'd suggest that you try Collaborator 10 and its plug-in for Visual Studio. Since the plug-in was greatly improved since 8,3. See Visual Studio Extension Overview1.5KViews1like0CommentsRe: Collaborator Client Version vs Server Version
Hello. Collaborator server is backward compatible with a certain number of earlier versions of Collaborator clients. Namely, 10,1 server can work with 7.x clients. You can check theMinimum Client Build setting of Administrator Settings to find the number of the oldest stable client application.3.9KViews1like2CommentsRe: Continual Intergration
Yes, sure. You can run TestComplete tests as a part of automated builds. Here at SmartBear we test our nightly builds with TestExecute (a lightweight test runner for TestComplete tests). You can launch tests from the command-line. This will work with any CI system. Besides, integration with some popular systems is available out of the box, or via plug-ins: Jenkins Microsoft Build Engine Microsoft Team Foundation Build Service Bamboo1.2KViews1like1CommentRe: I want to continue a recording that I already converted to code
Hello If you use Keyword Tests, then you can just press the Append to Test button on the editor's toolbar and continue recording. See Appending Recordings to the Current Keyword Test. If you use scripts, then appending a test will be a little bit trickier. At first, you'll need to run your existing script routine - it will restore the exact state of your tested app to the point where you would want to continue recording. (That is, open the same windows, enter the same values to the textboxes, click the same buttons and so forth.) Then, you will need to start recording and perform the desired actions. Stop recording when, done. This will generate another (new) script routine. Finally you will need to open the script editor and combine the existing and the new routines into one routine. >>I cannot see that option The "Always start a new test" option has been removed since TestComplete 10.30.2.9KViews0likes1CommentRe: Region Checkpoint
Hi balathavamani, You may use theRegions.Compare method for this purpose: Sub Test 'The Regions object is available if your project contains the Stores | Regions collection. If Not Regions.Compare("C:\FolderA\image1.png", "C:\FolderB\image1.png") Then Log.Error "The compared images are not identical." End If End Sub1.2KViews1like1Comment