The core of software testing
Just write down the sentiment, plain text, difficult to read, no wonder;
A requirement is a model used to satisfy a specific user story.
The development is to put the model on the ground
The test is to verify whether the model satisfies a specific user story, rather than verify whether the model is good-looking or bug-free ...
but:
- Since the development may damage the existing model that satisfies the user story during the landing process, it is necessary to verify the existing model, or to verify whether the model meets the specific user story
- And because the original model is too large, it takes a long time to verify the value of the original model;
- And in fact, the model is based on the product manager's guess of the user story, rather than the objective truth, so the value of the model to the user also needs to be tested;
- It is necessary to satisfy: to quickly verify the value of the new model, but also to satisfy: the value of the original model cannot be lost. Two satisfactions lead to the current dilemma of software testing: relative to product and development, testing is lagging behind;
The product's job is to add value to the original model and improve the value. In the process, pay attention to avoid affecting the original value.
The development work is to add logic to the original code, improve the code, and pay attention to avoid affecting the original logic (value) during the process.
The job of the test is to verify the new value and ensure the old value; in a more understandable way, the test needs to ensure the value of a toy (Lego?) That is used by products and development to play together. Among them, the quality of products and developers is not relevant, and the consequences are difficult to predict.
How to solve the above problems?
- Hiring better products and development? ? ?
- Although it is necessary to quickly verify the value of the new model, should we follow a set of specifications when proposing the new model, so that the final output of the finished product is valuable
- Although it is necessary to quickly verify the value of the new model, if the original value is too fragile because of the pursuit of speed, is it worthwhile for the tester to spend a lot of time on the original value? Why not establish a good specification from the beginning to minimize the impact of code changes on the original value
- What are the constraints in the whole process? Can it be improved?
- The development process is a constraint point, the development time is often too long, and the functions developed are not many
- Unplanned tasks are a constraint point, often due to online problems, which leads to continuous termination of core work
- Regression testing and new function testing are also constraints. Regression of old functions takes a lot of time, and verification of new functions also takes a lot of time
- ……