Contributions
Tag Expression Test Items no longer visible in Azure DevOps
I have an Azure DevOps pipeline that I use to run a Test Item made of a Tag Expression to pick up on tests that have been marked with specific tags. Azure DevOps then processes all tests that match that tag expression. However, at some point in the last couple months, Azure DevOps no longer sees the Tag Expression as a valid Test Item to run. I think this is because Tag Expressions are no longer able to be set as a Test Case. Is that the issue that I'm running into? If so, is there a workaround for this? Thanks.Solved1.6KViews0likes3CommentsEnum of possible options for TestComplete Element not showing up in Autocomplete / Code Completion
I have a question, I have a small script used to select values for different controls on a webpage. Because these values are finite, they are a perfect candidate for an Enum, so as to reduce the possibility of someone having a typo in text, and also to properly reference values in case they need to change in the future. Please see what I have below: const assuranceLevel = Object.freeze({ LOW: {value: 1, name: ' Low '}, MODERATE: {value: 2, name: ' Moderate '}, HIGH: {value: 3, name: ' High '}, VERY_HIGH: {value: 4, name: ' Very High '} }); function locateButtonGroup (buttonGroupTitleString) { return page.FindChildByXPath("//h4[text()='" + buttonGroupTitleString + "']/parent::div"); } function selectLevel(buttonGroupElement, assuranceLevel) { buttonGroupElement.FindChildByXPath("./descendant::label[contains(text(), '" + assuranceLevel.name + "')]").Click(); } function testPage() { selectLevel(locateButtonGroup("Overall SAL"), assuranceLevel.VERY_HIGH); selectLevel(locateButtonGroup("Confidentiality"), assuranceLevel.MODERATE); selectLevel(locateButtonGroup("Integrity"), assuranceLevel.VERY_HIGH); selectLevel(locateButtonGroup("Availability"), assuranceLevel.MODERATE); } This works as expected, and I can use one of the "assuranceLevel" options to constrain my choices to valid inputs. However, when typing assuranceLevel, when I hit the ".", I would expect an autocomplete window to come up, allowing me to select one of the viable options. That does not happen, and I have to type out the option. This defeats the entire purpose of using the enum in the first place, as the possibilities for typos still exist. It's frustrating that VSCode and sublime text editor can do this just fine, but TestComplete can't. Is there any way to get TestComplete to display options from enums in autocomplete?Solved1.7KViews0likes7CommentsRe: Enum of possible options for TestComplete Element not showing up in Autocomplete / Code Completion
No, I'm not talking about having autocomplete happen on the application under test. I'm talking about autocomplete in TestComplete itself when writing the script using javascript.1.7KViews0likes3Comments