What knowledge do you need to do software testing, and what do you need to do in software testing?

What do you need to learn about software testing?

It is recommended to learn from the following paths:

The first step is to lay a good foundation, which is similar to learning other skills, and it is important to lay a good foundation.

The workflow of a test engineer is generally as follows: the idea of a test plan, the writing of test cases (equivalence classes, boundary value analysis, flow charts, causal diagrams, orthogonal tests, etc.), then the writing of test reports, reporting bugs and tracking bug fixes, and learning to master various common testing methods such as functional testing, interface testing, app testing, automated testing, etc.

The second step is to learn some commonly used testing tools, such as loadrunner (performance test), selenium, appium (automated test), postman, jmeter (interface test), etc. These tools are very practical and can also help us greatly improve our work efficiency, and bug management tools also need to be learned, such as Zen Tao is very useful.

Finally, it is recommended to learn some auxiliary skills, such as learning common commands and databases of Linux systems, such as MySQL, Oracle and other mainstream databases.

In addition, programming ability is also an indispensable skill for software testing engineers, and those with rich interview experience may know that many companies will have a corresponding assessment of the programming ability of candidates for software testing positions.

While programming skills are not a must for beginner test engineers, mastering a programming language can help them cope with situations that testing tools can't, such as writing more complex test scripts in some cases, and that's where programming languages come in handy. At the same time, proficiency in programming languages is also a must for advanced to advanced software testing engineers, which can help improve our competitiveness and benefit our career development.

First of all, software testing is a quality inspector who is responsible for ensuring that your software is bug-free before it is put on the shelf for users.

First, familiarize yourself with the requirements and write use cases.

Before the app is developed, there will be a requirements specification, which will explain what the app does, how to use it, how to display and present her functions, and the development will carry out research and development according to this document.

Second, test and fix bugs

After writing the use case, and the app is available, you can do the test according to your use case, including but not limited to functional testing, UI proofreading, data proofreading, interface testing, performance testing, etc., in the testing process, you may find that it is different from the presentation of the requirements document, or there are problems such as inability to proceed to the next step, or automatic flashback, etc., this is a bug, you need to hand over to the corresponding development, let him modify.

Third, the regression.

After the development and correction of the bug, you have to go to the regression test, it is possible to change a and b and there will be problems, this is normal, the regression is to prevent omissions or new bugs

Fourth, prepare a test report.

and other related information, according to this report, the top will judge whether it can be released, of course, some companies go through the extremely fast process, and they won't even let you write this, just a sentence is OK.

That's it for a short time, welcome to add

1.The process of determining whether a product at a given stage in the software life cycle meets the requirements established in the previous phase.

2.Formal proof of program correctness, that is, the process of using formal theory to prove that the program complies with the provisions of the design specification.

3.Evaluate and report on market evaluation, examination, testing, inspection, auditing, etc., or whether certain processing, services or documents are consistent with the specified requirements.

Validation is a series of activities and processes designed to verify the logical correctness of software in a given external environment. That is, to ensure that the software does what you expect it to do.

1.Static confirmation, not actually executing the program on the computer, proving the correctness of the software through manual or program analysis.

2.Dynamic confirmation, by executing the program for analysis, testing the dynamic behavior of the program to confirm whether there is a problem with the software.

The object of software testing is not only program testing, software testing should include the documents generated at all stages of the entire software development period, such as requirements specification, outline design document, detailed design document, of course, the main object of software testing is the source program.