Shulou(Shulou.com)06/03 Report--

This article mainly explains "what are the misunderstandings about software testing". Interested friends might as well take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn what are the misunderstandings about software testing.

Misunderstanding 1: "throughout the project life cycle, testers only need to participate in the project after the development is completed."

This is one of the biggest misunderstandings. If that's the case, there must be a huge problem with the project. Introducing quality assurance (QA) only at a later stage is a huge risk to the quality and timing of deliverables. Testers need to be involved in the project at the same time as developers, because testers need to understand requirements, analyze differences, prepare deliverables, plan and run tests.

If testers are only involved in the later stages of the project, they will rely on the developer's understanding and follow-up of the project when testing the product, and the quality of the deliverables is unlikely to improve in the end.

Instead, the test team should be involved in the project from the start, with its own time to think, understand, analyze, and participate. This not only helps the QA team do better testing, but also makes the QA of the entire project team better. Many organizations have realized this and brought in the QA team from the beginning of the project.

Misconception 2: "testers will not become project managers."

Many people believe that testers lack professional training in management. But the two do not interfere with each other. Managers need to master skills such as personnel management, cost management, time management and so on. These skills have nothing to do with their work, whether they are testers, developers, or any other technical staff.

Project management skills need to be developed separately, and people in the world can be trained no matter what kind of technology they are engaged in and which school they belong to. Therefore, as a tester, the pursuit of project management will not be encouraged or hindered. This is a separate area that anyone interested in can participate in.

Myth 3: "reporting to the development supervisor is an obstacle to the tester's career."

Ideally, there should be an independent vertical department, and both the development supervisor and the QA supervisor should report to the project manager. Sometimes, however, there may be situations where the test team and the development team have the same development lead, and you have to report to someone who doesn't know how to conduct in-depth testing.

But in fact, as long as you do a good job and patiently help leaders complete the evaluation practice, there will be no mistakes and no long-term negative impact on your career.

Misunderstanding 4: "people with poor coding skills will engage in software testing."

In most cases, testing also includes coding. Testers need to write a complex structured query language (SDL) to validate data or to create test data during extraction transformation loading (ETL) tests / data validation. When conducting a migration test, the tester needs to convert the written code from one database to another. When conducting automated testing, testers need to write scripts in Java, Perl, or other programming languages.

Therefore, this view is simply untenable.

Myth 5: "Software testing is about clicking at random."

It is generally believed that testing is about clicking randomly in the user interface (UI) and then recording details in Excel or other documents. In fact, testers perform very clear test steps to ensure that UI/ applications work properly under very special circumstances. Therefore, the horizon is the most important.

Users have no idea of operational restrictions, and neither do testers. So it's important to explore the user interface, which may seem like a lot of random clicks. Only testers know that there are methods and steps for this crazy operation.

Myth 6: "testing is a document record, or filling in an Excel table."

First of all, it needs to be emphasized that everyone involved in the project must keep a record of it. An accurate and complete document can provide basic and historical proof for the project.

However, documentation is particularly important for testers because the product we create is not a program or module, but a quality assurance presented manually. The Microsoft Office suite is the first choice for most teams, but if you want to do better, use test management software.

Myth 7: "you don't make much money as a tester."

If this applies to testers, it would be a big mistake. This kind of thinking may need to be changed. Even so, compensation depends on many factors, and it is wrong to regard tester status as the only reason for lower pay.

Myth 8: "testers are not appreciated."

Software testing is sometimes like a "thankless" job, depending on how much the company culture attaches importance to the team. Try to keep a positive attitude and prove it with your work. I agree with the following statement: if the company and customers appreciate the QA team, things will be much easier. But if they don't appreciate the QA team, we don't have to underestimate ourselves.

Misunderstanding 9: "testers slow down project delivery."

Testers must wait until the development is complete before starting testing, whether or not they start working with the development team at the same time. This gives the rough impression that testing slows down the project again and again.

This problem will not occur if the test cycle is planned in advance on the computer. Therefore, testing is not the reason to delay the project, incorrect planning and unreasonable expectations are the culprit.

Myth # 10: "automated testers don't have to worry about manual testing."

Nothing is more incredible than this.

Automated testing is also a test, and the difference lies in the way it is tested. Don't forget that automated testing continues or follows the process of manual testing. Not all projects are automation projects, and similarly, it is rare for testers to master both manual and automated testing.

Manual testing is a basic skill that testers need to cultivate, and it is the foundation. Automated testing is very powerful, and it is the most magical thing in the field of quality control. However, in the field of software testing, we are not willing to evaluate which one is better or worse.

Automated testers can do manual testing in some projects, and manual testers can also do automated testing in some cases.

Misunderstanding 11: "the test supervisor does not participate in the test."

In fact, by industry standards, test supervisors do only 10% of their coordination work, and they are also members of the QA team and are responsible for assisting in testing activities. Of course, there are other tasks.

As a result, QA executives must devote a small portion of their energy to testing activities. To become a tester, you must be prepared to perform all the tasks you should perform as an average QA team member for the rest of your career, or it's time to consider a change of domain.

Myth 12: "testers question everything and are known to be 'picky' in the IT industry."

The life of those who doubt everything is the hardest. If we really doubt everything, we may even question the existence, use, and efficiency of the software, which means that we are still working on the product when we believe that it is useless.

Do you think this view is correct? Can we really spend a lot of time on a software system and think it's useless? The author doesn't think so.

Contrary to popular belief, testers believe in the performance, efficiency, productivity, and use of software and help it succeed in practice.

However, testers need to make sure that the software is at its best. When testing, keep in mind that the product is excellent and we must identify and eliminate any factors that may have a negative impact on this excellent product. We really recognize it and are loyal fans of it.

At this point, I believe you have a deeper understanding of "what are the misunderstandings about software testing?" you might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.