On a very fast system (high clock speed, since multicore doesn't help Flex), running Windows (fastest FlashPlayer) they take about 18 minutes to complete. On lower clockspeed Linux systems they take about 25 or so. That's why TeamCity, with its remote run feature, was so important to our team; it let us offload that test time onto our build infrastructure instead of waiting for it on our local PCs. On Oct 5, 2011 2:09 PM, "velo" <[email protected]> wrote: > Wow! how much time does it take to run all your tests? > > On Oct 5, 12:29 pm, Bryan Turner <[email protected]> wrote: >> We started with a test timeout of 20000, and as we get even more complicated >> tests we had to increase it again to 30000. The speed of the hardware >> running the tests also comes into play, here. We used JetBrains TeamCity for >> CI, and some of our build agents were faster than others. The faster agents >> were able to run successfully with a lower timeout, but the slower ones >> needed it to be longer or the build would randomly fail. > > -- > You received this message because you are subscribed to the Google > Groups "Flex Mojos" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/flex-mojos > > http://flexmojos.sonatype.org/
-- You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos http://flexmojos.sonatype.org/
