Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies replies
    8
  • Subscribers subscribers
    19
  • Views views
    1354
  • Users 0 members are here
  • Locked Locked
Related
Options
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?

Xavier Yuste Medina

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

 

Parents
  • 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 

    _________________________

    Ehud Michelson
    ValueEdge | ALM Octane R&D

    Although I am an OpenText employee, I speak for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

  • 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

    _________________________

    Ehud Michelson
    ValueEdge | ALM Octane R&D

    Although I am an OpenText employee, I speak for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

  • 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

Reply
  • 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

Children
  • 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

    _________________________

    Ehud Michelson
    ValueEdge | ALM Octane R&D

    Although I am an OpenText employee, I speak for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.