Restart the Gaming Era

Biquge www.xbiquge.tw, the fastest update to restart the game era!

Okay, since you understand everything, I will give you two tasks first, you can write the test cases of this document.

Liang Jun pointed to a design document of Mech Age, written by Xiong Kai.

What Xiong Kai wrote is the most important function of the new version of Mecha Age, a change to version 2.0 of Star Sea Battlefield.

Zhong Ming saw the version number clearly. The document he wrote before was regarded as Xinghai Battlefield 1.0, and the various modifications and optimizations later were regarded as 1.1, 1.2 and so on. This time it became 2.0, which means that it is very different from 1.0. obvious difference.

Obviously, this document is the most important part of the entire test work. Liang Jun was originally responsible for this. Liang Jun felt that the workload was not small, so he wanted to try to assign it to Zhong Ming. After making the test case, he can modify it on this basis, which can save a lot of work.

If you don't understand anything, you can ask me at any time. Liang Jun ordered a few more words, and went back to his station.

Zhong Ming was not in a hurry, so he read the document first.

After reading it, Zhong Ming frowned, it was nothing.

He originally thought that Liu Yuxin would either just use the document he left behind, or have someone rewrite it all from scratch, but now it turned out to be a mess!

The part of the document that modifies the function is what I wrote in the document. Basically, I copied it, modified it, repaired it, and it is forced to be a new function; in addition, a lot of stimulating recharge content has been added to the document. , For example, the mandatory blood loss in Xinghai Battlefield has been reduced to 5%, which means that rich players used to only have a maximum of 8 or 9 consecutive kills, but now they can get 20 consecutive kills!

There are many similar rules, coupled with other intensified recharge activities, basically the four words I want to collect money are written on the face naked.

Okay, you can't live without doing your own crimes.

Zhong Ming was helpless.

He was a bit sympathetic at first, he could dig a lot of holes in the new version of the document for Liu Yuxin to jump in, but he didn't do it, mainly because he didn't want the players to bear the result; now it's okay, Zhong Ming didn't dig holes, Liu Yuxin himself Dig a hole for yourself.

From the modification records of the document, it can be seen that the original version of this document was indeed written by Xiong Kai, but Zhou Zhen changed it, and Liu Yuxin also changed it. In other words, the final appearance of this document is what Liu Yuxin meant.

Okay, let's get to work.

Zhong Ming began to write test cases according to the specification, sorted out all the changes one by one, and listed them in a table. The process itself is actually not very technical, which means it needs to be careful. Although Zhong Ming doesn't like this job very much, he is still good at it, and it will be over after two o'clock in the afternoon.

After that, open the new version of the game to see if the functions in the game are completed as written in the design document. In fact, a large part of the functions in the test cases can be directly tested by the intelligent system, but some more complicated functions still need to be tested by Zhong Ming himself.

Until it was almost time to get off work, it was finished.

Zhong Ming directly sent a message to Liang Jun: The test is over.

Liang Jun was shocked: The test is over? Don't fool me, it's two days of work and you can finish it in less than one day? How did I tell you, make changes and make it perfect, and give it to me tomorrow morning. Don’t ask me to find a bunch of faults then.”

Zhong Ming: ...

All right, then change it again.

Zhong Ming pondered, what else can be changed?

Hey, yes, let's mention some function optimizations!

In addition to routinely reviewing design documents and finding bugs, the test group can also provide functional optimization. For example, during the test, if the test finds that a certain function is unreasonable, or there is a problem in the actual use process, this is not a bug, because the design is like this. At this time, the test can propose function optimization suggestions to the design team on the internal platform, and explain in detail For the problems you encounter, you can give a modification plan, or let the design team come up with a modification plan.

Of course, the design team has the final say on whether to change it or not, and most of the optimization plans will be called back by the design team and will not be really changed. But all in all, it is within the scope of work of the test group to provide optimization of this matter.

Having said that, why are the optimization suggestions of the test group often returned? Because the test group is not the design, the understanding of the design intent is often not so deep, so some function optimization suggestions are considered immature by the design team, so the design team ignores them.

But who is Zhong Ming, the changes he can think of must be something Xiong Kai didn't even think of!

Of course, Zhong Ming will definitely not propose some substantive modification suggestions. He will not mention any suggestions that are of great benefit to the function, but only mention some trivial optimizations at the corners.

There is an icon on the interface UI that seems to be shifted to the left by 3 pixels.

There is a problem with the presentation of the button. It should be changed to 4 states.

...

Zhong Ming found a lot of functional optimization solutions, and added them all to the test case table.

After everything was done, it was time to get off work, Zhong Ming packed up his things and left.

Seeing Zhong Ming leaving so early, Liang Jun felt very worried.

Can this kid do it? The work is so perfunctory, and I don't feel like I don't care when I divide the work... Oh, forget it, I will overhaul it when he brings the test cases tomorrow.

Liang Jun was busy testing another function.

The process of testing, first of all, is to make test cases, which is equivalent to listing a general table, and then inspecting the test cases in the game one by one, and experimenting with various extreme situations. After all the situations are smoothed out, bugs can be submitted in the background. These bugs will be assigned to the design team. The design team is responsible for the function design and then assigns the bug to the corresponding program and art. After the program modification is completed, the test and acceptance pass , even if it is repaired.

Zhong Ming is responsible for the previous items. He writes test cases, submits the results to Liang Jun after the test, and after Liang Jun revises it, Liang Jun submits bugs for follow-up.

...

The next morning, Zhong Ming arrived as usual.

The people in the test group are basically stuck in time, and no one is late, which is a bit different from the situation of the Mech Age project.

People like Xiong Kai worked crazy overtime at night, flexible in the morning, often late, but Liu Yuxin didn't care; while the test group worked crazy overtime at night, and got to work on time in the morning, which was much harder, after all, their Live more.

After Zhong Ming's work was done, he continued to fish, and finished watching the ending of a drama that he hadn't finished watching before.

Liang Jun, who went to get water from the drinking fountain, saw it again and was speechless.

This little clock... is too careless! I'll see what kind of test case he brings me later!