A few suggestions about game publishing packages

1. Sort out the module system of the package and list the function points of each module. Focus on testing the areas that are prone to problems to ensure that the package is problem-free.

2. Before outsourcing, communicate with the planners of each system to understand what requirements have been changed and what new requirements have been added in this version, and then perform quality assurance on the changes.

3. During the out-of-package week, you cannot run the use cases step by step in the traditional way, but conduct more smoke and exploratory testing. It is difficult to find new ones where the opinions are obvious after multiple tests. bug. At this time, we pay more attention to the multi-person interaction, because when the package is released, the planning and programs will enter the current server for testing. This is the best time for our multi-person interaction, because in the internal testing stage, testing alone will It is not enough for people in the department to interact with multiple people.

4. After the package is released, everyone is already tired. At this time, the program is more concerned about whether the game can be logged in normally and whether the system can be started normally. At this time, as a tester, it is more about smoking quickly, that is, not letting go of every module under the name, and finding problems in time. At this time, the program can be packaged again. If serious problems are discovered the next day and the program is packaged, this will arouse the program's resentment and make it difficult for similar situations to occur in the long term.