blocks|key|1143639|text|只有3天时间来测试你的应用程序！我们有可能运行15天的测试作业。我猜其他潜伏在这里的人可能会告诉你，他们有更大的测试工作；你知道程序--当我还是个孩子的时候，我们甚至没有生活的道路上的一个洞。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1143640|但说真的，用3天的时间完全测试一个收益流为O(USD10%5E7)的候选版本对我来说并不离谱。另一方面，如果您花了3天时间来测试将GUI上的一个字段从12个字符更改为24个字符，那么这似乎有点太多了。我认为你的问题可能更好地表达为“我们应该将多少开发时间花在测试上？”答案可能是10%25+-+50%25+(对于安全关键型系统可能更高)。如果你花了2天的时间开发一个补丁，那么测试应该不会超过1/2天。|1143641|是的，随着您的应用程序的扩展，您的测试套件也会扩展，这种情况非常熟悉。然而，如果我们添加了一些新的功能，我们往往会添加新的测试；更好的方法是修改现有的测试，这是一种我们永远没有时间的方法，尽管我们总是有时间处理不使用它的问题。修改代码->修改测试；添加新代码->添加新测试。|1143642|是的，我们尽可能多地使用自动化测试；我们使用bash脚本、python程序和make来驱动我们的自动化测试。我们使用的处理器从不抱怨测试乏味和重复，所以我们没有道德上的顾虑，让那些濒临热死的可怜的家伙工作。可悲的是，当地的劳工法阻止了同样强大的管理原则被应用于我们办公室的碳基生命形式。|1143643|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Only 3 days to test your application ! We've got test jobs that run for maybe 15 days. And I guess other lurkers around here can tell you that they have even bigger test jobs; you know the drill -- when I were a lad we didn't even have a hole in't' road to live in.

But seriously, 3 days to fully test a release candidate with a benefit stream worth O(USD10^7) doesn't seem outrageous to me. On the other hand, if it's taking you 3 days to test changing one field on a GUI from 12 characters to 24 characters, then that does seem a bit too much. I think your question might be better phrased as 'How much of our development time should be spent on testing ?' and the answer might be anything from 10% -- 50% (possibly higher for safety-critical systems). If you are spending 2 days developing a patch, then testing should probably take no more than 1/2 day.

And yes, the scenario where as your application expands your test suite expands too, is very familiar. However if we add a new bit of functionality we tend to add new tests; a better approach, -- one we never have time for though we always have time to deal with not taking it -- is to modify existing tests. Modify code -> modify tests; add new code -> add new tests.

Yes, we use automated testing as much as we can; we use a lash-up of bash scripts, python programs and make to drive our automated tests. The processors we use never complain that testing is boring and repetitive, so we have no ethical qualms about working the poor dawgs close to heat-death. Sadly local labour laws prevent the same robust management principles being applied to the carbon-based life forms in our offices.

blocks|key|3460192|text|CI可以帮助您实现这一点，自动化是关键词。对于测试过程，你要做的是自动化测试、UT测试、接口测试、UIbased测试和性能测试。但是有一个根本的概念是需要接受的，质量不等于测试。在编码完成之前，由RD创建UT；在整个编码过程中，由QA开发UIbased测试和接口测试。当新的羽毛完成时，有一个测试套件来确保质量。你唯一需要做的就是功能测试，这是自动化测试不能涵盖的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3460193|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

CI can help you to achieve that, automation is the key word. For testing process, you have to do is automation testing, UT, interface testing, UIbased testing and performance testing. But there is a root concept needs to be accepted, quality is not equal to testing. UT can be created by RD before coding is finish; UIbased testing and interface testing are develped by QA in the whole coding process. When the new feather finished, there is a test suite to ensure the quality. The only thing you have to do is functional testing which automation testing can not be covered.

blocks|key|1167745|text|我相信你应该选择敏捷方法论，这将帮助你创建小版本，场景不会像现在这样长。此外，您还可以自动化一些重复用于回归测试的场景。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1167746|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I believe you should go for Agile Methodology, this will help you to create small releases and the scenarios wont be as long as they are getting now. Also you can automate few scenarios which are used repeatedly for regression testing.

blocks|key|1143772|text|我也相信你应该选择敏捷。由于敏捷是迭代和增量过程的组合，因此客户共享的故事点，即需求和更新。你可以按照优先级顺序对需求进行排序&可以为冲刺制定计划，也就是说，所有的需求都应该按照从高到低的顺序排序，因为产品待办事项和冲刺可以从产品待办事项准备好。因此，当sprint+1的开发正在进行时，您可以在此跨度中为sprint+1的测试准备场景。在sprint交付之后，如果在任何流程中有任何更改请求，都可以很容易地进行管理，并且在scrum和sprint回顾会议的帮助下，可以在即将到来的projects.Thus项目中改进流程，可以在短时间内轻松交付sprint项目。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1143773|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I also do believe that u should go for Agile . As agile is a combination of iterative &amp; incremental process therefore the Story Points shared by client i.e. requirements &amp; updates. u can sort the Requirement in the order of priority &amp; can plan for sprints i.e. all requirements should be ordered in high to low order as product backlog and sprints can be prepared from the product backlog . Therefore By the time development is in progress for sprint 1 , u can prepare scenarios for testing of sprint 1 in this span . after the sprint delivery if there is any change request in any process follow the same can be managed easily and with the help of scrum &amp; sprint retrospective meetings the process can be improved in the upcoming projects.Thus Project can be delivered in the sprints easily &amp; in a short span of time.

blocks|key|4928978|text|你为什么不自动化你的应用程序测试套件呢？当当前版本和下一个版本之间存在差距时，您可以同时自动化现有的测试用例。这不仅节省了测试周期时间，而且回归测试将更加准确，而不会跳过或遗漏任何测试场景。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4928979|您可以自动化至少60-70%25的总测试用例，这将节省大量的测试执行时间，并且可以在一夜之间运行。|4928980|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Why don’t you automate your application Test suit? Whenever there is a gap between the current and next release, you can automate the existing test cases in the meanwhile. This will not only save the Testing cycle time but also the Regression Testing will be more accurate without skipping or missing any test scenario. 
You can automate at least 60-70% of your total test cases which will save test execution time by a good margin and can be run overnight.

In my workplace we use scenario based testing. However whenever somethign is fixed or a new patch is added new scenarios are added as a result the list keeps getting longer and longer and takes 3 days plus to test the application.
Is there a way to do proper testing without taking a long long time?
What do you use?

Thanks

Software testing

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在我的工作场所，我们使用基于场景的测试。然而，每当修复了某些东西或添加了新的补丁时，就会添加新的场景，因此列表会越来越长，并且需要3天以上的时间来测试应用程序。有没有一种方法可以在不花费很长时间的情况下进行适当的测试？你用的是什么？谢谢

问软件测试
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问软件测试EN