?? Management determine efficiency, method determine the effect. Everything is true.
"The" Art of War "has a cloud: Mado does not fight, the temple will win, and it is more important; the husband does not fight, the temple is invalid, and it is less. Even more than calculated, but nothing!
?? First discuss which work can be done in the current test department. According to our current development, the next step will all be used, and the two development groups will distinguish the development tasks according to different services involved, and the developers will also increase accordingly. From now on, from now on behalf, after using the three-layer architecture, it will continue to increase the complexity of the system, because there is different business objects in the client, intermediate layer, and database server, and all business objects may The path that appears will also increase. Individuals think that in this case, component testing, integration testing, and system testing are required. Among them, component testing and integration test faces code level, system testing facing the application level. Component tests mainly consider testing a single component present in the system, check whether the component meets the design requirements, whether or not the corresponding input is made, whether there is a corresponding output, this stage is like checking a nut. Quality, To check its inner diameter, outer diameter, weight, height, and whether the thread meets the design requirements, and this nut is an indispensable component in the entire machine, but it does not have any function as an individual; integrated test It is the interface problem between the key inspection components. Check if multiple components can complete a established function, whether there is a normal cooperation between multiple components, as if they pass a screw through a steel plate, and then we top The tested nut is screwed, and if the screws and nuts cannot be tightly coupled together, there is a problem with the interface between the different components. For component testing and integration testing, you can use a black box test method and a white box test method for testing. • The benefits of carrying out component tests and integration tests are from the beginning of development, the test work can be intervened, and the problem will be allowed to limit the problem in the first floor - or the unit is tested. When designing, the integration test is started, and if a problem occurs, it can be limited to the interface between the components. Use "step-by-step integration", or "continuous integration" method, the scope of defects can be limited to the range of control, which is conducive to the grasp of the project progress. However, based on the human hand and ability of the current test department, the component testing and integration test cannot be carried out because the human hand is not enough. Even if the next step is increased to 5 people, it is also unable to test all programmers' code; at the same time, Test and integrated tests require development of "Drive Modules" and "Store Modules", which requires different applications to develop different applications to complete the test. At the same time, such work is relatively high, usually requires testing units with test case designers, test scripts developers, "drive modules", and "driver modules", "drive modules" and "stub module" Developers, of course, while also have test items managers and independent databases to configure managers. The most critical problem is that if you want to test and integrate testing, the entire project needs to perform in a rigorous specification, and the loop ring between different tasks. For example, if the pre-system analysis and design are not clear enough, it is difficult to develop frequently during the development process, and it is difficult to perform test scripts and test programs during development. ?? We can now start, the cost is relatively low, and the effect is better is the system test. System testing is relatively mature in technology and methods, and it is relatively easy. We can put more energy into exploration operation processes and working methods, and as long as these work is solid, introduce new technology and tools will bring To relatively good results; the opposite, if the operation process is not clear, there is no effective way to make a working method, and the new field will be confusing. So it should still be done by easy, step-by-step progress.
?? Now consider the system testing, it will involve five test types, namely functional test, performance testing, compatibility test, interface testing and data correlation and integrity testing. Explain one by one: ?? 1. Function test. It mainly includes testing of the actual business covered by the system. The actual business here refers to the work that the user is also necessary to perform, such as the library of materials, must fill in the new outbound list, and the departure of the outbound bill must also meet certain requirements (business rules) And the processing of the outbound bill will also be subject to some specified processes (such as applications, review, outbound). This part will not consider content increased by the design of the computer system. ?? 2. Performance test. As in this part, like other systems, mainly consider the system's processing capabilities for services in different test environments. The client / server hardware configuration, client / server software configuration, client / server resource occupation, network load conditions, large number of business processing, concurrent processing, etc. will be considered. ?? 3. Compatibility test. This part of the main test company's development of the company is compatible with different hardware platforms and software platforms. For hardware mainly considering the impact of different printers on printing, the operating system mainly considers the impact of different Windows versions on the system operation, and considering some common applications on the system, such as this time, "Tsinghua Violet input method "There are conflicts with some controls of DEV. If the WAN is involved in the WAN, some cases related to the WAN are also considered. ?? 4. Interface test. This part of the main test system is added to the actual business that does not have a direct relationship with the actual business. For example, shortcut keys, icons display, text display, initialization of the interface, input type / length limits of the control, position adjustment / order adjustment in the grid, etc. The key to the key is the distinction between the same function. The function test is included in the actual work, while the interface test is facing things that are expressed on the computer for the functionality required to implement the user needs. Perhaps more accurate use cases of functional testing will mainly come from demand, while the interface test is used more from design and implementation. ?? 5. Data correlation and integrity test. This part can also be a comparison with functional testing. For functional testing, the accuracy of data is also considered, but this part of the test will be primarily limited to a single subsystem. For example, outpatient charges, after charging the prescription, reduce the booklet stock in the pharmacy, and modify the prescription sign. The operation of the outpatient toll subsystem is, and the operator responsible for the charge is not concerned about the changes in the pharmacy, because this part has exceeded his business scope, but the business of the pharmacy operator is related to these changes. Then this part involves the test of multiple system data streams belong to data correlation and integrity test.
For work, I want to talk about some problems from the perspective of our test, and of course I hope everyone can discuss it. • For the adjustment of the process, mainly consider how to achieve high efficiency and effectiveness of work, as well as interaction and communication between different teams. For example, I hope that we can strive to establish the following workflow: ?? 1. Demand phase. This stage is very important for the development group and test group, because we also experience the impact of demand variations on design and development and testing. I hope that in the development below, put demand in a decisive location, although the demand changes will appear, but we should try to avoid some of them, mainly to avoid the daily work that users think that they think is their daily work, very normal A simple thing is not proposed. It is usually found in our in-depth research needs and some algorithms. ?? I consider adjusting from testing to help improve demand. Specifically, as follows: ??. Design and plan test work for function test cases in the demand phase. The design of most of the functional test cases related to the main business will be completed in accordance with the needs. It is expected that the test personnel understand the needs of the business, try to find the missing or deviation of the demand; ??. As the highest level document that guides the entire test work, it can be understood as the Constitution, design documentation, and specific implementation must not violate the requirements in demand documents. For Defect's definition, it will be a large extent to the demand document (lasting in this document Description This Defect's judgment standard); ??. For the demand document, it is necessary to pay attention to the writing problem of the document itself, such as whether there is an secondary meaning, whether it is accurate, this job is the testability of the inspection document, that is, check Demand documents can provide basis and help for testing; Change or add new demand, then it should be described in the supplemental needs. Moreover, it is also desirable to use the discussion and review of the project in the project group to use as an effective work. ?? 2. Design phase. This stage of the test staff is mainly to confirm whether the design is corresponding to the needs, try to avoid different understanding of the needs of developers, and to ensure the testability and description of design documents. The focus is based on the detailed design document, add test cases, focusing on functional testing, performance testing and data correlation and integrity testing. ?? 3. Implementation stage. In the coding implementation phase of the development group, the work of the test group will still focus on the pre-preparation of the test. In addition to continuing to improve the original test case, you will focus on the UI test case. At the same time, consider writing a use case suitable for automated testing into testing. In addition, you must prepare test data to complete all preparations before performing the test. ?? 4. Exercise phase. At this stage, the main task is based on the test cases, and submits Defect and registering the Defect that has been processed. In addition, the attenuation test required for the version iteration is also considered. For content involved in some test cases, the problem is found in the actual operation, and the test case is added as a supplementary test case. ?? 5. Evaluation phase. At the end of the test, the test work summarizes and effectively evaluates, adjusts or improves the details found in the test process, extracts as much as possible, so that the content and method can be used in the next version of the test. Iterate use. (end)
?? I will also make an entry and exit rule for each test stage, when starting that stage, when this stage enters the next stage, it will clearly indicate. Oh, there will be a documentation for the detailed description of the entire test process to clearly express all tasks in the entire test process, especially those related to work in the above phase. What is another job is the design of test cases. This issue will be treated as the most important thing this year, mainly considering improving the effectiveness and maintainability of test cases.
?? Some opinions, I also hope that there will be a chance to continue discussing and perfect.
?? Chen Lei ??
