Yes, either of your suggestions does give you the information, but not in a easily viewed/digestible format. How about a format where the result instance status is in columns, where each column is either
- By Day - with the latest result of that day shown
- By Result - with the tested on date in the status box
Something along the lines of: https://wiki.jenkins.io/display/JENKINS/Test+Results+Analyzer+Plugin
Alternatively, a new test plan for each execution could be built, but then the Test Runs & Results tab gets unruly quickly, polluted with many instances of test plans that represent one shot runs. Aggregating and filtering would be nice on this page nonetheless.
Maybe I don’t understand the recommended approach to using testrail for automation. Documentation seems to be lacking for that use. Sure, there is lots of documentation on pushing test results, but there is a lack of recommendations on whether those should be added results to a constantly open test plan or a wholly new test plan. If it should be a new test plan then integrating manual and exploratory results becomes problematic. Anything that separates test types into different test plans seems to drive a wedge into a wholistic picture of test status. Maybe there needs to be a notion of an integrated test plan that aggregates results. IDK, but whatever way we approach this, there seems to be glaring holes in the tool.