You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 29, 2022. It is now read-only.
It would be nice to have automated tests for the WebAssembly API. This is complicated issue right now as the --preload-file does not support Node.js environment and that an headless browser should be used. Setting up headless browser environment without heavy dependencies is not possible (chrome --headless does not provide enough control without the debug protocol and using the debug protocol requires further dependencies).
At first, the tests will be semi-automatic, requiring a web server (it seems like loading .wasm files is complicated over the file:// protocol).
After loading the test HTML file, it initializes the swi instance, runs some tests, and writes result (PASS/FAIL) to the page. Loading and inspection of results has to be done manually for now.
The text was updated successfully, but these errors were encountered:
For pengines I used phantomjs, but this is broken and discontinued. I switched to slimerjs, but this node module seems to be hard to synchronise with the latest firefox ... A good, easy to install and robust alternative is more than welcome ...
@JanWielemaker where could I see the tests? They do not seem to be in swipl-devel nor in the pengines repo. The headless Chrome/Chromium approach will require Node as a dependency (for wasm build I might be able to use one that comes with Emskripten) but if the slimerjs required it as well, it's not a so big deal.
It would be nice to have automated tests for the WebAssembly API. This is complicated issue right now as the
--preload-file
does not support Node.js environment and that an headless browser should be used. Setting up headless browser environment without heavy dependencies is not possible (chrome --headless
does not provide enough control without the debug protocol and using the debug protocol requires further dependencies).At first, the tests will be semi-automatic, requiring a web server (it seems like loading .wasm files is complicated over the
file://
protocol).After loading the test HTML file, it initializes the swi instance, runs some tests, and writes result (PASS/FAIL) to the page. Loading and inspection of results has to be done manually for now.
The text was updated successfully, but these errors were encountered: