This is great, thank you!
On 19/05/2016 7:09 PM, Matthew N. wrote:
> Hello,
>
> One of the reasons developers have been avoiding pushPrefEnv compared to
> the synchronous set*Pref (with a registerCleanupFunction) is because
> pushPrefEnv required using a callback function to wait for the
> prefer
On Thu, May 19, 2016, at 07:09 PM, Matthew N. wrote:
> Hello,
>
> One of the reasons developers have been avoiding pushPrefEnv compared to
> the synchronous set*Pref (with a registerCleanupFunction) is because
> pushPrefEnv required using a callback function to wait for the
> preference change
On Thu, May 19, 2016 at 4:09 PM, Matthew N. wrote:
> As a reminder, the nice thing about pushPrefEnv is that the pref changes
> are reverted at the end of the test file which avoids them leaking into
> other tests unintentionally.
>
Another good thing about it is that set*Pref isn't actually syn
Hello,
One of the reasons developers have been avoiding pushPrefEnv compared to
the synchronous set*Pref (with a registerCleanupFunction) is because
pushPrefEnv required using a callback function to wait for the
preference change before moving on in the test file. This can make the
test flow
4 matches
Mail list logo