habhoub
Occasional Contributor
Joined 8 years ago
User Profile
User Widgets
Contributions
Grid Controls issue - Please help
Hi, I have a windows application, having a data grid control, containing in her columns some icons (edit, delete) to be clicked. I'm not finding a method to click on this image icon in order to edit or delete the selected row. Any suggestion please? The Grid doesn't have the ClickCell method in the list of available methods. It has only Click.. I have attached to the message a screenshot of the grid I have; maybe this will help detecting its type... Thank you2KViews0likes6CommentsRe: Sharing Project Items
Hello I have a project suite with one project and i want to add another project in the same project suite but i noticed that the new project created doesn't include testedapps nor stores nor namemapping items! Do you have any idea what can be the reason?? Thank you1.7KViews0likes1CommentProblem in Name Mapping shared objects! Needs Help
Hello we are a team of 4 users, starting working on GitHub on a TestComplete project, we are facing an issue when merging our projects files in NameMapping objects, as on some machines the list of objects is not complete and so some controls are not found using the object name "Aliases.etc..." Do you have any suggestion for the solution? Question: Usually, the names gotten from the object Spy are exactly the real names of the controls in the code of the project right? If some objects are not added to the name mapping and a user wants to use a test calling these objects by their alias names, does this include an issue? (example: Aliases.NovoClinicalTrialsManager.FrmMain.TableLayoutPanel1.TableLayoutPanel2.HeadlessTabControl1.TabPage10.SponsorsList1.NavigableDataControl1.Body.SponsorDetails1.flwMain.ctlContacts.tblContacts.btnNew) and why? Thank you2.3KViews0likes7CommentsRe: what's the best solution for working as a team on a TestComplete project?
Thank you I read your post on the mentioned thread, You said the following: "I would recommend to set a process when all TestComplete project files except script unit ones are not changed concurrently. If any modification of any of these files is required, only one person must do it, commit changes to the repository and flag others that they can proceed. As for the script unit files, they can be merged with much lower risk, but only in a case when changes are small and merges done often. This also must be set as an enforced development process. Otherwise you will get into merging nightmare when it is near to impossible to merge fine and quickly because of massive concurrent changes required to be merged." The process you are talking about should be managed then by a locking system, like TFS. Let's say i added the project to TFS: if one user takes the responsibility of adding/deleting tests, and others checked out the tests just to edit them... Can it be controlled this way in your opinion? The problem that Stores and TestedApp parts of the project should be checked out by each user on each change! This is the thing i'm not arriving to understand. Thank you again for your help..2.9KViews0likes0CommentsRe: what's the best solution for working as a team on a TestComplete project?
Thank you I read your post on the mentioned thread, You said the following: "I would recommend to set a process when all TestComplete project files except script unit ones are not changed concurrently. If any modification of any of these files is required, only one person must do it, commit changes to the repository and flag others that they can proceed. As for the script unit files, they can be merged with much lower risk, but only in a case when changes are small and merges done often. This also must be set as an enforced development process. Otherwise you will get into merging nightmare when it is near to impossible to merge fine and quickly because of massive concurrent changes required to be merged." The process you are talking about should be managed then by a locking system, like TFS. Let's say i added the project to TFS: if one user takes the responsibility of adding/deleting tests, and others checked out the tests just to edit them... Can it be controlled this way in your opinion? The problem that Stores and TestedApp parts of the project should be checked out by each user on each change! This is the thing i'm not arriving to understand.. :smileyembarrassed: Thank you again for your help..2.9KViews0likes1Comment