The job mwext-WikibaseJavaScriptApi-qunit was overridden some time ago to run composer and thus working.
Do you mean the job mwext-WikibaseJavaScriptApi-testextension-zend job which should be made to run the resource tests from core?

There is now a generic job for phpunit that runs composer. We should be able to just use that as is for this repo.
Also the custom qunit job for this repo can be replaced with the generic composer qunit job.

Now that I said that I remember that this repo is actually more like a composer component than a Mediawiki extension, see T109171 for the details. But for now it should work in CI as an extension as it has an entry point.

Would using the composer-test test work.

If this were a normal php composer component, that were the way to go. But this is a javascript library that depends on ResourceLoader packaged as a composer component. So its primary CI need is running qunit tests, the secondary one is running the tests from core that check ResourceLoader definitions which are run during the phpunit extension test suite. So, no I meant using the jobs mwext-testextension-zend-composer, mwext-testextension-hhvm-composer instead of their non composer variant.

So all that needs to be added is

mwext-testextension-zend-composer

and

mwext-testextension-hhvm-composer

test would that require a new template with both of those test or how can you use them in ci file since template: only works for template.

Change 243597 had a related patch set uploaded (by Paladox):
[WikibaseJavaScriptApi] Update jenkins tests

https://gerrit.wikimedia.org/r/243597

Change 243597 abandoned by Paladox:
[WikibaseJavaScriptApi] Update jenkins tests

https://gerrit.wikimedia.org/r/243597

https://gerrit.wikimedia.org/r/#/c/270757/

https://gerrit.wikimedia.org/r/270761