We started our project in July 2018. Up to now, the system has been updated from version 1.0.0 to version 1.3.1. At this stage, 1.3.2 and 1.3.3 and 140 are developed in parallel. Several iterations of testing are required in parallel. Product requirements Already prepared to 1.5.0.
For the above three digits, the change in the first digit is equivalent to changes in the entire system such as refactoring, and the largest changes are involved, and this number will be upgraded; if the second digit changes, it means that a functional module is added to the original foundation. It may also be a business logic change; the third-digit change is only the optimization or small change of the previous function, which has little impact on optimization requirements;
Iterative requirements process:
1. According to the existing customer needs and business, the market operation requests the product manager, and the product manager organizes the requirements and business logic;
2. The product manager will review the requirements prototype and related documents, and the corresponding page design drawings after finalizing the draft. Meeting to discuss the delivery technology;
3. After the requirements review meeting, the development and testing needs to consider the implementation process and prepare test cases for the existing business needs after the requirements review meeting. Questions and difficult points can be raised. At the same time, the development completion time and the testing time will be determined so that the product or project manager can advance the project schedule.
4. If there is time during this period, a test case review will be conducted to ensure the coverage that the test will achieve. After the development is completed and the requirements are delivered to the test, the test tests the existing use cases and business logic, raises bugs, and tracks and repairs;
5. After the test is completed, the delivered product is checked and accepted to determine whether it meets the original requirements; verify that there is no problem and arrange it online.
The above is the daily iterative task flow. Each minor version iteration has several to a dozen requirements to be dismantled, and the front and back ends are split and then joint debugging. The time during this period is generally within one month, and the small iteration is generally within two weeks. In this way, it can avoid that the process is too long, causing the staff to consume energy and generate negative energy.
1. Preparation before testing:
For testing, we need to conceive various test points in advance, and listen to them during normal development and product detailed requirements. In case the requirements change or the interaction cannot be done, the interaction method must be changed. Our test cases should also be changed accordingly. A team is really To work together, we should not be responsible for certain positions, and we should enter our own strength and think of things that others can't think of but to do. We must provide support and assistance. It is best to make up for the deficiencies of others in addition to our own duties, so that we can play an elite group. spirit.
2. Between test executions:
1. Ensure that all test cases are executed;
2. Test case coverage reaches 100%;
3. Verify that the new business logic is, and whether it affects the functions of the previous business logic.
Each project of the company's business has dockable data and linked business, which can open up services and provide customers with more comprehensive network connectivity. Based on the erp system business, the product has made a lot of functional optimizations and demand upgrades according to market needs. The real-time feedback and technical support from the market are for customers to use the system more easily. The more iterations we have, the more experience needs In the optimization, the role of testing is to check the problems before the new demand goes online and to ensure that online customers use various incurable diseases to respond to.
3. After the test business goes online:
The project is already operating in the market. There are 60 online companies, with tens of thousands of customers behind them, and the average daily online usage will reach about 3,000. This means that if a bug is found in online operations, the test receives feedback and needs to be quickly located and synchronized to the development for rapid repair and emergency online, and the market will always have endless demands and deadlines for us. During this period, our ability to withstand stress and communication and coordination will be tested.
With the increase of iteration experience, we basically tested the whole system before going online to return to various functions and business logic, and strictly controlled the outflow of bugs. This is not only a responsibility to the market, but also a lot of relief for us after we go online. The project implements multiple iterations and parallel development, so that small steps can be taken quickly, and the testers need to arrange multiple versions to be tested in a tight time. After the police force many times, the individual is iterative experience, the way of handling things, and personal emotions. The control has been greatly improved and improved.
The above is an overview and summary of some work content that testers will dabble in during the iterative development of the project.