估计测试用例的数量

发布于 2024-11-26 10:44:31 字数 107 浏览 1 评论 0原文

我们的客户向我们提出了一系列该项目的要求。

他们首先希望我们估计系统测试用例的数量。

有什么技术可以做到这一点吗?

谢谢

问候, 詹姆斯

Our customer has given us a set of requirments for the project.

Up front they want us to estimate the number of system test cases.

Is there any technique for doing this?

Thanks

Regards,
James

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

卖梦商人 2024-12-03 10:44:31

我将从计算用例开始,并为用例或需求的每个组件编写一个测试。这是一个很好的开始数字,但是还有更多的变量,直到您实际开发系统时才会知道,并且还取决于系统的功能。

通常,您需要大量的单元测试来测试客户甚至不知道的代码。例如,如果它们需要身份验证,您可能需要一个单元测试来模拟对用户进行身份验证,但您可能还需要一个测试来测试用于加密密码的加密。

单元测试的数量主要取决于您想要完成的任务,并且很难预先预测。

如果您的客户预先提出这个问题,我会要求他们确定他们想要测试什么。程序员根据所提供的规范编写代码,这通常包括用例图和功能需求,他们/您可以从中导出测试用例。

希望这有帮助!

I would start with counting the use cases and write one test for each component of the use cases or requirements. That's a good number to start with, however there are so many more variables that will not be known until you actually develop the system and also depends on what the system does.

More often than not, you'll need a lot of unit tests to test your code that the customer will not even be aware of. For example, if they require authentication you might have a unit test to simulate authenticating the user, but you may also want a test to test the encryption you're using to encrypt the password.

The number of unit tests depends mainly on what you are trying to accomplish and is hard to predict up front.

I'd ask your customer to determine what they would like to test if they are asking this up front. Programmers write code given the specification they are provided, this usually includes use case diagrams and functional requirements from where they/you can derive the test cases.

Hope this helps!

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文