This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Is there a limit on the length of a Cucumber feature for BDD injection in Octane?

Hi

We have one cucumber feature with 257 lines and 16 scenarios

When we try to add it in a octane pipeline to be injected as BDD content, it does not work, and in the builds tab, appears the next message: Test injection failed

We divide the .feature file in 2 feature files, and then it works correctly, and it was injected as BSP with the corresponding BSC.

Thanks

Xavier Yuste

 

  • 0  

    What version of Octane are you using?

    In order to see a detailed error message, go into the pipeline’s details view in Octane, press the Follow button and run the pipeline. 
    After the pipeline finish, check the notifications tab in the My Work module and share the detailed message 

  • 0 in reply to   

    Hi,

    About the version:

    Product version: 16.0.116.68
    edition: Enterprise
    buid time: Oct 13, 2021 3:05:52 AM
    Tenant id: 136698439

    About notifications, I am following the pipeline, but no new notifications are displayed in My Work section

    Thanks and Regards,

    Xavier Yuste

  • 0 in reply to   

    Hi Ehud,

    Product version: 16.0.116.68
    Edition: Enterprise
    Build time: Oct 13, 2021 3:05:52 AM
    Tenant id: 136698439

    I am following the pipeline, but about My Work module no new notifications are displayed.

    Thanks and Regards

    Xavier

  • 0   in reply to 

    Hi Xavier,

    Sounds like something R&D needs to examine. I suggest that you will submit a support ticket.

    Thanks,

    Ehud

  • 0 in reply to   

    Hi Ehud

    I have review the following "options" , and the flag "BDD content injection failure" was disable, I enabled it, and now, I have the information about the error:

    There is a duplicated scenario name and it causes the error trying to be injected the BDD content into Octane.

    The information in the "MY WORK" section is very good:

    "The specification contains duplicate scenario names: 'Access to the Staff Scheduling - Shift Assignments'. Make sure each scenario has a unique name."

    Really there is not length problems

    Many thanks 

    Xavier

  • 0   in reply to 

    Hi Xavier,

    Thanks for sharing the good news. I'm glad that you found the way to turn on the BDD notifications and that the message directed you to the root cause Blush

    Ehud

  • 0 in reply to   

    Hi Ehud and OpenText colleagues,

    I hope it's OK to revive this thread.

    We just had a related issue in our team. And through the Follow + Notifications feature we stumbled across here, we were finally able to find out the root cause (-> new Octane Idea ahead...).

    But with respect to this flow of information, I cannot believe those essential details are only available through "Following" upcoming Pipeline runs.

    Can you please share how to find the same data (especially the list of Errors regarding test result injection) for past Pipeline runs e.g. through the REST API? (Internal and Technical Preview APIs are gladly accepted, too!)

    We are on ALM Octane Enterprise v16.1.200.120.

    Klaus

  • 0   in reply to 

    Hi Klaus,

    Apologies for the late response.

    I feel that there is a mixup with this topic.

    The "Follow Pipeline" purpose is to surface issues or potential defects with the injection mechanism. You should use it only if you feel that something is wrong with the injection, and this tool can help you when you submit a ticket to Octane's Support. Otherwise, there is no need to follow the pipeline.

    Ehud