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

The creation and use of tools, as well as the creation and use of methods, is one of the remarkable features that distinguish human beings from other animals. However, our university education often only focuses on the dissemination of knowledge, neglecting the education of tools and methodology. Here I would like to summarize the tool platform and related processes and methods needed by the IT industry testing department.

= the tool platform that the test department needs to build =

* defect tracking platform

Defects, namely bug, also known as MR (Modify Requirement), are the most direct manifestation of the results of the daily work of test engineers. When submitting a bug, it is logical and clear that a smooth narrative is the most important, which is a bit like writing a narrative, with time, place, character, cause and result. Common defect tracking platforms are Bugzilla,Clearquest,Jira,Redmine and so on. General defect tracking platforms will provide project management, version management, module management, automatic Email notification, rights management, custom parameters and other functions. I think a good defect tracking platform should be simple, intuitive, fast and easy to use. It would be even better if you could provide sorting, summarization, and graphics. As the most important interface between the test team and other teams, the defect management platform should be integrated into the overall IT environment of the company. IT department needs to ensure the convenience of team access in order to promote the efficiency of communication between teams. If a product manager does not care about the defects of the product, he is not a qualified product manager.

* knowledge management platform

The knowledge management platform is used to share product knowledge and experience within and between teams. The turnover rate of staff in IT industry is notoriously high, so a good knowledge management platform is very necessary for the healthy growth of the team. Due to its convenient update function, Wiki can keep articles often new, so it has almost become a standard platform for knowledge sharing, and can completely eliminate forums, SVN and other tools. On a knowledge management platform with a certain accumulation, almost everyone in the upstream and downstream of the product can benefit from it, from the market to R & D. Common Wiki tools include Mediawiki,Confluence and so on.

* Automated test platform

Automated testing is very important for code refactoring and regression testing between versions. It can be said that the rise of agile development model is entirely due to the Open and progress of automated testing technology. Especially for a product with a long life cycle and more versions, automated testing is a very important firewall. The essence of automated testing is to test software, so it needs to be treated in the way of software engineering. Almost all programming languages have their own xUnit automated testing framework, but it should be noted that not only unit testing can do automation, IT,SIT, SVT stages can do automation, need to choose automated testing methods in different stages of the product according to the characteristics of the product.

* explore the test platform

Many test engineers will find that sometimes the bug found by spec and plan is not as good as divergence test and exploration test, so it is necessary to explore the test platform. Exploring the test platform should be a tool platform to solve the simulation problems of the test environment, and it is necessary to continuously add applicable and useful tools to the platform. Exploring the test platform should form a good interaction with the automated test platform, and the good tools should be continuously introduced into the automated test platform.

* continuous integration platform

The construction of continuous integration platform can greatly improve the efficiency of the software release process and reduce human errors. The goal of continuous integration is faster, more comprehensive, and more intuitive. Code checkout, compilation, release, deployment, testing, reporting, each step has a huge room for efficiency improvement, automation of everything. Common continuous integration platforms include Jenkins/Hudson,CruiseControl,Bamboo and so on. Software changes the world, tools change the world.

* accessibility platform

The assistive tool platform is used to assist test engineers in their daily work, such as use case design, document inspection, time planning, mail processing, IM, screenshot tools, etc. Teams should try to use the same set of tools and follow the same configuration to reduce unnecessary communication and misunderstandings

* version management platform

Scripts, documents and tools should be versioned. Git is recommended by individuals. Compared with Svn, there are fewer .svn folders and copy is much more convenient.

* use case management platform

With the growing size of the team and the increasing number of use cases and versions, it is very necessary to build a use case management platform. Common use case management platforms include testlink,testcenter, etc., but the range of options is relatively small. Compared with the strong stability and ease of use of Excel, it is not recommended to write use cases directly on the test management platform, endless trouble, it is best to use an auxiliary import tool from Excel use case documents to the use case management platform.

= the process required for the daily work of the testing department =

* Task decomposition process

Einstein said, to do complex things simply, I understand that the meaning is to decompose. The characteristic of modern society is that the division of labor is more detailed, and the team with 1: 1 > > 2 is the excellent team. Therefore, it is one of the magic weapons for Huawei team to set up a hierarchical team of experts to show their strengths to ensure that everyone can shine to the greatest extent regardless of their skills and experience.

* defect handling process

The resources of each team are limited, and most of the time we can't release the product until all the defects have been solved, so how to deal with and evaluate the defects is related to the product as a whole, which will involve the market, R & D, testing and other teams. need a clear process to ensure

* Product release process

Before the product release, it is usually necessary to make sure that all the risks have been avoided, that all the relevant data manuals are complete, and that the final version matches the requirements, which also involves many departments and links of the company. Product release should establish a set of strong process specifications to coordinate the sequence of work between different teams.

* use case and script maintenance process

One of the ideas of agile development is to pay attention to the communication of documents, because it is very troublesome to maintain the state of documents that are always new, how to ensure the consistency of use cases and scripts, and how to ensure the closed loop of online problems. these are all problems that the test team needs to pay attention to, so it is necessary to operate under a unified process.

* New employee training process

For the training of new employees, we must establish a series of clear goals, which tools, templates, processes and resources we need to master. If we do a good training plan and process in advance, we can save a lot of things.

* Review process of the document

Documents are the output that can best reflect the professional literacy of engineers, logic and language are things that need to be trained to master, documents without Review are substandard documents, the Review process can be checked to fill gaps, but also a unified caliber. For the documents output by the testing department, we should specify when and who uses what method to Review, where to come from, and where to go, which should have a clear process and system to ensure.

* work status reporting and follow-up process

Weekly newspapers, daily newspapers, key tasks, Gantt charts, milestones, all these things are used to become a habit.

= commonly used templates in the test department =

* Test case templates, plan / requirements / report templates

* Weekly / Daily / Task tracking template

= things to pay attention to =

# the construction of these platforms and processes is not just for the testing department, but should be integrated into the company's overall IT environment as far as possible, such as Email system, identity management and so on. SSO single sign-on is the best way to avoid jumping between a bunch of passwords.

# attention needs to be paid to the training of new employees to ensure that everyone can use the complete set of tools in the right way

# to borrow the words of Boss Ren (Zhengfei): professionalization is standardization, formalization, templating, data and flow.

Any work should be a process of continuous optimization and continuous improvement, dogma is bad, to borrow the Agile Manifesto: people-oriented. Then to borrow the words of Boss Ren: first ossification, then optimization.

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.