Home > other >  How to efficiently reduce the unknown defect after the release
How to efficiently reduce the unknown defect after the release

Time:12-24

Today. Bad defects after release, the function has three or four versions without modification code, not as a test point to test during testing, the end user found that the defects, lead to think!
First think of the automated regression testing, but regular function and version changes, the front-end UI automation maintenance requires a lot of time, this is the boss clearly feel unworthy,

In addition to each iteration release to return all functions, there is no other way to? Can high efficiency low cost to avoid this kind of phenomenon?
  • Related