Time Travel: 2014

Chapter 215 A few things about software testing

Even if it can explain the experience problems of different models of Lin Hui games.

But it’s hard to explain when it comes to frequency reduction.

It would be fine if there was no frequency reduction.

But the trouble is that Apple has really reduced the frequency.

More troublesome than this is the speed at which downclocking events occur.

Apple’s marketing staff still can’t figure out why what was originally an inconspicuous incident on Weibo has become more and more serious.

Could there be another driving force behind this incident?

It seems that this is the only way to explain it.

Otherwise, there are many people who complain about Apple mobile phones on Weibo every day.

Why did things turn out like this this time?

If there were pushers after the incident, it would obviously be inappropriate to blame Lin Hui.

The people behind this incident are deliberately trying to make a fuss about "downclocking" even if they don't use the game "Hill Climb Racing" as an entry point this time.

You will also find various other entry points.

In this case, it is unnecessary to involve Lin Hui.

As for who is the driving force behind it?

The first thing Apple thought of was the boom phone.

This is the most likely driver.

Judging from the current share of the global mobile phone market.

If Apple is going to be unlucky, it will definitely be the BOOM phone that will make the most profit.

And it seems that the most direct promoter of this incident on Weibo is the blogger "Science and Technology Baitai".

Although this person has always been independent, objective and fair in his evaluation philosophy.

But in life, no one has a time when they are really fragrant.

This kind of person who always seems to be fair is very lethal when he suddenly takes up the rhythm.

Apple's market analysts have long felt that this person has an eye for BOOM phones.

Among the mobile phones previously reviewed by "Technology", the main model of BOOM mobile phone has almost never been tested.

There's probably something fishy here.

Although there is no definite evidence, public relations personnel from Apple's marketing department still believe that there are signs of this.

In particular, the performance of the blogger "Technology Baitai" tonight was even more problematic.

If there is really a problem, it is a matter for the legal department.

What the marketing department has to consider now is not who is driving the event.

It's about solving the derivatives of the underclocking issue.

Although there are not many derivative events involving frequency reduction.

At present, external reports only claim that some games are lagging due to Apple's frequency reduction.

But if the time drags on for a longer time, it may not be possible.

Problems such as unsmooth use of the phone, slow running speed, and decreased running scores may be attributed to frequency reduction.

It's even possible that some problems caused by human manipulation can be attributed to underclocking.

Antennagate was only a few years old.

Apple doesn't want to make the same mistake just yet.

In this case, Apple chose to continue reporting the frequency reduction incident.

After all, when it comes to "downclocking", it will definitely affect not only Apple phones in the domestic region, but Apple phones around the world.

When it comes to global Apple phones, the idea is definitely to have Apple headquarters make the decision.

And Apple China can only choose to report it.

Although Apple already has a business in a large Eastern country, its business scale is not small.

But at this time, Apple's business in a large Eastern country is jointly responsible for four business divisions, including the Industrial Customer Division, the Consumer Electronics Division, and the Education Market Products Division.

These departments are basically not subordinate to each other and are basically a mess.

When it comes to ordinary events, it can be said that it is impossible to cope with such emergencies.

In this case, escalation seems to be the most correct approach.

Of course, Apple China's marketing staff also did not forget to report their analysis conclusions when reporting.

Although Lin Hui has decided to conduct internal testing of the workflow software.

But there is another problem before Lin Hui that needs to be solved:

Where should Lin Hui go to find internal testers?

This wasn't originally a problem.

According to Lin Hui’s previous work experience, so-called alpha testing was basically done part-time by internal employees of the company.

It’s rare to find someone specifically to test.

But now Lin Hui is just a polished commander.

Who should he go to for internal testing?

Lin Hui really didn't expect that he would get stuck on the last step of the software development process.

This is indeed the last step.

The internal testing involving a software is actually a process before the software is about to go online.

Generally speaking, the process of an Apple mobile application from development to release is:

It is nothing more than analyzing the needs first.

The purpose of the so-called needs analysis is mainly to conduct feasibility assessment.

After all, when a project begins, it may just be some abstract ideas.

In this case, ideas need to be discussed and researched.

When it comes to the specific research process, developers may need to split and subdivide their ideas step by step.

Break down general ideas into specific functional requirements.

After the needs analysis is completed, corresponding market research must be conducted.

Through market research, we can further measure whether the previously analyzed needs are universal.

Only then will the developers formally develop the app.

When it comes to some complex software development.

There may be two groups of people engaged in specific development.

One group of people is specifically responsible for UI development.

Another group of developers will wait to get the UI design drawings and then develop functions and interfaces based on each UI interface renderings.

When no technical difficulties are involved, the specific development is generally not too complicated.

This is just a general situation.

It is still very troublesome when it comes to some scenes that require interaction.

Many functions that are easy to implement in the eyes of ordinary people are actually very difficult to implement.

After the App development is completed, it enters the project testing phase.

Testers test the entire App in order to find some problems in the program.

This process generally requires developers to simultaneously debug problems discovered by testers.

After testing and debugging, the application can basically be officially put on the shelves.

This is just to put it simply.

It involves big applications like Tengu and Mouyin.

Testing is extremely cumbersome.

The first thing to do is product process testing.

Testing at this stage is generally completed by product managers and developers.

Test each functional module one by one according to the logical coherence of the product to see if it can be used smoothly, especially whether some core function points have been implemented.

This test focuses on testing the functional requirements of the software.

The main purpose of this round of testing is to check whether the functions are unusable or missing;

Is the interface wrong? Are the inputs and outputs correct?

Are there any shortcomings in the database?

Functional issues such as initialization and termination errors.

After completing the first round of functional logic testing by developers.

The next step is to build a test environment for professional testers to conduct download testing.

Tap the screen to use advanced tools Tip: You can use left and right keyboard keys to browse between chapters.

You'll Also Like