Generate Step definition in Keyword test recorder
Hi, The feature to record directly into the step definition script and be guided by the recorder toolbar is great but is reserved to the testers that are comfortable with scripting. To be able to do the same in the Keyword test module would be very useful and open up the tool to a larger number of testers. I know you can link the script to the keyword tests but this defeats the purpose of having a sime and easy to maintain framework.
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.BDD - 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.BDD integration in TestComplete
I like the BDD principles and was investigating it's potential application combined with TestComplete. Read this, this, thisand this article on it. Personally I have come to the conclusion that BDD has definitely potential but the frameworks currently investigated (Lettuce, Cucumber) require way to much fragile configuration (settings project folders name, test names, etc, etc) to be able to use this effectively in Contiuous Delivery / Continuous Integration alike approaches. In practise you end up maintaining the configuration files, editing connection / integration scripts to keep 'alive' the integration between Cucumber/Lettuce and TestComplete. Therefore, I would go for a BDD framework within TestComplete (or another product from SmartBear) which can guaranty integrity of BDD features/specifications/test-steps on the one hand, and the actual tests/validations (wheter these are scripts or Keyword tests) on the other hand. I would like to see this implemented in either TestComplete itself (sort of like currently Manual Testing (and the conversion to automated tests) is supported (but this is going to be depreciated unfortunately but that's another subject), or in a seperate tool which would then be required to be very well integrated with TC (such as like sharing variables, parameters, etc). When supported in TestComplete itself it could be placed in "advanced node" in a project, for example. And this module would be able to read (import) .feature files like the GIVEN/WHEN/THEN , Gherkin language support. After importing the test/QA engineer would do his/her work to 'knot' the features and the tests together in the framework. By keeping this all in one tool would prevent ending up in constantly updating settings like updating configuration files, (re)define directories if projects are moved, etc. That's exactly what's NOT needed in CI/CD environments.
