What does the pain spot that software checks have?

What does the pain spot that software checks have?

From the test integral angle analyses:

The first pain spot is an introduction easy development is difficult. A lot of people think to check also so return a responsibility, actually otherwise. The test needs very solid technology strength and very comprehensive knowledge to lay in. Be in abroad, the technology is below a lot of circumstances big ox transition does a test, and in home criterion unluckily contrary.

The 2nd pain spot is value is reflected. Product branch defines a product, those who do is user analysis and demand affirm, affirm otherwise to should be done; Department of research and development creates a product, this is from 0 to a phase of 1, affirm can do; What is checking a branch? Is checking a branch product of test and verify? Can be the product that monitor used? Other still? From objective angle for, the value of the test by be underestimated badly and misunderstand, the value output that a lot of people feel to check personnel to offer is insufficient. the understanding with respect to me, the basic value of the test assures quality namely, this is the lifeline that tests a person, also be the basiccest value is reflected. Extend value for, the test can be assisted optimize the flow of research and development and efficiency, efficiency that improves consign and carry dimension, abidance that is a product to improve offer proposal and support to wait a moment, the business that can do is very much. Because check a person to be familiar with a product most, understand an user most, most system of understanding research and development, this is the advantage that tests a person.

The 3rd pain spot is do not know the system still has how many drawback forever. This world is such, we have rife uncharted territory. To the product of development, we do not know to still have drawback forever likewise, so called quality also is of relative to character very. We cannot end checks, cannot define quality directly more, can be based on certain level and test method to judge the qualification with whether true product only.

The 4th pain spot is with personnel of research and development " quarrel " . Because located position is different, the circumstance that checks personnel and personnel of research and development to produce conflict is very much. Below simple citing, the BUG that personnel of research and development thinks to check personnel to put forward has a problem, do not grant repair, test personnel thinks personnel of research and development should repair this BUG, bilateral refuse to budge does not fall, similar setting is very much.

The 5th pain spot is a test personnel is " a person adept in martial arts and given to chivalrous conduct back boiler " . In client spot the test gives an issue, the line on the system gives an issue, the first consciousness reacts even if test personnel did not test a lot of people reach the designated position, leakage is measured. To test person, in heart of this kind of misunderstanding very afflictive, hard to avoid feels he is subdued. Development staff introduces all BUG, but test personnel serves as quality " Palladium " , need guards last defense line, must be defended, defend firm, although some moment can suffer,grouse, authority is actually clear also, the essential and ongoing hair of the problem end or product end.

What does the pain spot that software checks have?

Carry out angle analysis from the test:

The first pain spot is test environment. Different test object, needs test environment can have difference, especially the equipment of soft hardware an organic whole (hardware is not stabilized or software function is complex) , perhaps say performance test, more complex with the test of the exemple, test environment to checking personnel all through the ages it is special " painful " a thing. Some moment do sth over and over again check an environment to need most day, and the test implements mere need 5 minutes, ten minutes came to an end. Check an environment it is so important to build, concerning to measure the executive quality of try out exemple directly sometimes.

The 2nd pain spot is to measure try out exemple. Those who measure try out exemple write, check those who use a base line to safeguard, different project measures try out exemple arrange, the label that measures try out exemple (importance, setting, category, whether environment of automation, test, , exceedingly important, and each job here nots allow exceedingly easy.

The 3rd pain spot is the test is analysed. The fixed position analysis that test analysis includes to check blemish, analysis that is based on blemish itself (trend graph, distributinging graph, reason graph) , the analysis with the analysis that checks executive process, analysis of product quality, politic test is waited a moment. Checking an analysis is to check the mastery of a skill or technique that in carrying out, often uses, its more is way of a kind of habit of a kind of means of a kind of thinking, job, work.

The 4th pain spot is regression checks. Returning to a test is version need in system testing the phase of a test of classics. Does recursive test refer personnel to return to the blemish that he refers by blemish after all? Be still returned to by someone else? Returning to a test after all is itself of mere regression blemish, still develop more tests with correction code around blemish? The test strategy inside this is very much. I feel we want to join test resource, project the compound decision such as flow of actual condition, test and mechanism how better develop recursive test.

The 5th pain spot is blemish reproduction. To test personnel, the reproduction of blemish especially hard the blemish of reproduction is very aggravating really. Because of those blemish itself special hard reproduction, need rife reproduction skill and method necessarily. A lot of moment, everybody can discover reproduction for a long time, but final whats come out without reproduction, for nothing do sth over and over again for a long time, still wasted a lot of energy. I feel to blemish reproduction, if inside two 3 take second place can reproduction comes out, basically calculate came to an end. Reproduction exceeds above 3 times, I do not suggest to check personnel to cost too much time to be on reproduction problem again, instead should let personnel of research and development undertake code is read with code examine and verify, seek an issue from code itself.

What does the pain spot that software checks have?

The 6th pain spot is the patch checks. If do not have off-the-peg test environment, the test of the patch is exceedingly troublesome, version of test environment, test, patch releases the metropolis such as the specification to affect the test of the patch. If did not hold continuation to become an environment, the patch checks can intense cause physical or mental suffering and trouble, build test of patch of version of environment, deploy, design to use afresh the exemple exceedingly time-consuming. I believe a lot of people can have the same feeling certainly, especially on-line blemish is exceedingly anxious.

The 7th pain spot is task butt joint. Personnel of a lot of tests can have feeling, personnel of research and development looks for test personnel to check a small module, technical support staff looks for test personnel test and verify small parts of an apparatus, supply chain personnel to look for test personnel test and verify stock, product manager looks for test personnel to check temporarily the project is waited a moment. The butt joint of all tasks, not certain and complete butt joint gives a test controller, because some are small the task, temporarily kind task likelihood looks for relevant test personnel directly, they perhaps are not do not press a road to give a shop sign of purpose; Stem from good individual to concerned to say directly occasionally; Do not know to who look for to seek a help occasionally, find check this. All we need these situations consideration, again strict task allots flow, regular also meeting has special case, test personnel must learn to be answered neatly.

Anyhow, the pain spot of the test is very much, these pain spot of above are done not have strict early or late ordinal, but the word says, which position and part do not have pain spot, if have painful then we are solved painful. The road needs to go forth, the life needs to look ahead, the job needs to advance in development. Hopeful state of mind and up the manner is our progressive motive force, want to believe the meeting is better tomorrow forever. Everybody is cheered.

未经允许不得转载:News » What does the pain spot that software checks have?