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

From "from a rookie to a test architect-- the growth diary of a test engineer"

Test the work of the architect

Development:

1. Participate in design discussion and document review

Practice: project team members will participate in the document review, the most basic will participate in the requirements discussion and review. In the last project team, the outline design document of R & D will also be discussed and reviewed. In the current project team, the outline design will be written at every development stage of R & D, but it will not be reviewed. Testers will not look at these outline designs if they do not need them.

Improvements:

Any document, you have to work hard to find out. The first step is to read the document, whether or not you can find the pros and cons of the design and solution, read the document, at least understand the program logic and implementation process, at least some problems can be solved in the early stage, not later. For example, if the product manager misdescribes or misses the requirements document, he can communicate with the product manager early when looking at it, instead of confirming and modifying it after the process is completed. No matter how much can be found, the cost of finding a problem in the early stage is lower than that in the later stage.

2. Participate in the review of unit test reports

Reality: at present, the white-box testing and unit testing of the project team are done by R & D colleagues, and there is no formal unit test, so there will be no unit test report.

What you can do is:

Carefully write every test report, whether you write it yourself, or your colleagues write your own inspection, you should write it carefully and check it carefully. For example, some special test programs, test reports, external test programs, external test reports and so on. Every report is practical, realistic, meaningful, meaningful and valuable.

This should have been done very well, but in the future we should think more about how to do it and how we can do it better.

3. Participate in the discussion of performance optimization architecture

Practice: performance testing is also done by the R & D colleagues of the project team.

What you can do is:

Find some information about performance testing and learn about performance testing first. Research and development can develop performance testing tools, but the design and implementation of performance testing can be done by ourselves in the future.

4. Participate in the scheme design for continuous improvement of development quality.

Reality: do not know who is doing this part of the work, there will be such a work content, but not a special work. For example, in the test release report, it will record what the continuous improvement is at each stage, and put forward some suggestions for improvement on some problems existing in the testing process at this stage. Each stage will track the improvement recommendations of the previous stage, whether it is implemented, how effective the implementation is, and what are the difficulties and problems. It is a question of full participation.

What you can do is:

As the project manager said, everyone has their own role, play their own role, do their job well. In addition, we are a team, when other people make mistakes, don't blame others, but think about what I can do to avoid such problems again. For example, in the last round of release testing, when the test expired and found that the program driver could not be installed in the winxp system, the project manager did not say that it was the tiger's problem, but that I did not find the problem in the early stage of the test. I may not have thought too much about it, and I will inadvertently talk about Xiaohu, and the project manager will pay attention to protecting Xiaohu's self-esteem.

Everyone makes mistakes, and when everyone makes mistakes, they will be willing to admit and accept possible punishment. However, they will not be willing to, because of this problem, others have been talking about it, or being criticized. I already know that I have made a mistake, but others still keep mentioning it and keep saying that it is a very uncomfortable thing. If I make a mistake myself, I will be very worried that others will always say it and bring it up consistently, because one thing, one mistake, will be framed by others. Since I don't want to be treated like this, I should be careful not to treat others like this at work.

Testing:

1. Write test strategy and overall test plan documents.

Reality: I am responsible for and complete the overall test plan.

Improvement: now the program function is less, planning, personnel arrangement, time, resources, test content are relatively easy to arrange and determine. When the program has more and more functions, think about how to do it better every time you make a plan. Why do you line up like this? is there a better arrangement? As the project manager said, there is an attitude and awareness that when you do anything, ask yourself if there is a better way.

2. Audit test plan and test case design

Reality: the test plan is being completed, the test case is being written, the test case is being designed, and it is being checked.

Improvement: nothing can be thought of for the time being.

3. Guide the construction of test automation system.

Reality: no automated testing has been introduced into the project yet.

What you can do is to plan the next release test phase and verify the installation and uninstallation of the program in an automated way. On the one hand, step by step to master automation, to contact it in order to understand it, by doing to learn.

4. Test coverage review

Reality: because it is not a large-scale software, the test coverage is 100% covered during the testing process. The review process is recorded in the test release review report.

5. Selection of testing tools

Practice: use existing testing tools.

6. Test process management

Practice: using agile development, project team R & D, testing, product, UI a total of 9 people. There are only 2 people in the test, no one is in charge, but will pay attention to the test process. Personally, I think that because of the small number of personnel, the testing process is relatively clear, and the task assignment is more reasonable. There is not much, dissatisfaction or work piling up.

7. Defect quality inspection

Reality: defects will be tracked and recorded in the release test report, and all participants will review the defect quality in the test review.

In the book, it is written about what the test architect will do, and the situation varies from company to company. Sort out what we are doing and what we are not doing according to the actual situation. If that's what a test architect does, I think what I can do before I'm a test architect is to refine my work according to what the test architect does. Therefore, what can be done in the next stage and beyond can be summarized as follows:

1. Make great efforts to read any document and figure it out.

2. all the documents that need to be completed should be completed carefully, and think about how to write better.

3. Learn automated testing and performance testing through practice

4. Attitude: don't blame yourself and your colleagues when you encounter problems. Think about what you can do to solve the problem and what you can do to avoid the same problem next time. When you do anything, ask yourself if there is a better way.

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.