It is ideal to have a solid amount of coverage done at a unit test level … compared to a webdriver/slow level. In the past, I have only been concerned about tracking webdriver tests in testrail because they follow a flow, making our manual test cases easy to automate.
Now we want to track unit tests and I’m wondering what other companies out there are doing (or what testrail guru’s recommend).
Basically we have no issues adding unit tests to testrail and adding results to them, the problem is the # of test cases that would add, we will potentially slow down testrail.
My overall goal is to be able to see a picture of our features and the manual, unit and webdriver test coverage. I want to be able to flip (or delete) manual tests when they have become automated (aka maintenance).
My gut tells me that we might just need to leave testrail as webdriver + manual, extract that data to kibana or another reporting tool, have our CI tool that reports on unit test results also export to that reporting tool, link them all by feature (maybe by component) and get a view that way. The one issue with this is that when i go to testrail, I need to understand there will be test gaps because unit tests will cover them… Perhaps I would just flag that test as ‘unit tested’, perhaps have a link to where in the code this is covered and leave it at that…
Anyway, anyone have any success stories/other ideas?