every solution/tool is based on the usage of the TestRail API.
AS mentioned above there is a second reporter, which is using another paramter to get the test run passed. I’m not sure if there are other public solutions available for the integration with cypress.
But first you have to make your requirements clear. The discussed reporting will bring the results to TestRail, so your requirement is fulfilled, be happy.
But I guess, this won’t help you. Let’s assume you have a daily test execution of 100 tests. This might lead into 365x100 test runs having one test with one result in. Usually you get the request to post the automation results to TestRail for reporting reasons, try to report across these 36.500 runs.
Basic: You need to have a case for every automated test in TestRail.
Do you plan to structure them in different suites?
Where do you define which cases have to be executed (or at least needs to have a result in TestRail)? You need to have a test run with selected cases to add a result to. Who is in charge to create this run and the selection of the test cases (you can do so before execution or probably on the fly with a special logic).
How do you want to structure your test execution?
- Having a run per single test execution (like with the reporter).
- Having a run for the daily execution of your collection of tests. Created automatically or manual, as part of a testplan (indicating a structure like releases or versions) or not.
Do you plan to add more information to the results than the status? How do you plan to a solution to add additional information of e.g. custom fields…?
Not sure if there is a solution available for your needs beeding flexible enough, I bet it isn’t.
I wasn’t able to find a public available solution for my (well, our) needs to integrate the results from a JUnit&Selenium based test framework as part of a Jenkins pipe. So I implemented my own solution for it, using a Java implementation using the TestRail API.
[No, it’s not public.]