Way to get coverage information?

Discuss test processes, standards, documentation, teams, criteria, test environments, etc.

Moderators: Amaradana, TurboPT, TL Developers

Post Reply
jptest
Advanced user
Posts: 26
Joined: Fri Feb 04, 2011 8:51 pm

Way to get coverage information?

Post by jptest »

I am new to Testlink so please bear with me if i am asking the obvious.
I have looked through the user's guide but no answer there.

Say I have a Test Project with 15 test suites. Each of these test suites have 30-50 test cases.

When I create a test plan for a particular release, I pick and choose test cases I want to run as regression (from existing 1000 cases) and then add new cases based on the new features in the release.

What I want to know is, is there a way to report %coverage I am regressing each test suite.
20% of Test Suite 1
37% of Test Suite 2 etc.
Amaradana
Member of TestLink Community
Posts: 398
Joined: Mon Feb 16, 2009 11:19 am
Contact:

Re: Way to get coverage information?

Post by Amaradana »

TestLink is test managment tool, it does not tell how much percentage of test you covered. Well you can get the percentage based/failed etc. or the execution percentage of build etc.
Thanks,
TesterWorld
Http://amartester.blogspot.com
jptest
Advanced user
Posts: 26
Joined: Fri Feb 04, 2011 8:51 pm

Re: Way to get coverage information?

Post by jptest »

Thanks Appreciate the response.

Interesting that test coverage is not considered as part of test management.
Amaradana
Member of TestLink Community
Posts: 398
Joined: Mon Feb 16, 2009 11:19 am
Contact:

Re: Way to get coverage information?

Post by Amaradana »

ow thats strange i did not see any tool that would cover the test coverage. Can you please point me to some test case management tool that covers test coverage for test cases, or elaborate what you mean test coverage means and what you are expecting?

Well i will write down that come to my mind that can help you may be!

First test Plan is intended for executing your set or for a release, may be an official version of a release of your application. To me not all builds consider as official release. There would be builds in a release that can be 'n' number defined as per your process.

Second When you assign some test cases to test plan and create builds for execution and reports generate accordingly and the test cases that were not assigned will be ignored for test execution.

Thrid, there is a report test case not assigned in test plan which lists all test cases that were not assigned.

I think you can log an issue as future request for development and let development discuss it.

Hope this information helps you.
Thanks,
TesterWorld
Http://amartester.blogspot.com
Post Reply