Open source internship experience sharing: openeuler software package reinforcement test

Open source internship

*

To cultivate the ability of college students to participate in open source communities ,openEuler The community is carrying out open source internships , Students can practice online in the community , Choose what you are interested in SIG Participate in community projects , Complete internship tasks and accumulate points , Earn internship salary and internship certificate with points .

Open source internship official website ：

https://www.openeuler.org/zh/internship/

The author participated in the open source internship openEuler Community QA SIG The job of , The following share is about openEuler Experience in software package reinforcement testing .

#

About SIG-QA

As a popular operating system ,openEuler A lot of software has been released , But these releases are not necessarily complete , There may be quality 、 Safety and other issues , In order to reduce the software development cost and use risk , We need to test the software package for reinforcement .

openEuler Communities according to different SIG（Special Interest Group） To organize , In order to better manage and improve the workflow . The work related to the software package reinforcement test is carried out by SIG-QA Team responsibility ,SIG-QA The goal of the team is to test the composition openEuler Distribution software , Improve openEuler The quality and testing capabilities of the community . The team will be in src-openeuler Organization warehouse （https://gitee.com/src-openeuler） Release software Related tasks of package reinforcement , You can go through intern-QA The tag is located to all tasks related to the software package reinforcement test , Then select the task of interest to claim .

The task address is shown in the figure below

#

Skills required for software package reinforcement test tasks

The most important thing to do software package reinforcement testing is to be familiar with Linux The operating instructions of are the same as shell Scripting language . Because the software is running on the Euler server , Need to pass through Linux Instructions to deploy the relevant environment and perform package functions . And finally you need to write shell The script executes the test case and submits the code to the warehouse . In a few cases, you may need to write code that runs in other languages to verify the functionality of the software package , This is determined by the software to be tested .

#

Specific test steps

• Prepare the system environment

View the relevant environmental requirements in the task , Choose the right one OS edition . The system environment construction process is not described , There are detailed in the warehouse word Documentation to guide .

see OS edition

•  Deploy the test environment --mugen The test framework

After deploying the system environment , You need to deploy the test environment . We need to use mugen Test the framework .

mugen The framework needs to start from openEuler Warehouse (https://gitee.com/openeuler/mugen) To pull .

mugen frame

•  Learn to mugen frame

If a worker wants to do a good job, he must sharpen his tools first ,mugen The framework is our weapon to accomplish the task , Only familiar with mugen Framework can complete the task .mugen The framework defines how the use cases we write are executed ,shell How to write script format , It also stipulates that various public functions can be called directly . Learned to mugen frame , Just know how to write a test case 、 How to run test cases , All of these can be in mugen The warehouse README.md Learn from the documentation .

mugen The framework has two important packages , One is suite2cases, One is testcases Of cli-test. stay suite2cases We only need to write one in it json file , The test case name is stored inside （ Script name ）. When json When there are multiple test cases in the file , We can use instructions to control whether to execute one use case or multiple use cases at a time .cli-test Store script files for execution . Detailed knowledge can be obtained through reading mugen Documents provided by the warehouse and B Station video for learning .

mugen Important folder

•  Test specific software

When the environment is ready , We need to test specific software . First of all, we need to be familiar with the functions of the software （ The following pictures are shown in crontabs For example, a software package ）, Its various instructions . The goal of our test is to cover the basic command line functions of the software package, that is, all instructions . The so-called sharpening a knife does not miss the woodcutter , Only fully understand the role of software before testing , In order to achieve twice the result with half the effort , We can look for documentation about this directive to read , If there is less information about the software , We can also read its source code .

crontabs Instructions that need to be tested

For software package testing , The points to be tested include but are not limited to whether the software can be downloaded normally 、 Normally open or close 、 Each instruction of the software can be executed normally and achieve the expected effect , The software can be uninstalled normally . After the test , Make sure that “ Traceless ”, That is to ensure that all relevant files of the software are cleared , Perfect recovery , In this way, a software package test is completed . After any one of these links has been tested , If there is a problem , You need to submit to the corresponding software package warehouse issue, For the development engineer to solve .

Examples of functional test methods

• Submit test results

After all instructions have been tested , When the code is written , You can submit code . It should be noted that mugen After the warehouse is configured , Redundant files will be generated , These do not need to be uploaded , Must be cleared before submitting , Which documents can be compared mugen Warehouse documents . Submit pr when , Bind your own task number , And attach the screenshot of the successful operation of the test case .

pr explain

During the test , If you don't understand anything, you can ask the tutor who is responsible for the task , The tutor will be very responsible to tell you how to solve , But we should ask questions after careful consideration . Submit pr After that, the teacher will leave a message for the existing problems , Reply in time and make changes .

•  Gains and suggestions

To participate in openEuler The open source internship in the community is of great significance to my personal growth . By completing the software package reinforcement test task , I'm concerned about linux The use of instructions is more handy , about shell Script writing is also more skilled . The process of testing software packages , In fact, it is also a process of learning software , In the future study or work , When you encounter a certain scenario, you may happen to be able to use the software we have tested to solve the problem . Like crontabs Software can be used to complete scenarios related to timed tasks , But before I came into contact with the task, I was completely unaware .

I hope interested students can actively participate in SIG-QA From the task of , Don't be timid because you don't have a solid knowledge of a certain field , This is just the best time to improve yourself , Try boldly , Calm down and learn according to the problems you encounter , To explore , Finally, we will find a solution ！

The author of this article | Qin Haiqi

Qinhuangdao branch of Northeast University

Junior majoring in computer science and Technology

This article is from WeChat official account. - openEuler（openEulercommunity）.
If there is any infringement , Please contact the [email protected] Delete .
Participation of this paper “OSC Source creation plan ”, You are welcome to join us , share .