Chapter 3 software evaluator’s guide
Software reviewers play an important role in software development projects. Microsoft’s software development, is a developer for two software testers, the importance of software evaluation division can be seen. Of course, this is the practice of large companies. In small companies, software engineers and software designers are often required to participate in some basic tests or participate in system integration tests at the later stage. However, software reviewers are more than just testing. They can scan code, perform white-box testing, and influence the work of developers as well. As a result, good software reviewers sometimes come from software engineers or software designers.
3.1 Job Responsibilities
The job of software reviewer is not so easy, he needs a lot of patience, perseverance. In the work, it is often some repetitive work, so, the work of software evaluation division is more tedious. However, the job of a software reviewer is to make the software run flawlessly, and even minor problems should be found and solved by software engineers and software designers.
The responsibilities of software reviewers are as follows:
L Participate in software test writing test cases;
L Familiar with software engineering knowledge, understand software development methods and processes;
L Familiar with software quality and basic knowledge of software quality management;
L Master software testing techniques and methods;
Master software testing project management knowledge;
Familiar with software testing standards;
L Participate in software unit testing;
L Participate in software integration testing;
L Participate in software system testing;
L Participate in software testing including white box and black box testing;
The purpose of the job responsibility of the software reviewer is to make the software reviewer have relevant industry knowledge, better find bugs and other problems in the process of software development, and better serve the software developed by software engineers and software designers.
3.2. Knowledge required
Software reviewers don’t need a lot of knowledge, but it’s worth learning something else for the sake of industry domain knowledge. Here is a brief description of some of the industry domain knowledge that software reviewers need.
L Familiar with basic knowledge of computer;
L Familiar with basic knowledge of operating system, database, middleware and programming language;
L Familiar with basic knowledge of computer network;
L Familiar with software engineering knowledge, understand software development methods and processes;
L Familiar with software quality and basic knowledge of software quality management;
Familiar with software testing standards;
L Master software testing techniques and methods;
Master software testing project management knowledge;
L Master C language and C ++ or Java language programming skills;
L Basic knowledge of informatization and information security;
L Familiar with laws and regulations related to intellectual property;
L Read and understand relevant English materials.
3.3. Daily work
The daily work of software evaluators is tedious and basically repetitive. Although there are automated software testing software now, some test contents still need to be tested manually by software evaluators. Especially for some large systems, automated tests also need to be carried out manually.
L Write test cases for the software system to be tested;
L Unit test the software system to be tested;
L Conduct integration testing of the software system to be tested;
L System testing of the software system to be tested;
L White-box and black-box testing of the software system to be tested;
L Perform automated software testing for the software system to be tested;
3.4 methods of experience promotion
There are also few ways for software reviewers to improve their experience. Because of the simple, repetitive and tedious work, software reviewers often need to learn by themselves to improve their experience, such as obtaining test methods and automated test methods from websites. For example, the website www.51testing.com in China is a good place for software testing to improve experience.
At present, domestic attention to the field of software testing is not very high, leading to some of the domestic software testing in the field of some testing methods are relatively outdated, often just to some software testing basic methods and automatic testing to do some introduction is basically completed, so software testing in the domestic field still need to continue to improve.
Testing itself is divided into hardware testing and software testing, we only talk about software testing content here. The author once searched the domestic test magazine, also have several, specific we can go searching, but the level of these magazines are intermingled, some will also drop bimonthly for monthly, visible domestic software test level still needs to be improved.
3.5. Communication with other roles
Software reviewers do not have much communication with other roles in the project team. One is to hand over test bugs to software engineers and software designers to deal with; the other is to be responsible to the project manager to submit test reports.
1) Communication with software engineers and software designers. In the project, the software reviewer should submit the tested bugs to the software engineer for modification, and also check part of the software engineer’s code to see if there are any problems in the unit test.
2) Communication with the project manager. Software reviewers need to submit test reports to the project manager for review so that the project manager can know who has the most bugs and who needs to work on coding. The project manager can also get a rough idea of who is doing the best testing.
3.6. Books to Read
As the level of software testing is uneven in China, software reviewers do not have many books to read.
1) Software reviewer tutorial. Written by the soft test group of teachers, a good interpretation of the definition of domestic software testing, standards, quality and testing method cases and so on, is a software testing learning tutorial.
2) Chinese Software Testing Journal. Chinese software Test Manager alliance magazine, some of the current software testing content is explained.
3) 3) 51 Test world. The magazine launched by 51TESTING website, one of the most valuable magazines in China, is more about the theoretical aspects of software testing starting from the actual software testing.
3.7 words to bear in mind
1) Be careful and meticulous;
2) Never let go of a BUG;
3) Be sure to write test cases;
4) If possible, please use automated test tools, combined with manual test;