'How to estimate test execution using testlink

I have gone through many articles and all are suggested me to create custom fields/Keywords in testlink to estimate the time for sprint execution.

Articles like :-

http://www.softwaretestingconcepts.com/testlink-using-custom-fields-and-keywords-for-effective-testing

Is there any alternative approach or any scientific method to estimate your sprint execution accurately.

I have found one article proposing below method:-

Number of Test Cases = (Number of Function Points) × 1.2

Source :- http://www.tutorialspoint.com/estimation_techniques/estimation_techniques_testing.htm

What should be the approach to estimating your execution cycle? Currently, I am doing it as per my experience in my project. It is working fine but management wants a concrete mechanism for same. Please suggest and share your experience

I have added Time Estimate and Actual Time from below option:-

enter image description here

Below is the result of above setting

enter image description here

enter image description here

I am not able to get this field data in report. I need total estimate also and then comparison between actual and estimated time

Any help would be appreciated

testlink


Solution 1:[1]

TestLink provides inbuilt support to record Estimated Exec. time(define at TestCase creation) Estimated Exec. time define at TestCase creation and Actual Execution time. (record at TestCase Execution time) enter image description here

Based on this feature hopes you can buildup your requirement.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1 Asanka V

Related Questions