基于testrail的对于功能测试的一点思考 (二)(完结)

continue from 基于testrail的对于功能测试的一点思考 (一)

1. when I using the tool some time,
   I find a pretty feature:
   we can find a case running history, for example, when we test 1.0 APP, run “correct login” case.
   and when we test 2.0APP, beacuse it is regression testing , we need retest the “correct login” case. and we can find the hostory when we run 1.0 APP, so simple and useful.
   and when we run a same case on iOS and Android platforms, we can refer to another platform, and get the test result.
   the feature is useful, because if we find a common issue in APP 2.0, but we don’t find it in APP 1.0, I think we need to retest 1.0.
   of course, if we don’t use testrail, we still can track the 1.0, but we need to find the old excel and get the test result.
   when we use testrail , so simple.

The opposite, if we find a bug when we run case A, on APP 1.0. when we test 2.0, run the same case, we need be careful, because the module maybe has bugs.

for QA leader, “if we find a common issue in APP 2.0, but we don’t find it in APP 1.0, I think we need to retest 1.0.” is important.
2. as a test tool, generate testing report must have:

we can select generate summary and defects report.
summary:

so for leader, can get your point in report.

may be thinking of testrail is ending, I feel my style is prose, maybe I take blog as my thinking to my work. sometimes I even write my real-time thinking in blog, I can remove these content, but I think is real, wo I want to keep it. so sorry, need your understanding.