Add feature to create Bug/Issue in Azure DevOps from TestComplete
I had check the TestComplete documentation and could not find any feature to Create Bug/Issue in Azure DevOps from TestComplete logs directly. So can you implement this feature in TestComplete as it would be helpful to automate the process of posting bug on failure. As currently I can see it is only possible to create issue in Jira, Bugzilla and QAComplete only.
More specific crash detection
Currently the crash detection posts an error to the test log on any crash of any application systemwide. Please make it configurable (project settings, or even better project suite settings) to post only errors of the applications configured in the TestedApps section (all others unnecessarily spoil the test log ;-) ).
How to get the data in the summary report into variable
I am working on creating a table with all the data available in the Junit summary report I want to check here to see if there is any Test complete inbuilt variables that has these values available. I am looking for execution data such as Run test cases, Passed test cases & Failed test cases. i am using below command to generate & export Test results summary in Junit format Log.SaveResultsAs("C:\\Work\\Log\\Log.xml", lsJUnit) sample Junit report -> <testsuites name="CommonAutomationFramework" tests="2" failures="2" errors="0" time="17" > <testsuite name="CommonAutomationFramework-UI" tests="2" failures="2" errors="0" hostname="xxxxxxxx" time="17" timestamp="2024-08-15T09:34:22.088-07:00">
Failed step is not specified
Hi, When I have a keyword test (A) in which another keyword test (B) is executed multiple times and keyword test A fails because keyword test B failed, then it is not possible to see which instance of keyword test B failed. Example: Keyword test A (check values in employee file) Step 1: Open employee file Step 2: Press button 1 Step 3: run keyword test B "Check all values" Step 4: Press button 2 Step 5: run keyword test B "Check all values" Step 6: Press button 3 Step 7: run keyword test B "Check all values" Step 8: Close employee file If the run of Keyword test A fails, because in step 5 keyword test B failed the keyword test log of keyword test B shows that the failed step is in keyword test B, but not in which instance (step 3, 5 or 7). It would be better if steps 1, 2, 3 and 4 where indicated as succeeded and step 5 as failed. Am I overlooking something?
Warning messages in the test run log for improve performance
Hello, Recently I have updated all my nameMapping to use unique identifiers in the XPath and deleted all others that TC saved when recorded. So tipically I have only one selector for each object or element. When I ran the test it gave me the following warning almost for all the objects. You can improve the performance of the object search in the test. The NameMapping.Sys.browser.pageAuth.login_SignIn_Btn object can be found faster if you make //input[@type="submit"] the first selector in its selector list. And in the nameMapping for this object I see only one selector as I mentioned above. Still not sure why its throwing warning messages. Even when I click on Improve performance button in the log it just added an Empty selector, and even with that when I rerun the test it gave same message. One another thing is that the Extended Find column doesn't have any checkboxes. Is there something I missed in the settings or somewhere else TIAMerging multiple tcLogX file into one tcLogX
I am running tests on GitLab separately with parallel matrix keywords. I want to merge test logs into one and keep them as a test run. Is there a way to merge tcLogX file into one? By this way, I can also share my results on Smartbear server with details and images. Otherwise, it is very difficult to keep track which log belongs to which test. I kindly ask for a new function on TestComplete which It can merge test logs.
