# Determine Amount of Effort (time) Remaining

I think this relates to a quesion that Butch had in this discussion: https://community.smartbear.com/discussions/zephyrscale/how-to-view-estimated-time-effort-in-reports/262576

Is there a way to determine how much effort there is remaining for a test cycle/plan?

At the start of a cycle, you can look at estimated time, and know where you are at.

If you are executing the cycle there are reports to see *how many* cases are at each staus (pass/fail/not-execucted).

However, I would like to see how much time/effort is remaining based on the estimate.

example: There is a cycle with 100 test cases. The total estimate is 100 hours for simple math. However, half the cases take 1.5 hours, and the other half take .5 hours. The engineer responsible for estimating is not always accurate. The test cycle now has half the cases excecuted, and there are 50 hours used. Is it going to be complete early, late, or on-time? That would depend on which test cases had been executed. It also could be that all the 'quick' ones were done first, but were misestimated and it is going to be REALLY late, or all the long ones were done first and it is going to be done REALLY early.

alternate example: I have 4 test cycles with varying numbers of test cases in them. We have decided to SKIP (state that we use) 70% of the test cases in 2 of the cycles, as these tests were decided to be not required to validate the software on this hardware change. How can I recalculate the estimated time for these cycles? In this situation, there are 30 test cases that take a total of 6 hours, however one case takes 3 hours to run. Do we really need to look at 30 individual test cases and add them up manually (or not) to see how long this is going to take?