It doesn't necessarily follow.
I don't know what is "Mathon debug version blood event", but if use the proper policy, the debug version would contribute the trail of some damn bug and no ...
Thx your advice .thats right, with the development of the internet,plenty of websites become so complex and some of frameworks maybe not fit the normal.how to improve the stability and reliability of theworld browser becomes more and more significant.I always think that the phoenix studio devote themselvs 2 analyze the reliability of the browser with study of test process and testing tools is so hard .U know,2 the developer ,finding the bugs how 2 entered the developprogress and testing why the error impossible to defend effectively on ocassion.
As a developer,u should c thats NOT the certain particular error,the developers take part in the progress lacked communication of cz not evasion. As a result,many guys thought that put the dugversion will get the user done once and for ever .Its the final methods of software reliability and its strategic apply in browser quality assurance are summarized importantly.At the present time,establishing the unobstructed communication channel in the development personnel and the common user should be become the plan stage as a part. At present developing the group should emphasis to put in participates in the application procedure development, the user should cooperation eachohter , this certainly not mean had to use thespecial-purpose procedure to test promotes the quality,just forms a ring circuit 2 put in the bugs.germination, refined management, constructs with the transformation is the inevitable process in the software develops, bless our browser.
发表于 2007-4-20 13:30
| 
发表于 2007-4-20 13:48
| 