Answers are grounded in this paper and cite their sources.
Including test activity in the software’s lifecycle requires it to be planned, so that the time and resources to be spent can be estimated. However, estimating test effort is still an unexplored process. This work describes a method to get test activity effort, based on the information of software use cases. The method was applied in testing of systems from the Brazilian Federal Revenue Service and results showed that the estimates' error was attractive relative to other methods evaluated, with the advantage of including an important refinement that distinguishes normal scenarios of a use case from exceptional ones.
No takes yet. Share an insight, caveat, or question.
Almeida et al. (2009) studied this question.
Synapse has enriched one closely related paper. Consider it for comparative context: