In terms of service coupling, a search engine can be divided into two parts: online and offline. The two parts are associated through index.
Online can be divided into core engines and online applications, while offline contains data crawling and offline processing processes.
The search engine online test can be divided into the following steps:
- Unit test:It is widely recognized that the earlier the error is discovered, the lower the cost of mistake change, and the higher the possibility of correct errors. TDD may be a good solution, but programmers should avoid testing their own programs, because it is difficult for them to suddenly change their perspectives and review code with a "destructive" view.
- Code check:Reading the code is of great value for creating a complete software testing and debugging method. In addition to manual inspection, you can also use some static code check tools to help.
- Function test:Data-driven testing is mainly to directly access the search engine or online application modules through a combination of different search keywords and attributes according to the use case, check whether the returned data and Parameters match the expected results.
- Performance test:Directly pressurize the search engine to test the true performance of the search engine. You can test the search engine's effective load and maximum load. In addition, the pressure can be applied through the front-end application, and the main pressure is concentrated on the front-end application. This test is also necessary, because your search engine is inseparable from the front-end application, this test can be used by the most authentic end users.
- Integration test:For joint debugging and testing, errors are often related to the interfaces between modules. practice shows that although some modules can work independently, they cannot be properly connected. Some problems that cannot be reflected by the program are exposed globally, affecting the implementation of the function.
- System test:System Testing integrates the system that passes the validation test as an element of the entire computer-based system with other system elements such as computer hardware, peripherals, data, and personnel. The purpose of a system test is to compare it with the requirement definition of the system to find out the inconsistency or conflict between the software and the definition of the system. Test points that may be involved include performance testing, capability testing, recoverability testing, compatibility/configuration/conversion testing, security testing, and Failover testing.
- Online Verification:This includes regression tests before traffic switch, regression tests after traffic switch, and online function module monitoring.
