What are basic skills? The result of Baidu is: the basic knowledge and skills necessary to engage in a certain job.
Reasoning 1: The word " basic" means that basic skills must be the basic process of source testing. Reasoning 2: The word
" must" means that whether you are advanced test development or primary manual testing, you must have skills.
Knowing the concept of basic skills, "Does development technology count as a tester's basic skills?", it definitely doesn't count. I am a junior tester, I don't know how to automate, but I can still complete the test manually. Although inefficient, it can also be tested. This shows that development is not necessary for testing, and of course it is not a basic skill.
Back to the topic: What are the basic skills of software testers? Combined with the above analysis, the structure of the next question is as follows:
1. First look at the basic process of software testing
2. Second, look at the job requirements of junior testers
3. Clarify the basic skills of software testing
4. How to firmly grasp these basic skills
1. Basic process of software testing
The above figure is the basic process of software testing.
1) Requirements review
2) Plan writing
3) Use case design
4) Use case execution
5) Defect management
6) Test report
The work of all company software testing teams basically revolves around this set of processes.
Which of the 6 links are the basic skills, but also combined with the job requirements of the primary test.
Because the work content that junior testers do not need to master is not called basic skills.
Second, look at the job requirements of junior testers
From the job description of primary functional testing (also called manual testing), combined with the basic testing process, we can disassemble the work content related to skills, which are the following 4 points.
1) Write test cases
2) Complete test execution
3) Submit tracking defects (called defect management in the basic process)
4) Submit test reports
The "requirements review" and "plan writing" in the basic process can only be done by the test team leader or test manager, and the junior test engineer does not need to be involved, so these two items are not basic skills.
3. What are the basic skills of software testing?
But the test report is "statistical test results and defect statistics". Because it is just statistics, it is far from being a skill . The final basic skills of software testers are the following three items:
1) Test Cases
2) Test Execution
3) Defect Management
Whether you are doing Internet software testing, offline hardware testing, or " vehicle testing " combining hardware and software, the above three are basic skills and have wide versatility.
So as long as you want to eat this bowl of rice, you must firmly master these three basic skills.
The basic skills are so important, how to master them firmly, next I will elaborate on the four dimensions according to 1) what it is, 2) what it is useful for, 3) how to do it, and 4) how to strengthen it.
4. How to firmly grasp the three basic skills of testing - test cases
1. What is a test case?
The professional term is explained as: a test case is a test execution document designed for a specific test purpose.
The popular explanation is: for the function to be tested, what do you want to test, you have to write it out in the form of a standardized use case by the test team.
Test cases, in simple terms, are the documentation of personal testing ideas .
Examples of test cases
2. What is the function of the test case?
A test case has 3 roles, each of which is very important:
a) prevention of leaks
b) criteria for implementing tests
c) evaluation of test efforts
3. How to make test cases
First of all, to understand the 8 elements of the test case:
Element 1: Use Case Number: Project + Module + Number
Element 2: Use Case Title: Expected Results + Operation Steps Element 3
: Module/Project: Belonging Project or Module
Element 4: Preconditions: To execute this use case, what are the prerequisites Operation
Element 5: Priority: Indicates the importance or influence of the use case P0~p4 (P0 is the highest)
Element 6: Test steps: Describe the operation steps
Element 7: Test data: Operational data, if not available, it can be empty
Element 8: Expected Result: desired result
Next, it is necessary to understand the commonly used test case methods.
Method 1: flow chart method .
Method 2: Equivalence class division method.
Method 3: Boundary Value Analysis
Method 4: Decision Table
Method 5: Orthogonal Method
Method 6: Error Guessing Method
Commonly used methods are the first three, namely flow chart method, equivalence class division method, and boundary value analysis method.
In the test case method, the most important thing is to understand the difference between the application scenarios of each method .
a) The application scenario of the flowchart method is "to describe the user's use scenario, and to involve multi-functional combination logic in the business scenario". Typical representative is "process test"
b) The application scenario of the equivalence class division method is "the test data that cannot be exhausted or the amount of test data is too large", and the typical representative is "the input box test of the page".
c) The application scenario of the boundary value division method is "on the basis of the equivalence class, for the test data with a boundary range, the test data is generally digital or time", and the typical representative is "input box test with a boundary range " .
d) The application scenario of the orthogonal table method is "a use case needs to cover multiple input conditions (less than 4 conditions), and there are dependencies (constraints) between the conditions"
e) The application scenario of the judgment table is "there are too many valid test cases, but because the input value of the condition is Chinese and English characters, the boundary value division method cannot be used to narrow the test range, so the mathematical statistics tool 'judgment table' is used to narrow it down reasonably number of test cases".
f) The application scenario of the error guessing method is "testing possible errors based on experience", which is not suitable for Xiaobai.
5. How to firmly grasp the three basic skills of testing-test execution sharing
1. What is test execution
It is to strictly implement the written test cases, execute them on the software, verify whether the expected results are the same, and record them.
The red font is the record after the test execution
2. What is the use of test execution?
Finding flaws (also called bugs) in software.
3. How to execute the test?
step1: Execute the test case according to the priority of the test case
step2: compare whether the actual result is consistent with the expected result in the test case.
If consistent, the record is passed. If not, the record fails. If it cannot be executed, the record is blocked.
step3: Use case execution failure: record and submit the defect.
step4: Update the test case.
Why is it possible to update the test case when the test is executed? The reason is that the test case is not completed overnight, but the result of repeated optimization. If the tester finds that the test case is missing, redundant, or unable to be executed during execution, just perform corresponding operations.
4. How to firmly grasp the test execution?
If the test is executed manually, it can be executed strictly according to the test cases . Therefore, although test execution is a basic skill, the technical threshold is not high, just be careful when executing it.
6. How to firmly grasp the three basic skills of testing-test execution sharing
1. What is Defect Management
Defects, also called bugs. Defect management is to submit bugs and track bugs.
2. What is the use of defect management?
1) Software test engineers should deal with development through defect management and fix bugs in the software;
2) Software test engineers can help development locate defects through defect management.
3. How to do defect management?
For defect submissions, tools such as Jira or Zen Tao can be used. Tools are easy to master, tools are not the point, just means.
Therefore, the core of defect management lies in the preparation of defect submission content (as shown in the figure below).
Defect submission template
1) The submission elements of defect management are divided into the following five types:
a) bug number, b) bug status, c) severity, d) priority e) bug type
It is very easy to grasp the defect number, just English + numbers.
Defect status, severity, and priority can be output according to the company's requirements.
The bug type is not required, it depends on the company's requirements.
A company's requirements for defect submission elements
2) But the core elements of defects are the following three:
a) Defect Title [Core]
The function of the defect title is to describe the defect clearly.
Clearly described evaluation criteria: that is, developers can know what bug is reported by just looking at the title without looking at other elements.
In order to describe clearly, the defect naming technique should adopt the naming method of [actual result + expected result].
For example, "The verification code can still log in successfully at (10,15] minutes - expected failure, because the valid time is within 10 minutes"; another
example "QQ number is empty, the next step can be clicked (expected not to be clicked)"
b) Defect description (important)
Defect description, including these four pieces:
1) Pre-conditions (corresponding to the "pre-conditions" of the test cases)
2) Recurrence steps (corresponding to the "test steps" of the test cases)
3) Expected results (corresponding to the "expected results" of the test cases)
4) Actual Result (corresponds to the "actual result" of the test case)
The frame part is the defect description
Although the defect description is important, it is very simple to write, just write the core of the test case .
Why is it necessary to express the test case again in the defect description?
Reason 1: The test case refers to an important output of the internal execution of the test team, and is an execution reference within the test group (not viewed across groups).
Reason 2: The defect is mentioned to the development, and you have to let the development reproduce the defect (bug). So you need to clearly write the core content of the test case in the bug.
c) Necessary accessories
Attachments can be the following three types, the purpose is to avoid and develop disputes
Or pictures - bugs that can be fed back with pictures must use pictures
or logs - if they can be put in logs, they must be put in, which is convenient for development and bug analysis
or video - for occasional bugs, be sure to record videos
4. How to firmly grasp the defect development
7. Summary:
Business understanding, effective communication, thinking logic... Are these important for testers?
Of course it is important. But these are abilities, not basic skills.
For technical positions such as software testing, basic skills refer to technology.
However, with solid basic skills, it is still difficult to get a job under the current economic environment, and automation technology must be mastered.
Because all walks of life are having a hard time, at this time, when companies employ people, they will find more cost-effective ones.
So everyone wants to engage in testing work. On the basis of getting the basic skills, I hope you can learn some automation things.
The source of the screenshot is directly hired by boss, welcome to ask for confirmation
If you are not only interested in the basic skills of software testing, but also interested in automated testing, and want to systematically learn software testing by yourself, you don't have to worry about not having learning resources. Now I will offer you a 13G super practical dry goods test and learning resource, which involves a very comprehensive content. Including linux database, functional testing , python, interface testing , performance testing , UI automation testing ...
Finally: The complete software testing video tutorial below has been organized and uploaded, and friends who need it can get it by themselves [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.
