Hi, -------- Original-Nachricht -------- > Von: Helge Delfs <[email protected]>
> > Btw. please do me a favour and contact me or the responsible engineer of > an autotest[1] directly if you encounter any problems with the tooling > in the future. Sorry - no! If we have problems with the tooling, all qa-members need to be aware of this. Or each member will run into the same problems. Furthermore - if we do not report the problems we will go on in the "all is fine" mood. > This problem was solved within minutes and I think it's > not worth to challenge the whole tooling as it works in majority of > cases ( I would say 99%) . And 1% failure might be critical if this hits stopper bugs. > This does not help and unsettles the > community members working with this tooling. Furthermore those problems > had already been identified (#100235) and meanwhile fixed in CWS sw31fb08. This is not the point - or it even proves that we find stoppers much to late due to several shortcomings in our processes. In theory all was fine: automation team corerctly prepared the testscripts, run the tests and VCLTesttool was able to identify the problem. If we had localized builds much earlier and if the results had ben analyzed correctly we could have prevented one of the very late stopper reports. (I'd guess the issue has been introduced months ago). André -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
