Contributions
Use aqString.format to generate a number with the thousands separator
It can't possibly be this hard, but I can't for the life of me figure out how to do it! What I want: aqString.Format("???", 1) = 1 aqString.Format("???", 100) = 100 aqString.Format("???", 100000) = 100,000 aqString.Format("???", 10000000) = 10,000,000 What does "???" need to be? No examples in Smartbear documentation for creating this format.Solved3KViews0likes2CommentsTestComplete Does Not See Child Objects in DWM window
I'm trying to create test scripts for an application written in Delphi. Running on a VM using Windows 7 Ultimate. The app opens a DWM dialog window which the Object Browser can see, but it can't see the text items or the Cancel button inside the dialog window. See the attached screenshot (SC1) for the properties as indicated by the object browser. Screenshot SC2 shows an example of the dialog window itself. It doesn't look at all exotic to me. Any help would be GREATLY appreciated. Dave2.3KViews0likes2CommentsRe: The "Visible" property of the "Stub object" object does not meet the checkpoint's condition.
It drives me crazy that I can't add a "Visible" property check to my scripts that won't fail if the object doesn't happen to exist in a given scenario. Its even more exasperating if I'm trying to verify that the object isn't supposed to exist! Consider: Property Checkpoint(objX, "Visible", cmpEqual, true) // Checkpointshould return success if the object isvisible, failure if it is not In practice, it works fine if the object is visible, but returns a runtime error if it is not (because the object is not visible. DUH!). Property Checkpoint(objX, "Visible", cmpEqual, false) // Checkpointshould return success if the object is NOT visible, failure if it is In this case, the checkpoint ALWAYS logs a failure. If its not visible, a runtime error is logged (again, because its not visible). If it is visible, it logs an error because the object isn't supposed to be visible, which is actually correct. This has always been a problem with "Visible" andsimilar properties in every automation system I'm familiar with. Upon my first exposure to TestComplete, I had hoped that the issue would have been addressed in a logical manner. Alas, that is not the case. A special case needs to be added to the code for property checkpoints where "Visible" and similar properties are concerned, specifically: if (property_checked = "Visible", "VisibleOnScreen", etc) { if (expectedValue = false) { if (!object.Exists) { log success; return true; } else { // process normally } } else { // expectedValue = true if (!object.Exists) { log failure; return false; } else { // process normally } } } Bottom line is that there is no good reason whatsoever why executing a property check against the Visible property should ever generate a run-time error. EVER!2.4KViews0likes0CommentsRe: Can I copy and paste name mapping items?
I've always beenconfused by this also. What purpose does the Copy command serve in the NameMapping tool as it is currently designed? There are times when you know all the identification parameters you need to map a given object, but it just isn't available right now; or you need to map several similar objects that only differ in an identification string. It would be much easier and faster to Copy/Paste/Edit an existing object than it would be to map each object individually. Consider this a feature request to add this functionality to NameMapping, its an operation that is long overdue. Dave1.1KViews1like0Comments- 12 years agoPlace QAComplete QuestionsQAComplete Questions560Views0likes0Comments
Cross-project Reporting: How to Do It?
In the manuals for ALM Complete, there is at least one reference to specifying cross-project reporting, but I haven't been able to find anything that explains how to do it? Has anyone ever set this up? Here is my situation. My company has several different software product lines. We want to keep them as separate projects within ALM Complete. Every month when Microsoft releases software updates (patch tuesday), we have to verify that our software products are not adversely affected by Microsoft's updates. The specific requirements and test procedures are different for each of our product lines, so we want to keep those requirements and tests properly associated with their "local" products. But the Windows update tests occur every month, so it makes sense to define that as a distinct project. We want to use this project as a central point for testing and reporting. That is, we want the Windows Patch project to link to the requirements and tests within each of the specific software projects and the results of those monthly tests, but the Windows Patch project has very few, if any, requirements and tests of its own. Any suggestions? Thanks, Dave12 years agoPlace QAComplete QuestionsQAComplete Questions5KViews0likes1Comment