Imported tests not recognized as such by Testomat

[XavierDeMontis]

Describe the bug While the test import command is apparently successfull Testomat fails to see any actual test.

To Reproduce

1. We regularly import our tests to Testomat thanks to the dedicated command
2. The imports are apparently successfull
3. But it looks like, in spite of each test having an id (automatically generated by the import command), the tests are not recognized by Testomat

As a consequence most of Testomat abilities are lost.

Expected behavior I expect my tests to be properly imported and recognized. nb : I've noticed that sometimes a few tests do not receive an automatically generated id. As an example I can give you this example of a feature file ` @Level0:Spaces @Level1:Spaces/Ressources_Management @S169e5472 Feature: Asset Management

@Level2:Spaces_Management @Level3:Disabling/Enabling_Space_Mgt Scenario Outline: Admin and Source Manager can enable/disable Manage Spaces feature Given I am logged in as And I group And I Manage Spaces feature And I save my changes When I group Then I see Manage Spaces feature is

Examples:
  | user          | manage | action  | state    | groupName         | edit |
  | admin         | create | enable  | enabled  | AmForSpacesGroup1 | edit |
  | sourceManager | edit   | disable | disabled | AmForSpacesGroup1 | edit |
  | admin         | edit   | enable  | enabled  | AmForSpacesGroup1 | edit |
  | sourceManager | create | disable | disabled | AmForSpacesGroup2 | edit |

@Level2:Spaces_Management @Level3:Built-In_groups_with_space_mgt @T302dc863 Scenario Outline: Admin and Source Manager built-in groups have Manage Spaces feature enabled by default Given I am logged in as And I go to /spaces Then I see that I am to manage spaces

Examples:
  | user          | access      |
  | admin         | allowed     |
  | sourceManager | allowed     |
  | codeceptRead  | not allowed | `

As you can see the first scenario outline has not received an id, while the second one did.

Screenshots If applicable, add screenshots or video to help explain your problem.

Desktop (please complete the following information):

• OS: irrelevant
• Browser [e.g. chrome, safari]
• Browser Version [e.g. 22]
• Application: [production or beta]

Additional context Add any other context about the problem here.

[olexandr13]

@XavierDeMontis please specify versions of:

• check-cucumber
• reporter
• cucumber version which you use for testrun

[XavierDeMontis]

Hi @olexandr13 If I believe my package-lock.json we're using cucumber version : "6.0.7" I confess I'm not quite sure regarding the others, could you please tell me how can I check that ?

[olexandr13]

@XavierDeMontis sorry for such long delay. The latest cucumber version is 10, but you use 6. And this version is already deprecated. We want to satisfy our users, but also want to focus on the most common/popular frameworks. Please upgrade your cucumber to one of the latest versions and report again if problem reproduced.

[TetianaKhomenko]

@XavierDeMontis was this issue solved for you?