Some understanding of software testing __ Software Testing

Some of the status quo

Now most of the software enterprises are the ecological chain, software testing is the most downstream. This also determines that many situations must be passively accepted. Even if a test engineer has a rich theoretical knowledge and a strong ability to identify risks, a change in the demand for a product can make him dumbfounded and then try to adapt to the rhythm. Product operation leading is necessarily the trend, test-led is not good products

There is also a point that has been debated for a long time on the issue of accountability. If the product on the line or after the release of problems, we will feel that the test link should be "reasonable control", the risk points listed and told the responsible person, sometimes a "why did not test out" unexpectedly let testing students speechless several common misunderstanding

From the above, as a test of the status is often very embarrassing, there is a "people carnival has my hair, out of the question I am sad to urge" feeling. But this is the truth. Before we explain, let's take a look at a few misconceptions about test comprehension:

Misunderstanding one: The test is simple, the technical requirements are not high
Many people think that software testing is to install and run the program, click the mouse, press the keyboard work. What is the truth. Software testing technology is constantly updated and improved, new tools, new processes, new test design methods are constantly updated, need to master and learn a lot of testing knowledge. Programmers who only have programming experience are not necessarily a good test engineer

Myth Two: Testing is to find bugs
Many people define test engineers just to find bugs, submit bugs, this is just a test case performer rather than a test engineer, the test engineer is a product quality control, on behalf of the interests of customers to control, acceptance products, so do more than just find bugs

Misunderstanding three: Software development after the completion of software testing
It is generally believed that software projects go through the following stages: requirements analysis, schematic design, detailed design, software coding, software testing, software release. Therefore, it is considered that software testing is only a process after software coding.
In fact, software testing is a series of process activities, including software test requirements analysis, test plan design, test case design, execution testing. Therefore, the software test runs through the whole life process of the software project. At every stage of the software project, the testing activities of different objectives and content are carried out to ensure the correctness of each phase. The object of software testing is not only software code, but also software requirements documents and design documents.

Misunderstanding four: Using the Test tool, is to carry out an effective test
To test a software or module effectively, first the software or module should be testable. Testability is an intrinsic attribute that reflects the quality of the software, and does not result in the testability of the software being tested because you use a test tool to conduct the test behavior. For the choice of test tools, just meet the needs and be able to run test cases automatically, rather than pursuing complex functions and unnecessary flexibility

Mistake five: Machine automation will replace manual test
We can not deny the role of automated testing, but the end-user of the software is always human, so only people can really understand the needs of people, such as the user experience, which is extremely can never be replaced. There are certain things that are good at automation and some specific things that people are better at. Therefore, it would be better to combine the two methods. Automation can do some repetitive operations and analysis of data to make work easier, but it is not good at determining relevance and judgment calls, fortunately, human beings are good at judging the importance

Well, after correcting a few misconceptions, let's see why we need software to test this post.

Since it can not dominate the product, status and so embarrassing, then why need to test this post, or the industry is also the industry's consistent optimistic about it.

Here's a look at the importance of several tests:
1. The timing of the problem exposure and the cost of solving the problem
The cost of fixing an error in the requirements phase is 1, in the design phase is its 3~6 times, in the programming phase is its 10 times times, in the internal testing phase is its 15~40 times, in the external testing phase is its 30~70 times and when the product released, this number is its 40~ 1000 times times. The cost of correcting errors is not linear growth over time, but almost exponential growth.
2. Programmers often fail to find bugs in the products they implement
Because of the orientation of people's thinking, we should avoid developing and testing their own programmed positions .

What needs to be done as a software testing engineer.

In each software enterprise, the test occupies a very important position, for a qualified test engineer, need to understand how the product wants to play, how the user will play, the operation wants the user how to play, the development how realizes, the test how carries on, what is the technical difficulty and so on. A good tester is very rare, understand the user use, understand the code implementation, write the interface test, do the performance optimization, but also to coordinate a variety of contradictions. Better understanding of product development than product development, understanding of operations, better understanding of testing and product quality recommendations

Some suggestions on the good habits of software test engineers:
1. Analysis first, then execute, this will be more than twice
2. The ultimate goal of the test is to control the quality of the software on behalf of the client, rather than trying to find all the bugs
3. Familiar with the various modules of the product, understand the product development logic, understand the customer's use habits
4. The unreasonable demand of product, development, operation must learn to reject
The technology of software testing is progressing, and the core idea of mastering test is more important than the specific technology compared with the concrete test technology. The highest level of testing is the use of the most simple and effective testing technology, to maximize the discovery of software defects we

Our team's testing requirements:
Concept: Software PRODUCT quality must rely on process control and data monitoring
Strategy: actively participate in product function definition and product design link
Vision: To become a professional software quality control team
Mission: On behalf of our customers benefit control team output product quality
How to work: Light Agile: Quick validation, value driven, team self organization
Team: Open mind, willing to learn, pursuit of quality, continuous improvement
Product View: Stable and reliable, perceptual and easy to use, condensed and innovative, considerate, data, data, data

We hope that the design quality department can represent the interests of customers, to develop more quality control standards, to communicate these standards to the product and design departments, to help them achieve these standards, and ultimately through quality control of these standards, delivery of high-quality products to customers