It has been almost 5 months since the work was transferred to the maintenance test group a few years ago. Begin to have a general understanding of the job responsibilities and work content of maintenance testing. At the same time, I am also thinking about the value of maintenance testing to the product, the organizational structure of the department
The position of the maintenance test team, the core of the maintenance test work, and set their own skills requirements for the maintenance test team, including business ability, technical ability, communication ability, etc. The following is a brief description of my personal views from several aspects.
What is maintenance testing
Maintenance testing is the testing in the maintenance phase after the software product is released, that is, in the product GA (global release) ~ EOS phase. The following is the software testing life cycle diagram - the correspondence between IPD and PTM stages:
Abbreviations explained: GA (Global Release), EOP (Out of Production), EOM (Out of Maintenance), EOS (Out of Service)
(Charter~GA) Requirements testing at this stage, what is the difference between it and maintenance testing?
1. Version startup entry: Demand testing is driven by on-site research and customer needs, maintenance testing is based on existing network problem sheets, and a small number of patches will be incorporated into the requirements.
2. Workload: The overall test workload of the requirement test will be larger, and it will be released with the requirement version number. Maintenance tests are mainly released in patch versions, which are released in the form of patch versions.
3. Deliverables: Requirements testing is a function, and maintenance testing is a bug fix. Both include data.
Responsibilities and content of maintenance tests
Maintenance testing responsibilities, individuals do not see job responsibilities specifically for maintenance testing. According to personal understanding, they should include but are not limited to the following:
1. Responsible for maintaining the stability of the existing network operation products and providing effective solutions.
2. Responsible for supporting the answering and analysis of current front-line and customer business problems.
3. Responsible for all aspects of patch version testing, including tool verification provided to the front-line.
4. Responsible for the verification of the existing network operation instructions to ensure that there are no accidents caused by the existing network operation.
The contents of maintenance testing work include but are not limited to the following:
1. Responsible for patch version testing, including problem ticket and requirement analysis, test plan and use case design, and test execution.
2. Responsible for the verification of the existing network operation instructions. Including patch upgrade, platform upgrade, cutover test, mirror test operation instructions and other verifications,
3. Quickly reproduce and analyze existing network problems, track and verify problem solutions.
4. Quickly respond to front-line and customer questions about business and operation.
The summary is : testing patches, testing upgrades, reproducing existing network problems, and existing network support. According to the characteristics and test requirements of the current product, the work content is further detailed:
Patch version test: As mentioned above, the test content of the patch version is mainly the issue sheet. There are several types of issue sheets incorporated into the patch: new development, synchronization sheets, requirements, and data sheets, which need to be tested and designed. execute
Row. The other part is routine quality assurance testing, including ATP use case execution, automated factory use case batch running, code coverage scanning, memory leak scanning and testing of peripheral supporting products (fixed interfaces), as well as different patches
Validation of the upgrade path. The quality requirements for patch version release are that no known defects can be released, and no new problems can be introduced when going online.
Upgrade verification test: The upgrade verification work occupies a considerable proportion in the current work content, and there are various upgrade verification and cutover tests. Therefore, the project team has also accumulated a lot of experience and solidified it into specification documents, work
tools to ensure the quality and efficiency of upgrade verification. Before verifying the upgrade, be sure to read the upgrade specification carefully to understand the preparation before the upgrade, operations and observation points in the upgrade process, process data collection, post-upgrade inspections and use case verification, return
Back and so on. Must conform to specifications.
Recurrence, analysis, and answering of existing network problems: The location analysis of existing network problems is usually completed in cooperation with development. The test should ensure that the existing network environment is quickly built, the scene reproduction is completed, the familiarity with various test tools and analysis methods, and the communication with customers must be ensured.
Skill Requirements for Maintenance Testing
Compared with the requirement test, the maintenance test must directly face the existing network problems, and the existing network problems usually have several characteristics: the business form is uncertain, the problem is difficult to reproduce, and the triggering problems occur widely. So for maintenance testers
The requirements of the staff are to have a wider range of business familiarity, more comprehensive skills, strong problem analysis ability, and high problem-solving ability. That is to say, to be all-rounder, but to be all-rounder means not to be proficient. Specifically how to do it for the project team and for your own development
More favorable, you can weigh and think about it. From the perspective of personal development, it can be considered from the two directions of business and technology. If it is a business type, you should be familiar with the business, not only limited to a certain requirement and a certain feature. if technology
If you are a type, you should polish your coding ability, basic ability (OS, network, database), problem analysis ability, etc.