关于软件测试的思考 [英] Reflection about Software Testing
问题描述
您好！
我已阅读有关软件测试的更多信息，今天我无法找到以下问题的答案。
1.
什么时候应该停止在系统中发现一些错误？
2.
如果你以前在软件开发方面有经验并且在早期阶段找到一些bug错误，那会更有好处吗？
3.
有些人说你需要掌握沟通技巧，才能与组织层面的不同人沟通。这是真的吗？如果是，为什么？软件测试人员与组织中不同层的人员有什么关系？
4.
当您在Scrum团队工作时，您是否总是有开发人员和软件测试人员，或者是作为开发人员和测试人员的人？
谢谢！
1。你永远不会停止。
2.是的。
3.是的，原因很明显。
4.取决于tesm经理。 />
5.请阅读代码项目快速解答常见问题 [ ^ ]。
1。你应该永远不会停止。
这当然是校长，但出于经济原因，与其他更多的开发相比，可能不值得在工时找到每10000次发生的错误紧迫的需求。资源有限。
2.是的。
但是，经验丰富的测试人员也会有标准的方法来消除明显的错误。
所以关键字是经验。
3.嗯，你至少需要与老板和同行沟通。
然后你可能需要与用户和开发者互动。
4.通常最好将开发人员和测试人员的角色分开。
在我看来，主要原因是作为开发人员，你对自己是盲目的设计。
您倾向于按正确的顺序按下按钮并每次输入正确的数据。
最终用户很想找到以永远不会的方式崩溃程序的方法因此，一个好的测试人员会在发布软件之前完成这项工作。
然后再次，这取决于手头的资源。
感谢您对软件测试的兴趣。我只想讨论你的问题。
问题＃1。
我们需要停止测试某个时间。这可能取决于以下条件：
- 在承诺的测试截止日期到期时停止测试。
- 当我们无法再检测到时停止测试即使执行了所有计划的测试用例，也会出现错误。
- 在发布截止日期或测试截止日期等截止日期后停止测试。
- 在测试用例时停止测试已经完成了一些规定的通过百分比。
- 在测试预算结束时停止测试。
- 当代码覆盖率和功能要求到来时停止测试达到理想水平。
- 当错误率降至规定水平以下时停止测试。
- 在beta测试/ alpha测试结束时停止测试。
此外，测试指标可以帮助测试工程师做出更好，更准确的决策;比如何时停止测试或应用程序何时可以发布;例如，完成百分比，通过的百分比测试用例，测试用例百分比失败等。
问题＃2
是的，测试工程师具有软件开发经验非常重要。您需要编写用于编码的测试自动化的脚本。此外，您需要在执行白盒测试或代码检查时理解代码。您需要对开发人员代码执行重新设计。所以，你需要软件开发知识。
问题＃3
是的，沟通是一项非常重要的技能对于任何测试人员测试人员需要清楚地描述错误以便更好地理解。有时测试人员和开发人员位于同一办公室;在那种情况下，非常好的书面沟通是必须的。此外，测试人员需要根据情况进行缺陷倡导。因此，测试人员应该需要非常好的沟通技巧。
问题＃4
这取决于你的团队结构。
你也可以访问我的博客，以便更清楚地解释你的问题。请点击 http://modern-testing.blogspot.com/ [ ^ ]
Hello!
I have read more information about software testing and today I can't find some answer to my questions below.
1.
When should you stop finding some bug error in the system?
2.
Is it more benefit if you have previous experience in software development in order seach and locate some bug error in a early stage?
3.
There are some people saying that you need to have skills in communication in order to communicate with different people in the layer of the organisation. Is it true? If yes, why? What relation does a software tester has to do with people in different layer in a organisation?
4.
When you work in a scrum team, do you always have a developer and a software tester or is it a person who is acting as a developer and tester?
Thank you!
1. You never stop.
2. Yes.
3. Yes, for obvious reasons.
4. Depends on the tesm manager.
5. Please read Code Project Quick Answers FAQ[^].
1. You SHOULD never stop.
That is of course the principal, but for economical reasons it might not be worth putting in the man hours to find a bug that happens every 10000 times compared to the development of other more pressing needs. Resources are limited.
2. Yup.
However, an experienced tester will have a standard ways to smoke out the obvious bugs too.
So the keyword is experience.
3. Well, you need to at least communicate with your boss and your peers.
Then you might have to interact with users and developers.
4. It is usually better to separate the roles of developer and tester.
The main reason, in my opinion, is that as a developer you are blind for your own design.
You tend to press buttons in the right order and input the right data every time.
End users are notorious to find ways to crash programs in ways you could never thought of.
Hence, a good tester will do that job before release of the software.
Then again, it is down to the resources at hand.
Thanks for your interest in Software Testing. I just like to discuss about your questions.
Question#1.
We need to stop testing in a certain time. It may be depends on the following conditions:
- Stop the testing when the committed testing deadlines are expiring.
- Stop the testing when we are not able to detect any more errors even after execution of all the planned test Cases.
- Stop the Testing when deadlines like release deadlines or testing deadlines have reached.
- Stop the Testing when the test cases have been completed with some prescribed pass percentage.
- Stop the Testing when the testing budget comes to its end.
- Stop the Testing when the code coverage and functionality requirements come to a desired level.
- Stop the Testing when bug rate drops below a prescribed level.
- Stop the Testing when the period of beta testing / alpha testing gets over.
Also, Testing metrics can help the Test Engineer to take better and accurate decisions; like when to stop testing or when the application is ready for release; like, Percentage Completion, Percentage Test cases Passed, Percentage Test cases Failed etc.
Question#2
Yes, It is very important for a testing engineer to have experience in software development. You need to write script for test automation that is a coding. Also, you need to understand code while performing white-box testing or code inspection. You need to perform re-engineering over the developer code. So, you need software development knowledge.
Question#3
Yes, Communication is a very important skill for any tester. Tester need to describe bugs clearly for the better understand. Sometimes testers and developers are mot located in same office; on that case very good written communication is must. Also, tester needs to perform defect advocacy based on situation. So, tester should have need a very good communication skill.
Question#4
It is depends on your team structure.
You may also visit my blogs to more clarification of your questions. Please click on http://modern-testing.blogspot.com/[^]
这篇关于关于软件测试的思考的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
