Font Size:
Theme:

Chapter 61:Test Cases Completed

"Well, since you understand, then I'll give you two jobs, and you'll write about the test cases of this document."

Liang Jun pointed to a design document of the Mechao Age, written by Xiong.

This is the most important feature of the new version of the Mecha Era, which changes the 2.0 version of Xinghai Battlefield.

Zhong Ming glanced at this version number is clear, before he wrote the document is Xinghai battlefield 1.0, the following changes, optimization is 1.1, 1.2 and the like, this time became 2.0, it shows that there is a very obvious difference with 1.0.

Obviously, this document is the most important part of the whole test work, this was originally carried out by Liang Jun, Liang Jun felt that this workload is not small, so he wants to try to give the bell ring, even if the bell is not good, at least the test cases to make, he can modify it on this basis, can save a lot of things.

"Anything you don't know can ask me at any time."Liang Jun ordered two more words and returned to his work station.

The bell is in no hurry, so I read the file again.

After watching it, the bell frowned straight, which is what.

He thought that Liu Yuxin was either directly using the documents he left behind, or let people rewrite them all from scratch, and the results are now good, and they are not good!

The part of the document to the function modification, are those that they have written in the document, basically copying and modifying, repairing, even if it is a new function; in addition, the document also adds a large number of stimulus recharge content, such as the forced blood loss in the Xinghai battlefield to 5%, which means that the local players can only kill eight in a row, nine consecutive kills, and can now kill in 20 consecutive!

There are many similar rules, coupled with other intensified recharge activities, basically have been "I want to circle money" these four words to write naked on the face.

“O you, iniquity will not live.”

The bell is incredulous.

He was a little compassion, he can dig a lot of holes in the new version of the document to let Liu Yuxin jump, but he did not do so, mainly do not want players to bear this result; now, the bell did not dig a hole, Liu Yuxin himself dug a hole.

It can be seen from the revision record of the document that the original version of this document was indeed written by Xiong Cai, but Zhou Zhen changed, and Liu Yuxin also changed.That is to say, the final appearance of this document, which is the meaning of Liu Yuxin.

“Okay, then get to work.”

The bell began to write test cases according to the specification, and all the changes were taken one by one and listed in a table.The process itself is not high in technical content, that is, need to be careful, although the bell is not very like this work, but he is still good, get to two o'clock in the afternoon to finish.

After that, open the new version of the game to see if the function of the game is completed as written on the design document.In fact, a large part of the functions in the test cases can be measured directly by intelligent systems, but some of the more complex functions still have to ring the bell in person.

By the time you leave work, it’s done.

The bell directly sent a message to Liang Jun: "The test is over."

Liang Jun was shocked: “The test is over?Don't you pug me, it's two days of work, you're done in less than a day?How can I tell you, change it, improve it, give it to me tomorrow morning, and don't let me pick out a bunch of problems at that time."

The bell chime: “...”

Go ahead, then change it.

The clock is wondering, what else can be changed?

Oh, wait, let’s get some functional optimizations!

In addition to the regular design documentation and finding bugs, the test team can also improve the function optimization.For example, in the test process, the test found that a function is not reasonable, or in the actual use of the process of problems, this is not a bug, because the design is so, this time the test can be in the internal platform to the design team to put forward functional optimization recommendations, detailed in their own problems, you can give a modification plan, you can also let the design group out of their own modification scheme.

Of course, whether to change or whether the design group has the final say, and most of the optimization solutions will be called back by the design team, and will not really change.But in short, providing the ability to optimize this thing is within the scope of the test group's work.

Then again, why is the optimization recommendations of the test group often called back?Because the test group is not a design, the understanding of the design intention is often not so deep, so some functional optimization suggestions are very immature in the design group, so the design group ignores it.

But who is the bell, the change he can think of, is certainly what Xiong did not expect!

Of course, Zhong Ming certainly will not mention some substantive suggestions for changes, and does not mention any suggestions that have great benefits for the function, and mention some of the optimization of the chicken ribs at the corners of the corners, do not feel bad, change and toss.

"There's an icon on the UI that feels like three pixels to the left."

“The expression of the button is a bit of a problem, and it should be changed to four states.”

...

The bell found a whole bunch of functional optimizations, and then they all added to the test case table.

After it all was over, it was time to leave work, and the bell was packed up and left.

Liang Jun saw the bell ringing so early and felt very worried.

“Can this guy do it?The work is so perfunctory, it feels unconcerned to live... Alas, forget it, and tomorrow he will bring the test case, and I will overhaul it again."

Liang Jun continued to be busy testing another function.

The process of testing, first of all, is to do the test case, which is equivalent to listing a summary table, and then testing the test case one by one in detail in the game, experimenting with various extreme situations.All kinds of situations are smooth, you can submit bugs in the background, these bugs will be assigned to the design group, the design group is responsible for the design of the function of the function and then assign the bug to the corresponding program and art, and other program modifications to complete, test acceptance, even if it is repaired.

Zhong Ming is responsible for the work is the previous few, he is to write the test cases, after the test to submit the results to the Liang Jun, and then by the Liang Jun to submit the bug, follow up.

...

The next morning, the bells arrived as usual.

The people in the test team are basically stuck and not late, which is a little different from the situation of the Mechao Age project.

Like Xiong Cai, it is crazy to work overtime at night, flexible in the morning, and often late, but Liu Yuxin does not matter; and the test team is crazy at night, and work on time in the morning, this is much harder, after all, their lives are heavier.

The work of the bell is finished, so continue to touch the fish and finish the end of a drama that has not been seen before.

Liang Jun, who went to the water machine to pick up the water, saw it again, very speechless.

“This little clock... is too bad!”I’ll see what kind of test case he brings me in a moment!”

Comments

No comments yet. Be the first to comment on this chapter!