The following are all mock apps used within the FDC3 conformance framework tests.
| Mock App Name | Used By | Intents (Contexts) |
|---|---|---|
| Channels | fdc3.broadcast | |
| General | fdc3.open | |
| Intent-A | fdc3.findIntent, fdc3.findIntentByContext, fdc3.raiseIntent | aTestingIntent (testContextX, testContextZ), sharedTestingIntent1 (testContextX) |
| Intent-B | fdc3.findIntent, fdc3.findIntentByContext, fdc3.raiseIntent | bTestingIntent (testContextY), sharedTestingIntent1 (testContextX, testContextY) |
| Intent-C | fdc3.findIntent, fdc3.findIntentByContext, fdc3.raiseIntent | cTestingIntent (testContextX) |
The apps can be started in parallel via:
yarn startIt is the responsibility of the FDC3 application owner (the application under test) to ensure that these mock apps are configured correctly before the tests run. Examples of how to do this for some known FDC3 applications are below:
After the installation, copy the json snippet from snippet into /public/configs/application/appd.json under appd. This will add the test app and mock apps into the desktop container application under test, required for conformance testing.
Some tests in some FDC3 applications require already open mock apps to be closed in some cases before they can successfully test assertions automatically. Unfortunately, the FDC3 API does not support closing of previously opened apps, however, JavaScript/the HTML Standard does via window.close().
This has been implemented in file mock-functions.js.
If your container/Desktop Agent doesn't support closing windows with window.close(), it is likely you will need to update this file.