I’m evaluating Testrail as possible replacement to currently used TCMS.
I see the strange thing in Database: Testrail populates “tests” table with all test-cases existing in suite when I create run in specific suite. Even the run consists of only one test-case.
This may not be visible if suite consist of hundreds test-cases. But if several suites consist of dozen thousand test-cases and project contains hundreds run from these suites, “test” table grows extremely fast.
Small calculation allows to estimate that each run require adding one row “runs” table (~1000 bytes) and one row for each test-case existing in the suite (~66 bytes per row). In case if test-suite in project consists of 1000 test-cases, every run is costs ~67 kB. This calculation doesn’t include space required for indexes and row allocation in DB pages.
This looks like “wasting” DB space with data which never will be used.
Dividing suites to smaller suites may help to reduce “wasting” space. But it will also increase complexity of supporting, planning and managing projects.
This issue may partially be fixed by adding Hierarchical Test Suites support to Testrail. This functionality was requested several times previously. But it is not still implemented.