ESRI JS Promise never resolves in intern tests

Test that include an ESRI JS Promise never resolves in intern tests and test fails with the following error:

TimeoutError: Timeout reached on chrome 75.0.3770.100 on Mac OS X - widgets/App/AppViewModel - should resolve ESRI Promise#
      @ node_modules/intern/browser/remote.js:99:10665  

Description

ESRI JS Promise never resolves but “classic” one does resolve and test succeed. For example, in any test suite add the following sample:

import esriRequest from "esri/request";

test("should resolve ESRI Promise", async () => {
      return esriRequest('https://services.arcgisonline.com/arcgis/rest/services?f=json', {
        responseType: "json"
      }).then(function(response:any){
        assert.equal(response.data.currentVersion, '10.6');
      });
});

 test("should resolve a Promise", () => {
      function solvePromise(resolve:any, reject:any) {
        const req = new XMLHttpRequest();
        req.onreadystatechange = function(event) {
            if (this.readyState === XMLHttpRequest.DONE) {
                if (this.status === 200) {
                    resolve(this.responseText);
                }
            }
        };
        req.open('GET', 'https://services.arcgisonline.com/arcgis/rest/services?f=json', true);
        req.send(null);
      }

      var promise = new Promise(solvePromise);
      return promise.then(function(value:string) {
        assert.equal(JSON.parse(value).currentVersion, '10.6');
      });
});

Test ‘should resolve ESRI Promise’ never resolve and fails with a timeout error but ‘should resolve a Promise’ does resolve and test succeeds.

Expected Behavior

ESRI JS Promise should resolve in intern tests and test should be successful.

Actual Behavior

ESRI JS Promise never resolves in intern test and test fails.

Possible Fix

No idea

Steps to Reproduce

1. Include import esriRequest from "esri/request"; in any test suite
2. Copy paste the 2 tests described above
3. Run npm test

Context

I cannot test any function that returns an ESRI JS Promise

Your Environment

• Version used: 4.11.0
• Browser Name and version: Chrome Version 75.0.3770.100

Any idea @odoe ? Thanks !

[Biboba]

@jason0x43 found the trick ! In webpack test config, output.publicPath should be set to ‘/~tmp/’.

[Biboba]

Reading this post, I now understand why you wanted to wait for 4.12: nativ fetch will be used so my test might be successful. But I think the issue would still occur whenever a test will be executing ESRI JS code that will be doing a dynamic import just like “esri/request” is 4.11. Let’s see what see what the open issue on intern will say.