On 3/20/08, Stepan Mishura <[EMAIL PROTECTED]> wrote: <SNIP> > > But you missed my point - usually (not this particular case) there are
s/not/not only/ -Stepan. > dozens of commits between build breakage and its recovery. IMHO that > definitely means that people don't pay attention to alerts and don't > look at the integrity page. > Also it may mean that: > - commits are not monitored (IOW, the last/fresh code from repository > is not used) > - unit tests are not run > - regressions are not evaluated early. > (The last two points are nightmare for QA engineer :-)) > > Seriously speaking, I think we established good (not perfect, but > anyway I do believe it is good) testing process to assists developer. > Say, a developer doesn't need to run all suites included into > integrity testing on all platforms. She/he may run only selected tests > (I assume that most of developers test changes in this way) on couple > of platforms(Linux/Windows) and if everything pass then changes are > committed. And she/he have opportunity to see all tests results on all > platforms pretty soon(~5 hours). Wow! > ... and what are reasons to ignore such opportunity? > > Thanks, > Stepan. > > > Regards, > > Tim > > > > >
