Thanks Tobias, but that didn't answer my question unfortunately.
I already read the reference doc for 'results' and was able to use the add_result_for_case / add_result_for_cases API as a manual call. So I was seeking if anyone has any experience in what the best practice will be to use it with the Cucumber BDD framework.
Our projects consist of mobile games, which I set up our framework using the Appium tool for automation. And, internal admin web UI tools that both our customer service and marketing staff use, which that is setup using the Ruby gem Capybara that works with Cucumber.
But the problem I'm stuck with is when the tests are completed and the results are saved in a JSON output file, by finding the best method to scan the data of the results. From there, determine what the status of the test outcome was and match each test scenario with their Test Case in Testrail. So I was thinking to make it easier, if it was possible to save the Test Case ID using the TAG feature that Cucumber BDD supports.
@516555 <-- example of tag
Scenario: Unable to login with a blank email and password
Given I load the domain url
When I submit with a blank email and password
Then I should see the invalid account error message
I found similar results searching on Github from repositories that use RSpec like so:
describe "some test" do
id "some spec", testrail: 1234 do # 1234 is the id of a test case
Last question, our Test Cases are saved using the current admin default settings. I notice there's an option to activate and create Test Suites to better organize the Test Cases. My question is if the API supports finding Test Cases within a Test Suite, or is it better to not use them and just organize Test Cases with only sub-categories?
And thanks for the assistance by the way.