Q1: What is backtesting?
A: In the new version, all features on a version tested and re-tested again
Q2: Why do backtesting
A: 1. the original function may have an impact because the new version added new features bring new BUG
2. There may solve the BUG may create new problems, so regression testing of the original function, if you use an automated manner for regression testing, more efficient
Q3: process bug reports (life cycle)?
A: new → open → fixed → closed
Q4: BUG priority factors that influence the development of what?
Answer: 1. The severity of the defect, the more serious defects, the higher the priority,
2. Development pressure developers, development pressure, the higher the priority
3. The scope of the defect, the greater the impact range, the higher the priority
4. address the shortcomings of cost, time or money, the lower the cost, the higher the priority
Q5; the severity of the defect and the priority is strictly proportional to it?
A: No, for example: interface typos, low severity, but a high priority
Q6: After determining the severity and priority defects, whether you can modify?
A: You can not modify determining the severity of the priority development side but often modified, usually later postponed (delay)
Q7: In the version of the software release, whether there may be discovered but did not solve the BUG?
A: There may have this kind of BUG, for such defects, defects are usually open to discussion, weigh the cost of solving the BUG, BUG and not resolved whether the user will have a significant impact, or to bear the legal consequences of litigation before determine,
BUG class in the way the company will release software upgrade version or patch to give to solve