Generally you can get away with not using flush. You may still need flush for testing element lifecycle callbacks in polyfilled browsers, or measuring DOM, but I expect very few cornercases like that.
On Thu, Jul 16, 2015 at 10:46 AM, <[email protected]> wrote: > With Polymer 1.0, observers are now evaluated synchronously. If I have an > element whose behavior is driven by observers on attributes, and everything > appears to work in synchronous tests, is there any reason to call flush()? > That is, is it necessary that I call it before/after each test? > > Follow Polymer on Google+: plus.google.com/107187849809354688692 > --- > You received this message because you are subscribed to the Google Groups > "Polymer" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/polymer-dev/adc4db0a-459d-4abf-ab8f-6453dae62213%40googlegroups.com > <https://groups.google.com/d/msgid/polymer-dev/adc4db0a-459d-4abf-ab8f-6453dae62213%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/CAAUAVAhtWUNOMEw8Zm2Nq5JVA0Q4ihDEtgPJ4pDjRVqZHk1ENA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
