Open API Test Cases

[robmoffat]

A Opens B

• AOpensB1: [ ] A calls fdc3.open(‘app B Name’), check app B opens
• AOpensB1: [ ] A calls fdc3.open({name: “<app B Name>”}), check app B opens
• AOpensB1: [ ] A calls fdc3.open({name: “<app B Name>”, appId: “<app B ID”}), check app B opens
• AOpensB1: [ ] A calls {appID: “<app ID>”}, check app **B** opens. (FDC3 2.0`)

A Fails To Open B

• AFailsToOpenB: Run the above 4 tests again with a non-existent app name/app id. Should return “App Not Found” Error from https://fdc3.finos.org/docs/api/ref/Errors#openerror

A Opens B With Context

App	Step	Description
A	Opening App	various open methods as in AOpensB1 except with a <context> argument check app opens
B	Context present	fdc3.addContextListener() - receives <context> from A

• AOpensBWithContext: Perform above tests
• AOpensBWithSpecificContext: Perform above but replace Bs call with fdc3.addContextListener('fdc3.instrument)`

Specific Context

App	Step	Description
A	Opening App	fdc3.open(‘app Name’, <contact context>) check app opens
B	Context present	fdc3.addContextListener() - receives from a
A	Promise	- receives a rejection from the open promise with “App Timeout’ from https://fdc3.finos.org/docs/api/ref/Errors#openerror

• AOpensBWithWrongContext: As above
• AOpensBNoListen: Skip `fdc3.addContextListener() above.
• AOpensBMultipleListen: B performs fdc3.addContextListener('fdc3.instrument') prior to the existing addContextListener`. The correct context listener should receive the context, and the promise completes successfully
• AOpensBMalformedContext: A tries to pass malformed context to B. Context listener receives nothing, promise completes successfully.

[osouthwell-scottlogic]

@robmoffat Hi, is it possible to have this issue assigned to me?

[ColinEberhardt]

This has been partially implemented in #49 - we do have a big obstacle, how do you verify that a given app was opened and (optionally) context received. We'll look into various ways we can confirm this in an automated fashion.

[ColinEberhardt]

We now verify the communication from app to mock-app, via #51 - so this issue is resolved.