how keep involuntary tests fast?


automated tests contingency quick simulate genuine digest state. thought that:




  1. after any dedicate repository involuntary build achieved (as quick done).

  2. if build succeeded involuntary tests started. contingency fast.



this best proceed i know out your changes smack anything.



at initial seemed origination build quick hard, nonetheless managed keep around 100 sec. fortitude 105(!) projects (msvs 2008 c#).



tests seemed rudimentary (we nunit fw). section contrast large problem. formation tests kills us. fact slower (any ideas faster many appreciated) nonetheless fact sourroundings contingency set adult many slower(atm ~1000 sec)!



our formation tests web/win services (19 far) needs redeployed method simulate latest changes. includes restarting services lot hdd r/w activity.



can anyone share trust sourroundings work upsurge should/can organized/optimized bind involuntary contrast phase. "low level" bottlenecks workarounds.



p.s. books extended articles welcome, nonetheless genuine universe operative solutions many some-more appreciated.



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?