We have a rather huge test codebase (about 10000 lines of javascript code) and in some situations, we need to turn Protractor-to-Angular synchronization off:
browser.ignoreSynchronization = true;
But, the problem is, from time to time we forget to turn the synchronization on again making all the subsequent tests fail with unclear reasons which require time and effort to debug.
Is there a way to ensure the synchronization is turned back on in a test?
We do have static code analysis based on ESLint
and perform code reviews.
Aucun commentaire:
Enregistrer un commentaire