I often hear some comments in Zhihu, Tieba and other places: "Is the functional testing industry saturated?" With these remarks, many newcomers who plan to change careers are secretly glad that they have not changed careers yet, while others are helpless, sighing that there is one less career that can be changed.
So, what is the truth? Is there no future for functional testing?
01 Change cognition: Gao Fenglin can also be produced in ordinary positions
For most of us, we are all ordinary people, and most of the positions we hold are ordinary and ordinary positions. But don't underestimate the ordinary position you are in.
Some time ago, the Aeronautics Administration exposed an ordinary person with outstanding achievements——Gao Fenglin, a front-line employee of the Shenzhou 11 spacecraft manufacturing and a welder. Relying on his years of experience and learning, although he is only a basic rocket welding worker, he is also a staff member appointed to participate in the formulation of high-level welding quality standards at the highest-level technical analysis meeting.
Ordinary welding skills, after being trained to a high degree of proficiency, he was able to make "third-class merit" for the country, and was exceptionally awarded the title of super technician. What's more, it is an IT technology in the Internet + era! Functional testing is naturally practiced to perfection, and practitioners will naturally get the glory they deserve.
The author believes that for practitioners of functional testing, "sit and eat" is indeed easy to be eliminated, and it is right to have this concern, but if you can become the most proficient and efficient among the people who "rely on their laurels", One, then, you too can be Gao Fenglin in the IT world.
Believe me, no technician who is proficient in a certain industry will be eliminated. The ones who will really be eliminated by the times must be those "half-baked" players-the kind who don't have solid skills, but always like to be surprised and frighten themselves.
For technicians in IT positions in the new era, either, you should maintain the concept of lifelong learning, constantly develop your own technology, and let yourself be at the forefront of technology; or, you should be proficient in the technology you know , or in other words, do it line by line.
You must choose one of these two career development paths, otherwise it is only a matter of time before you are eliminated. dont you agree?
02Skill improvement: proficiency is king
Well, without further ado, I will share with you some commonly used test methods in functional testing. I hope that everyone can have a solid grasp of the knowledge points in the early stages of entering the industry. After all, only with quantitative changes can breakthroughs in qualitative changes be achieved.
For functional testing, when verifying each function of the product, we need to test and check the product item by item according to the functional test cases, so as to ensure that the product meets the level required by the user.
So, what are the test methods that we need to pay attention to every day?
Whether the function can be used normally
1) Button function: such as delete, cancel, update, save and other buttons, whether the function is normal and whether it can be used;
2) Delete function: In some places where multiple messages can be deleted at one time, do not select any message, press "delete" to see how the system handles it and see if there will be any errors; then select one or more messages and delete them to see if they are processed correctly ;
3) Search check: Where there is a search function, we continue to input content that exists in the system, and also need to input content that does not exist, to see if the search can output results normally;
4) Page links: whether each link has a corresponding page, and whether the switching between pages is correct;
5) Chinese characters: Enter Chinese characters at a specific position to see if it will be executed, whether there will be garbled characters, etc.;
6) Repeat submission: After successfully submitting a record, go back and submit again to see if the system will execute it again;
7) String length: In the specified position, after entering some content exceeding the length, check whether the system can execute it; will it report an error;
8) Input information position: When inputting information at the place where the cursor stays, check whether the content can be input normally; determine whether it will jump to other places after inputting information at the cursor.
Whether the function can be performed normally
9) Punctuation marks: where punctuation marks should be entered, test whether specific punctuation marks will be executed, including but not limited to: spaces, Chinese and English quotation marks, enter key, etc. and see if the system can handle it correctly.
10) Character type: where the specified type of content should be input, enter other types of content to see if the system will execute it; whether it will prompt that the wrong type of character is entered;
11) Duplication of information: In some places that need to be named and the name should be the only information, enter the duplicate name or ID (duplicate names include: whether it is case-sensitive; whether there are spaces, whether it is counted as 2 names, etc.), check whether the system can also be executed correctly;
12) Rename: When modifying the name, change the item that cannot be renamed to an existing item, check whether it can be executed, and whether an error will be reported;
13) Use the back key multiple times: where back can be executed, repeatedly execute back multiple times to check whether it will be executed and whether an error will be reported;
14) Search function: where there is a search function, we continue to input content that exists in the system, and also need to input content that does not exist, and check whether the results of the search are correct; if multiple search conditions can be input, reasonable and unreasonable ones can be added at the same time Reasonable conditions, to see whether the system handles correctly;
15) Enter key: After the input is complete, press the Enter key directly to check whether the system will execute;
16) Mandatory items: Whether to add prompt information to the required items, such as adding * before the required items. If the required items are not completed, can you continue to execute;
17) Upload and download files: Check whether the file can be uploaded and downloaded normally, and whether the uploaded or downloaded file can be opened;
Does it affect other functions after performing certain actions
18) Consistency of addition and modification: Check whether the requirements for adding and modifying information are consistent. For example, if you add an item that is specified as an integer, the modification must also be an integer; if you add a required item, the modification should also be mandatory.
19) Integrity of the information brought out: When viewing information (including update information), check whether the conclusion information contains all the filled information to ensure that the information brought out is consistent with the added information;
20) Item-to-item correlation: After adding or deleting some items, will it affect other items; if there is an impact, what will be the result;
21) Shortcut key: Whether the set shortcut key can be executed normally, and whether there is a problem that it cannot be executed due to being occupied. In addition, check whether there are restrictions on shortcuts for some fields that are not allowed to enter information, such as selecting people and selecting dates;
22) Upload and download files: Check whether the format of the uploaded file is clearly defined, whether the system has explanation information, and check whether the system can make normal judgments and identifications. If the uploaded content is a virus that meets the format requirements, whether it can be detected;
03 Make a good summary
For the problems we encounter in our daily work and the corresponding solutions, we must make a corresponding summary. It is said that a good memory is not as good as a bad pen. Many times, we always think that we can clearly remember the specific content we did at a specific time, but in fact, it is easy to forget after a while. So the best way is to record it and remind yourself not to forget.
In addition, functional testing is a meticulous job. Not everyone can quickly find bugs, and not everyone can know where it is easy to "overturn". Therefore, we must summarize some experience and take it out from time to time. Wake up your memory.
Only in this way, as time goes on, your skills will become more proficient.
Finally: The following complete software testing video learning tutorial has been sorted out and uploaded. Friends can get it for free if they need it [Guaranteed 100% free]
Software Testing Interview Documentation
We must study to find a high-paying job. The following interview questions are the latest interview materials from first-tier Internet companies such as Ali, Tencent, and Byte, and some Byte bosses have given authoritative answers. Finish this set The interview materials believe that everyone can find a satisfactory job.
