We are slowly generating small automated test cases for some software we develop. We've only got a few dozen or so written so far and we expect that in the end, we will have a few hundred, maybe a few thousands.
My question is what are some of the best practices for linking a test case to the requirement it is testing. Right now all our specifications are Word documents.
A simple way is to put a comment in the test case itself saying that it covers section x.y.z of the specification document, and then a similar comment in the Word document itself saying that this requirement is covered by test cases 1, 2 and 3.
One challenge with that approach is that out requirements documents are also the same documents we give to our clients.
To help understand my situation, I work for a large company and only have control over a subset of the developers (who will also be writing the tests). We don't use Agile or any other formal development process. We already have software in production and are now adding more features and fixing bugs. A solution that requires buy-in from the whole company or all developers or all BA's isn't viable.