How can a new test engineer teach himself software testing? 【Lebo TestPro】

As for how to write test cases, starting from software defect management, and if there is time, it will be updated to interface performance. too long...

content:

1. 10 characteristics of test cases and 8 methods of writing test
cases What is the path?
3. How to further improve yourself?

1. 10 characteristics of test cases and 8 test case writing methods

Test case number, test item, test title, use case attribute, importance level (high, medium and low), preset condition, test input, operation steps, expected result, actual result;

The principle of writing test cases: 100% coverage of the requirements documents, such as when the requirements change, the test cases need to be modified and updated.

Equivalence class

Equivalence class partitioning refers to a typical and important black-box testing method.

Definition:
insert image description here
Division:
insert image description here
Division Rules:
insert image description here
Equivalent Class Use Case Design:
insert image description here
Case:
insert image description here
The writing method of the other 7 types of design use cases and the actual case click here to learn~

Zero
-

2. How do the testers who are already on the job teach themselves? What is the path?

Getting started with software testing is easy, but it's not that easy to take root. Compared to development, there is a lot to know. What are the requirements of big manufacturers for test engineers? Familiar with network, Linux, database, software testing process and theory, java or python scripting language. The development to the above is the use of automated testing theory and tools.

Automation-related tools include: selenium, JMeter, Appium, loadrunner, etc.;

If you continue to learn, it is interface testing, security testing, and agile testing that has been mentioned all the time;

Let’s talk about how to study on the job first, and then what to study?

1. Reasonable management of working hours

Incumbents should pay attention to the fact that in the process of testing, they will always find developers who say they don't understand this, and product managers who urge the revision of the user manual. Either the requirements review will not be called a test, but the change will definitely pull the test. Obviously continuous work, but always interrupted.

2. Learn to set goals for yourself

In the transformation from functional testing to special testing, there is actually a lot to learn and understand, because testing needs to be divided into industries, and functional testing has been done in a certain business, and it takes a lot of time to learn more about the business. Goals don't have to be too big, just in stages.

3. What should I learn in the on-the-job test?

In fact, a very simple method is that you learn what your immediate leader does. Add more communication groups, participate in some offline salons, you will learn a lot of internal industry information, and if you can, participate in some open source tool conferences. There are many people like this around, and it is very fast to improve yourself.

Roadmap and lessons:
insert image description here
Stop doing functional testing and unlock new technologies (1)
Stop doing functional testing and unlock new technologies (2)

The concept and function of interface testing
insert image description here

The performance stage is divided into JMeter and Loadrunner need information:
insert image description here

Performance test compulsory course for Xiaobai literacy (1)

Performance test compulsory course for Xiaobai literacy (2)

Performance test compulsory course for Xiaobai literacy (3)

A must-have tool for software testing promotion and salary increase (excellent course) (1)

A must-have tool for software testing promotion and salary increase (excellent course) (2)

A must-have tool for software testing promotion and salary increase (excellent course) (3)

3. How to further improve yourself?

It is recommended that you learn to be dissatisfied no matter what your current salary is. As long as you are satisfied with the status quo, there is usually no desire to learn anything. I've seen too many functional tests for five or eight years, and it's done bit by bit before the weekly release.

If you work for a longer time in the workplace, you may find that you are familiar with the business in your own field, but you must know that there are many fields of software testing, and the road of testing must be explored all the time.

If you have fully grasped the performance of the above path interface.

Even the simplest TDD needs to be understood and is the core event of intent in agile methods. Basically test first, many companies may not allow it at all, but it is necessary to learn some methodologies.

I wrote an automated Python learning content of about 4,000 words before:
https://www.zhihu.com/question/269537286/answer/1561393135

I hope that everyone will get a promotion and a salary increase, and make some achievements in their own fields~ I am Qing Pingle, and I have been focusing on software testing for more than 8 years and nearly 9 years. You can leave a message to learn software testing and obtain information.

Guess you like

Origin blog.csdn.net/leboxy/article/details/110537762