Chapter 163 Blind students can always find Hua Dian

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

But there is still a 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 experience, so-called alpha testing was basically done part-time by employees within the company.

It is 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’s nothing more than analyzing the needs first.

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

After all, at the beginning of a project, the project 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 requirements and function points.

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 doing specific development.

One group of people is specifically responsible for UI development.

Another group of developers will wait for the UI design drawings to be obtained 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 troublesome.

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 whether 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 input and output 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 download and test.

Some teams use people from other departments in the company to conduct testing.

Usually it is a product manager, company executive, big boss or other personnel.

As long as it's not a company executive test, it's easy to say.

It’s outrageous that you still like to change your requirements when you don’t understand anything.

The product manager should at least understand something. The big boss is basically a technical boss and it is impossible to blindly change the requirements.

As for other personnel, other personnel generally have no say and can basically be ignored.

But no matter who completes the test, the testing behavior of this process also needs to be quantified.

Testing without quantification is meaningless. Only quantification can truly reflect the test results and ensure software quality.

After completing the above two testing tasks, you can now find some small-scale users and conduct target user testing at a low cost.

At this time, we need to make corresponding test preparations. One is the test result recovery channel. Common channels include questionnaires, software problem feedback channels, user communication groups, etc.

This last step is also often called grayscale testing.

However, the above processes are only some testing processes involving larger applications.

Like Lin Hui's current software, there is no need for logic testing and download testing at all.

Just perform the grayscale test directly.

When it comes to programming logic and other issues, Lin Hui can't do it well.

Don't engage in IT, just provide for your retirement.

When it comes to the internal testing of workflow software, it is quite different from the internal testing of games.

Being an internal beta tester of Apple software workflow is particularly troublesome.

The trouble is mainly with software distribution.

Apple mobile apps cannot be distributed "at will" like Android apps.

Lin Hui once suspected that the founder of Apple had a strong desire for manipulation.

In short, there are endless rules for everything involving Apple.

Apart from anything else, even the testing of Apple mobile phones is restricted for you.

Specifically, how to test Apple mobile software?

The most important issue during testing is the distribution of the software to be tested.

In other words, you have to distribute the software that needs to be tested to the testers' devices.

From the previous life, due to different distribution mechanisms, there are generally three types of software testing involved.

They are enterprise signature distribution, TF signature distribution and individual developer account distribution.

When Lin Hui worked in his previous life, when it came to this kind of testing, the development team usually directly used corporate signatures to distribute internal test applications.

This distribution method is a privilege of enterprise-level development accounts in the Apple App Store.

Developers in the Apple App Store generally have three types of accounts.

They are personal developer account, company developer account and enterprise developer account.

The Apple enterprise-level development account is a high-level developer account provided by Apple to iOS developers.

Although Lin Hui's previous account in the app store was already a distinguished developer account.

But in the final analysis it still belongs to a personal developer account.

Functionally speaking, the functions of individual developer accounts in the Apple App Store are still far from those of enterprise-level accounts.

Of course, the price of enterprise-level development accounts in the Apple App Store is also more expensive than personal accounts and company accounts, with an annual fee of US$299.

And you don’t have to have money to apply for this kind of account.

It is very difficult to apply for a brand new business account through Apple's official website.

On the one hand, when applying for a corporate account, developers need to provide Apple with a large amount of information;

On the other hand, Apple’s approval number for new business accounts is also extremely limited.
To be continued...