I work in Product based company as a QA/Test Engineer. For ex:I have been assigned a new project/enhancement that would be delivered to the clients in the next production release. The Business Analyst publishes the "Functional specification(SRS)' of the new feature/modules. Next, i start writing Test cases/scenarios for that.
After that the DEV team releases the build and i start doing the "functional" testing. I encounter issues, report them, it gets fixed, i re-test them and this goes on until i say that all is OK. The product is finally released to a production server.
Now, if management asks me about Test coverage, Test Cases coverage, then what is the best answer. My team does not follow Agile. It still follows the old waterfall based approach. There are no sprints or user stories.
Now, i believe that "Test cases are not Testing" and industry is moving towards a performance culture. Now, skilled Exploratory Testing is more important than Test Cases metrics. Then why should number of Test cases written define Test coverage. I wrote 100 test cases, which covers all of the requirements in the SRS. Then the question is, that is my coverage 100%. Why is this kind of coverage measurement wrong and outdated?