Contributions
BDD - Enhance step definition generation
For Cucumber steps, TestComplete doesn't generate step definition with Keyword And. It only generates steps with Given, When, & Then Keywords. This causes code duplicity. Module 1: Scenario: Check and Open app Given I have app installed on my machine And I install DB on SQL Server for "IM" And I should open app with "IM" database as "default" user Module2: Scenario: Prerequisite for app Given I have app installed on my machine And I install DB on SQL Server for "CF" Then I install Application Server on my machine "CF" with "WorkflowFeature" And I should open app with "CF" database as "default" user In the above 2 steps are the same And I should open app with "IM" database as "default" user And I should open app with "CF" database as "default" user and should have only one step definition. But TestComplete generates 2 steps definitions, one with Given And other with Then. Cucumber, in general, doesn't take keywords in consideration while doing the step matching but in TestComplete it does. This is causing the problem and creating a lot of duplicate code. We are looking for solution where TestComplete uses Cucumbers basic feature and do not consider Keywords while doing step matching and generates step definitions with all the keywords.We are looking for solution where TestComplete uses Cucumbers basic feature and do not consider Keywords while doing step matching and generates step definitions with all the keywords.1.9KViews4likes3CommentsBDD - Color coding for pending scenario steps
There is no color coding displayed for pending step definitions in scenario file. It is not clear by looking on the scenarios that which step has step definition and which step doesn't. It will be helpful if pending steps can be displayed in different color.572Views0likes0CommentsRe: Is Test Complete+Cucumber+Maven+Jenkins integration possible?
Yes, Its possible to do the integration.Create a maven project in jenkins and configure Build section: Root POM = pom.xml location Goals and options = cucumber execution command (example:-e clean test -Dcucumber.options="--tags @$tag")1.3KViews1like0CommentsRe: Test Complete12.50 doesn't recognize windows objects Windows10
Thanks for your reply Alex! I don't think this is a user related issue. I did run TestComplete routine without Cucumber integration and result was same. I have already submitted it to support team and still waiting for any concrete solution.2.3KViews0likes0CommentsRe: Test Complete12.50 doesn't recognize windows objects Windows10
Thanks for your reply Alex It's happening all the time and doen't look like issue with user account. Project has integration with Cuucmber (I use IntelliJ for integration) and if I run the script manully via Intellij then also this happens. It looks like if TestComplete engine is not started manually and triggered via IntelliJ , Jenkins or command line this issue occurs. I did run a test to check if the issue is with Cucumber integration but it is not. Running the same test via command line which invokes only TestComplete code also gives the same result.2.3KViews0likes2CommentsTest Complete12.50 doesn't recognize windows objects Windows10
While running a test via jenkins TestComplete reads random generated Object name as below Sys.Process("DBInstall").Window("WindowsForms10.Window.8.app.0.141b42a_r40_ad1", "Eze PMA - TradarBE Setup", 1).Window("WindowsForms10.Window.8.app.0.141b42a_r40_ad1", "", 2).Window("WindowsForms10.BUTTON.app.0.141b42a_r40_ad1", "&Next >", 2).Name But if I open TestComplete manually, it works fine and reads the same objects as below: Sys.Process("DBInstall").WinFormsObject("TradarDatabaseInstallWizard").WinFormsObject("buttonPanel").WinFormsObject("nextButton") This is happening on Windows10 while works fine on Windows7 Has anyone encountered similar issue? What could be the reason and solution?2.3KViews0likes4Comments