Today's article is some of the problems small partner counseling a new entry, the problem a bit more, so into the second reply, solve these problems, the king Peas think it suits joined the line, has not had the software test deep understanding of small partners to learn, Share it out, study together for discussion.
Q1. Generally the size of the company, technical department organizational structure what is it?
Several test? Several developers? Several front-end?
A: Each company's organizational structure is different, some companies are divided by product, but also by the departments of points, but also mixing points, the most simple Internet company organizational structure as an example:
Behind the three general groups, small companies are mostly based on the internal workings of responsibility points, slightly larger companies according to the number of testers, according to business will be divided into finer or other characteristics.
How much each company test, how many developers are not fixed, but there is a certain percentage, such as a test of the three developers, known as 3: 1, the level of this ratio depends on the decision of the leadership of the company, in general, if development and testing ratio of 5: 1, overtime will be relatively serious, but there are exceptions, such as our company has developed a test ratio of 2: 1, every day is busy dancing, because demand update too fast, too much return to the scene.
. Q2 general corporate project 1. Analysis of the requirements document from needs assessment -3 -2 writing test plans. - Program Evaluation and Review - written test - Use Cases Review - execute test cases - iteration. . . Such a process, and that if they go into the company, 1-3 at this stage has passed, as new entrants testers, writing test cases directly from the start it?
A: When the company which the entire testing process is a cycle, and do not have to miss the previous needs analysis, review and other steps to worry about, if that is the worry, it is best from project approval, product demo began to intervene, so that to witness a project from a new product, but the reality is that the company does not begin to develop new products, nor will you arrange a new project, unless itself is so recruitment requirements.
When it comes to companies just entering what do you do for general distribution to give you some new things simple and approachable, familiar with the pre-project business - "allocate some less important regression testing -" and do it with old colleagues Some projects, undertake less important functional test - "independent start with a simple and small project started -" independently undertake larger projects, basically in accordance with such a beginning of a gradual process, for newcomers, a leaders will not start allocating too important thing to you, do things slowly arrangements will be based on risk considerations.
Q3. A project cycle is about how long? We need to iterate several times it? Iteration time, testers usually do it?
A: Each company is different project cycle, the length of the project cycle also vary according to the size of the project, a small project cycle naturally short, big or strong expansion project cycle is very long, there are twelve short month long there are more than seven years (depending on the project which is derived from his past, beginning 12 years, are still doing).
According to the different periods of the project, the number of iterations is different, that project iterations before we basically do is press a month iterations, and faster iterations have seen the project.
An iterative process is a basic test, the tester in the testing process needs to be done, we will do a basic iteration. Detailed information is visible, "I wrote the test process of dismantling the testing process ," the article
Q4. Testing of the day, it looks like? Almost it is not a work day, have to write test cases in Zen trail, mentioning that bug. After confirming a bug, it is to develop and belongs to mention, or mention it one by one?
A: work content testers day progress of the project is to decide what to do today, there are likely to be familiar with the requirements, there may be a write test cases, there may be executed testing.
Overall, the testers work content is inseparable issues involved in the testing process.
Write test cases or bug is not necessary to mention in Zen trail, writing test cases or bug put on what tools? It is usually determined according to the company's requirements or personal habits.
In performing the test, generally a bug is found in submitting a bug defect management tools, defect management tool if not used, is generally found to inform developers on instant messaging, but this is not recommended , testers found bug, tracking bug, there is a trace can be traced as far as possible, be traced to facilitate testing and statistical analysis of late, it is also necessary to facilitate future inquiries.
Specific content can be found in my book, " software testers daily work routine ."
Q5. Project work need to do performance testing, who proposed it? Is the customer? Or test leader?
As well as projects which features need to do performance testing, which does not need to decide is how it? Leader or required?
A: To address this issue, whether it is performance testing or automated testing, and we will not for a particular function to do these special tests, in general, will be based on the entire system functions and business needs to consider, but most companies on performance and less stringent requirements, but to focus more than automated testing performance testing. This refers to performance testing means the professional performance tests do, in fact, will also include a portion of the performance test in our usual function tests, such as a function of the length of time of submission system, memory leaks caused by slow, or even crashes.
In general companies really need to do performance testing when the user is generally the amount of data reaches a certain size will start, we are not only specific to dozens, hundreds of users to specialize in performance testing, especially some management background a limited number of users, or internal personnel, Ren Ren passed.
If you need to do performance testing, general products mentioned in the product demand will have on the performance of certain estimates, the number is expected to reach certain performance indicators, and testers will be pressure on these performance indicators measured during the test, to determine performance metrics whether it expected.
So raised as to whether to do performance testing is generally the product, if the product is to help customers to do, of course, customers also have the power to mention, if the product is independent, of course, the boss will often make demands for performance, but should be judged according to the specific situation whether to do performance testing, a product is assumed that the user only a fixed number of little people, products generally do not like to do.