In the traditional industry of China Mobile projects, the test process is a set of sets, requirements review -- development detailed design review -- use case review -- test review
-- test execution -- report output -- arrangement online -- online acceptance, Many meetings require the participation of all production, research and testing, and the time investment is very large. The reason is
that the project/business iteration cycle is the last version every month, and there is enough time to do these. When the whole process of testing is involved, it can be confirmed that it can be found.
There are many problems, so here is a word: moving the quality forward, it is easier to understand. It is not until the test is executed that the problem is found, but the problem is moved forward and moved to the
requirements review, design review, and use case review. This step is done The good thing is one direction of testing: business experts, see that the height of the project/product has reached
the height of the product, consider the test case scenario from a global perspective, be very familiar with the business, improve the influence, and the development/product will come to consult your business knowledge
The core of Vipshop's process is the train release system. The project schedule is to release a version every week, that is, there is only one train per week. If the project wants to
go online, it needs to get on the train at the specified time, which means at the specified time. The development test is packaged. The whole process of the project is to schedule and plan according to the driving time of this
train . (Of course you have to ask a lot of online questions, what to do? What about emergency projects? Isn’t there a
term for temporary trains in the Spring Festival travel period?)
In the Internet industry, the iteration speed is obviously accelerated. It is also a must.
The requirements review will be carried out according to the size of the requirements. If the requirements are small, it is just a document review.
When we were at Vipshop, our team did a bit better, that is, in the testing process, we required the development and testing to have output, and asked them to sort out the function points:
which functions were added/modified, which files were changed, and self-test points , self-test results, static code inspection, unit tests are all passed, these are also
a kind of responsibilities of testing, project assurance is not just a matter of testing, testing has the obligation/responsibility to improve the quality from the entire project process.
After the test, the test must go through the smoke test. The smoke test must first check whether the output of the development contains the ones mentioned above. The test has the right to directly
call back this test, and the problem that blocks the main process must also be called back. Smoke does not pass. The quality of the code of the project that fails to pass the smoke is worrying; for functional testing, the
tester has a test machine and deploys the project in its own environment for functional testing.
A set of development environment, hahaha)
regression test, after the functional test is completed, it is necessary to develop and merge the code to the master (the branch that finally goes online). Due to the parallelism of multiple projects, there may be
code merging problems, and it is necessary to return to another round. This The environment can verify the main use case, and can also use automation to verify, there is also a code
review link;
It needs to be mentioned separately here, code permission control. After developing the merged code, there is no permission to push the code. The code permission is controlled by the tester. At
this time, the code needs to be modified. The reason is that the function test is omitted, or the merged code is wrong, you can Make a statistic;
pre-release test, after the regression is OK, package and deploy to the pre-release environment, which is all the production database, and focus on verifying whether the configuration (configuration file,
DB...) is OK, there are also many tests here. If it does not pass, you can do statistical data;
on-line acceptance, provide the final package for operation and maintenance, and do the online acceptance
and some details of the process of Vipshop. Explain what function this project has;
will it have any impact on the old online functions; what risks exist; whether it can be accepted online, how to accept it, and if there is no monitoring;
what is the rollback plan, brainstorming
requirements review- - Use Case Review--Testing--Smoke Testing--Functional Testing--Regression Testing--Pre-release Testing--Online Acceptance--Data Monitoring
Testing, not looking for bugs, should be called quality assurance, and the means is the route of your career planning.
Management is probably the route that many people want to take. Many people think that if you
stay Yes, those who have the overall risk awareness of the project also need certain opportunities;
technology, this road is what many test students are taking or want to take. They want to engage in automation and performance, because the improvement of technology means an increase in wages. , it
is very important to learn a language well;
no matter what you do, if you have the rare resources, the treatment will naturally go up.
Back to the theme of this time: the advantages of process and work experience will be highlighted. Combine the existing team with past experience, formulate processes, or make suggestions for
existing processes;
1. Quality migration, test intervention in advance, from the demand side If you find a problem, go to the requirement review with the problem, and fight against the product/requirement;
2. Merge the code regression test, after communicating with the development, do not go online directly, you need to go through it again;
3. On-line review, think about online dependencies, risks, and old data /Functional impact, rollback scheme;