Software testing in the design of software testing tools

Platform-based software testing tools, often involving various roles, are most exposed to software test engineers and development engineers.

Communicate with users

Ordinary users complain more and offer less, but most users of software testing tools are software test engineers and development engineers.

They are generally aware of their needs and the ability to articulate clearly, have a clear value goal, a good sense of direction and situational sense, some themselves have developed excellent tools, so throughout the tool development lifecycle, they can assume more roles, participate in more processes.

Testers are involved in the demand, even in some modules of PD, participate in product development, the smooth promotion of tools is also helpful. After all, it's his own. This group of students is the first user of tools, their working mode can affect and drive a group of users.

The requirements of the designer

Test tools differ from general Internet products.

Traditional page navigation and content-oriented, testing tools content is not complex, heavy functionality and interaction.

Unlike navigation and content lists, as a management and help tool, a page usually focuses on a number of functions; every step that the tool seeks to reduce is to save the time of the engineer, and for efficiency reasons, a richer and more convenient interaction is required.

In the actual development process, most front-end problems are also in the interactive aspect. From the perspective of user feedback, the user's requirements for functionality and interactivity far outweigh the interface styles.

This requires the designer to have an understanding of the requirements of the system, including business processes, understanding of professional terminology and the purpose of each step, otherwise it is elephant.

Designers who do not understand the test have difficulty in making the interface design that meets expectations. The designer roles of such tools are generally borne by the test or development itself. The disadvantage is that the output interface is less beautiful. However, according to my experience, the people are not afraid of ugly interface, the real tools can be used to survive for a long time.

and Development communication

With regard to tool interaction, users have a lot of good suggestions and ideas, but the final implementation is on the development head. Unfortunately, good interaction is generally very time-consuming to develop. You know, to make the user experience to the extreme, so that users relaxed, development will be "suffering", to do a lot of extra work in their view of the small value of detail. Programmers have a belief that in this world, there is no code that can't be done. If he says it can't be achieved, he must not. Designers for the development of the knowledge used in the work, not to become an expert, but at least "slightly understand", it is best to have their own hands-on ability to estimate the development of investment. In this way, we can establish an equal dialogue with the development engineers, the requirements and design will not be a slight. "Yue Guang box" inside Zhuge Liang is not a line, what all understand a little, life can be more colorful.

Easy to say, practical difficult, a lot of things unless the development of their own to understand that persuasion is useless. The team is best to have a language to set the authority of the universe of characters, and the development of communication can not, to find his decision.

Tool development process, in many cases, development itself is PD, will tend to simplify the project, as far as possible to do, do their own familiar, so that the project successfully completed, and fewer bugs, may be done out of the experience is not good, but absolutely "enough."

In fact, Synergy is where you collaborate with others, rather than others to collaborate with you. Take the initiative and get more.