Having advocated the use of "build once, use many" we have a large test suite constructed using a multitude of reusable actions from various test silos. When it comes to maintenance, it's always a good idea to assess the impact of changes and therefore to know where those actions are used - e.g. some kind of matrix.
In BPT, Quality Center retains information on where a component is used and it is that type of idea I want to leverage wrt reusable actions.
Has anyone used a slick way of achieving this? ..Or some ideas...
I want to make it easy to enter and retrieve info, but torn between the simplicity of a spreadsheet (matrix) and a database (search efficiency).
To cover existing tests I intend to run a script over them to extract the 'external' action data. The dilema is where to put it.