在我们的测试工作中
除了需要不断的学习新知识外
还有一个可能常常被我们忽视的工作
那就是反思
它可以让我们总结过往的经验教训
它可以让我们复盘工作中的得失
它可以让我们找到未来需要规避的问题
它可以让我们获取工作中更高效的方法
Classic BUG
For testing, bug mention that most of the work we do. So in the past mentioning that bug gives us knowledge of it?
For each share out the bug, we will introduce to you the following questions:
This is what needs?
What about the demand point and this bug is?
bug description of what?
Whether describe clearly the causes and processes which produced?
After whether to allow developers to see immediately understand how to reproduce this bug?
This technology demand point is what?
What is the logic behind?
What is the reason this bug is produced?
Behind this point there is demand for which exceptions?
We use cases are taken into account yet?
Whether the same type of demand points have similar problems?
How do we design these use cases demand point?
This bug has taught us what testing methods?
Which brings us deeper methodology? ``
Only when these issues clearly say, is a classic bug brings us full thinking, so it makes sense to share, but also to bring more progress to our needs and enhance the testing capabilities.
Priority needs
The process of testing requirements, there is a content worthy of our reflection and sedimentation, that is representative of the demand. These demands, or is there a technology representative, or is there worth sediment content on the business logic, or the testing methods used in the testing process where there is a need to summarize. For these needs, which we call 'priority needs. "
On demand summarize, we also have a problem that can be shared:
This is a kind of demand?
The principle of this demand is what?
Technical architecture behind what?
Call the relationship between it and other modules What?
Our case design idea is what?
What is different from the past where demand?
Testing of this demand, what aids need to use?
The principle of this tool is what?
Demand in the past, whether there is a similar demand?
What are the similarities and differences of these needs point?
What are the needs of abnormal scenes or special circumstances need to be considered?
Why is this particular point?
This test will give us what needs knowledge precipitation?
What are the new methodology can bring us?
After this demand continues to dig deep, we will be on understanding the needs of a higher level, we will review the design and have a better complement and complete the test.
In order to do testing, software testers should not only depth, but also have the breadth; both should be efficient, but also have a complete quality testing itself. Therefore, we should be thinking forward and reverse thinking organically combine to balance efficiency and quality.
In other words, when we need efficiency, greater use of reverse thinking. When we need to test to ensure the full breadth of test quality, it is to use more forward-thinking.
Software testing Learning Exchange Q & qun: six six 3 4 85 nine hundred ninety-six
