Posts

AngularFire / Protractor: a solution to the famous ScriptTimeoutError error message

Image
As part of the development of ionic application 4 / Angular 6 / AngularFire2, specifically the e2e tests, I turned round for more than 24 hours, following a mysterious behavior of the test environment that crashed on error messages: ScriptTimeoutError: script timeout: result was not received in 11 seconds. I worked hard on the protractor.conf.js configuration file and on the .steps.ts files by trying several possible combinations: When ( / ^ User click on the button " ([^ " ] * ) " $ / ,  async  ( id )  =>  {    await   element ( by . id ( id )). click (); }); When ( / ^ User click on the button " ([^ " ] * ) " $ / ,  function ( id : string ,  callback ){    element ( by . id ( id )). click (). then ( callback ); }); but no light at the end of the tunnel. Until I come across a discussion on github ( https://github.com/angular/angularfire2/issues/225 ) where I discover that the problem comes from the AngularFirestore that

AngularFire / Protractor : une solution au fameux message d'erreur ScriptTimeoutError

Image
Dans le cadre du développement d'une application ionic 4 / Angular 6 /  AngularFire2 , et plus précisément les tests e2e , j'ai tourné en ronds pendant plus de 24 h, suite à un comportement mystérieux de l'environnement de test qui se bloquait sur des messages d’erreur:  ScriptTimeoutError: script timeout: result was not received in 11 seconds.   Je me suis acharné sur le fichier de configuration protractor.conf.js et sur les fichiers .steps.ts en essayant plusieurs combinaisons possibles: When ( / ^ User click on the button " ([^ " ] * ) " $ / , async ( id ) => {    await element ( by . id ( id )). click (); }); When ( / ^ User click on the button " ([^ " ] * ) " $ / , function ( id : string , callback ){    element ( by . id ( id )). click (). then ( callback ); }); mais pas de lumière à la fin du tunnel. Jusqu'à ce que je tombe sur une discussion sur github   ( https://github.com/angular/angularfire