Re: Long running test suite
"Tim Ottinger [email protected] [testdrivendevelopment]" <[email protected]> Mon, 23 May 2016 19:41:55 +0000
| Newsgroups | gmane.comp.programming.test-driven-development |
|---|---|
| Message-ID | <CAN2NSt=dwKRLo-5jaHefw5nCg7yfS_3MtKO+hZNQORXsy9uyZg@mail.gmail.com> |
Empty out the integration and up tests and sub in more microtests. On Mon, May 23, 2016, 12:15 'Niklas Bergkvist' [email protected] [testdrivendevelopment] <[email protected]> wrote: > > > Hi, > > I'd say you have a good opportunity for refacoring! If your tests cover > your functionality; go a head and refactor into smaller functional units. > > good luck! > /niklasb > > > <-----Ursprungligt Meddelande-----> > *From: Joselito D Moreno [email protected] <[email protected]> > [testdrivendevelopment] [[email protected] > <[email protected]>]* > Sent: 23/5/2016 5:25:11 AM > To: [email protected] > Subject: [TDD] Long running test suite > > > > > Hello, > > To those who have experienced test suites that run long, say ~25 minutes, > what are some techniques you have used to mitigate it? We still would like > to be able to check in often and run the test suites prior to checking our > code in to our repository but these long running tests makes us stretch > what we mean with "often". > > Joen > > > > >