[js/web/training] added end-to-end tests

[carzh]

Summary

• following inference's set-up for end-to-end tests, created an end-to-end test runner for training
• this test runner copies testdata from the trainingapi folder
• then runs two tests (training session with evalModel & optimizer model, and training session with the minimum options), and tests if the ORT-web training package encompasses inference
  • these tests check
    • createTrainingSession
    • runTrainStep
    • runOptimizerStep if applicable
    • the parameters methods (getParametersSize, loadParametersBuffer, and getContiguousParameters)

TL;DR

• js/web/test/training/e2e/run.js is responsible for setting up and running the end to end tests
• js/web/test/training/e2e/common.js contains the test function definitions (testInferenceFunction, testTrainingFunctionMin, testTrainingFunctionAll)

Flow

• entrypoint: user runs the following command in the terminal: npm run test:training:e2e
• js/web/package.json was modified to include an npm script that will run run.js which will run the end to end tests
• js/web/test/training/e2e/run.js is responsible for
  • detecting and installing local tarball packages of ORT-web
  • copying training data to the js/web/training/e2e/data folder
  • starting two Karma processes. Karma is a test runner framework that simulates testing in the browser.
    • In this case, the tests happen in Chrome. We can configure the tests to run in Edge and other browsers in the future.
    • one of these karma processes is self-hosted, meaning it pulls the ORT-web package from local
    • the other karma process is not self-hosted, meaning it pulls the ORT-web package from another source. In this case, we start an http server that serves the ORT-web binaries.
      • js/web/test/training/e2e/simple-http-server.js is responsible for starting the HTTP server and serving the ORT binary files. This code almost identical to the same code in the inference E2E tests.
• js/web/test/training/e2e/karma.conf.js Karma configuration file that specifies what happens when a karma process is started. The config specifies Mocha as the testing framework, which will go through all the loaded files and run any tests that exist
• js/web/test/training/e2e/browser-test-wasm.js File that contains the tests that Mocha will pick up on and run.
• The test functions (such as testInference and testTrainingFunctionAll) are defined in js/web/test/training/e2e/common.js.

Notes

• I followed the tests for training core where they randomly generated input for the training session
• E2E tests are triggered by running npm run test:training:e2e -- suggestions for alternative script names are appreciated!!!

Motivation and Context

• adding training bindings for web

[carzh]

Successful pipeline run -- the E2E training tests stage can be seen here

[jchen351]

Looks good from the ES side.

[askhade]

LGTM