2 2 conformance

.gitignore

@@ -3,6 +3,7 @@
 
 # dependencies
 /node_modules
+/ng/node_modules
 
 # build output
 /dist

README.md

@@ -21,43 +21,43 @@ Tests are currently implemented for version [1.2](https://fdc3.finos.org/docs/1.
 
 ✔️ **Multiple Platforms**
 
-It can be annoying for users to find that features in their apps that they rely on don't work when changing between Desktop Agents.  Hopefully these conformance tests will add security around that.
+It can be annoying for users to find that features in their apps that they rely on don't work when changing between Desktop Agents. Hopefully these conformance tests will add security around that.
 
 ✔️ **Marketing**
 
-FINOS has created _badges_ to indicate conformance with the FDC3 standard.   By passing the conformance tests and joining the conformance program, firms are able to use those badges in their own marketing materials.
+FINOS has created _badges_ to indicate conformance with the FDC3 standard. By passing the conformance tests and joining the conformance program, firms are able to use those badges in their own marketing materials.
 
 ✔️ **Backwards Compatibility**
 
-There are multiple versions of the FDC3 standard.  A Desktop Agent could host apps written in _any one of these versions_.  For that reason, it's important that Desktop Agents are tested to make sure that they keep on supporting apps written against older versions of FDC3.
+There are multiple versions of the FDC3 standard. A Desktop Agent could host apps written in _any one of these versions_. For that reason, it's important that Desktop Agents are tested to make sure that they keep on supporting apps written against older versions of FDC3.
 
 ## How Does It Work?
 
 There are two main parts to conformance:
-  
-  - Running the tests _locally_, then
-  - Joining the Conformance Program
+
+- Running the tests _locally_, then
+- Joining the Conformance Program
 
 ### Running The Conformance Tests
 
-You can either run the hosted conformance tests listed in the FINOS App Directory, or run them on your local machine (useful if you are making changes).  Instructions for doing either of those things are here:
+You can either run the hosted conformance tests listed in the FINOS App Directory, or run them on your local machine (useful if you are making changes). Instructions for doing either of those things are here:
 
 #### Using The FINOS App Directory
 
-If you have a Desktop Agent supporting the [AppD v2 standard](https://fdc3.finos.org/docs/app-directory/spec), you can point it at [The FINOS App Directory](https://directory.fdc3.finos.org) which contains not only the current conformance suite but also many other sample FDC3 applications.  The endpoint for your agent is:
+If you have a Desktop Agent supporting the [AppD v2 standard](https://fdc3.finos.org/docs/app-directory/spec), you can point it at [The FINOS App Directory](https://directory.fdc3.finos.org) which contains not only the current conformance suite but also many other sample FDC3 applications. The endpoint for your agent is:
 
- - https://directory.fdc3.finos.org/v2/apps
+- https://directory.fdc3.finos.org/v2/apps
 
 #### Local Installation
 
 1.  **Check Out The Repo**
 
 This repository currently contains:
 
- - `tests` - the FDC3 conformance tests, implemented using Mocha / TypeScript, making use of the FDC3 type definitions, [@finos/fdc3](https://www.npmjs.com/package/@finos/fdc3).
- - `static` - HTML files used to create the static server
- - `directory` - Some JSON files in the FDC3 V2 Directory format that you can use to set up your desktop agent with either 1.2 or 2.0 test suites.
- - `terms-conditions` - [Terms and Conditions](terms-conditions/FDC3-Certified-Terms.md) of the Conformance Program.  Instructions for joining the program are [here](Instructions.md)
+- `tests` - the FDC3 conformance tests, implemented using Mocha / TypeScript, making use of the FDC3 type definitions, [@finos/fdc3](https://www.npmjs.com/package/@finos/fdc3).
+- `static` - HTML files used to create the static server
+- `directory` - Some JSON files in the FDC3 V2 Directory format that you can use to set up your desktop agent with either 1.2 or 2.0 test suites.
+- `terms-conditions` - [Terms and Conditions](terms-conditions/FDC3-Certified-Terms.md) of the Conformance Program. Instructions for joining the program are [here](Instructions.md)
 
 2. **Install Dependencies**
 
@@ -77,7 +77,7 @@ npm run start
 
 4.  **Set Up Your Desktop Agent**
 
-You will need to set up your desktop agent so that it has an _App Directory containing all the conformance apps_.   
+You will need to set up your desktop agent so that it has an _App Directory containing all the conformance apps_.  
 This step is vendor-dependent, but examples of `AppD` records can be found in the `directory` folder.
 
 ### Running The Tests
@@ -86,7 +86,7 @@ Once you have configured your desktop agent correctly, open the conformance app
 
 <img src="static/selecting.png" alt="Selecting Tests" width="400px" />
 
-The tests run and produce an output in the window.  Failure are shown with a stack trace in red:
+The tests run and produce an output in the window. Failure are shown with a stack trace in red:
 
 <img src="static/failing.png" alt="Running Tests" width="400px" />
 
@@ -106,20 +106,18 @@ Once you have followed these steps, you will be allowed to display the FDC3 Comp
 
 ### Who Is Conformant?
 
-We publish the details of conformant desktop agents on the [FDC3 Community Page](https://fdc3.finos.org/community).  Please check there to find out who FINOS has certified! 
+We publish the details of conformant desktop agents on the [FDC3 Community Page](https://fdc3.finos.org/community). Please check there to find out who FINOS has certified!
 
 [Read the latest blog post here about the certification announcements at OSFF New York](https://www.finos.org/blog/first-fdc3-1.2-certified-desktop-agents)
 
-
 ## Contributing
 
 Please see [CONTRIBUTING](CONTRIBUTING.md) page.
 
 ## License
 
-Copyright 2022 FINOS 
+Copyright 2022 FINOS
 
 Distributed under the [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0).
 
-SPDX-License-Identifier: [Apache-2.0](https://spdx.org/licenses/Apache-2.0)
-
+SPDX-License-Identifier: [Apache-2.0](https://spdx.org/licenses/Apache-2.0)

ng/features/intents-tests.feature

@@ -0,0 +1,31 @@
+Feature: FDC3 Raise Intents
+
+  Background:
+    Given A Desktop Agent in "api1"
+    And "textContextX" is a context object with the following contents
+      | type         |
+      | textContextX |
+    And the following apps are configured with the following behaviours
+      | App | Usage                                                 | ListensFor (pattern: intent([context-types…]) (=> result-type))                               | On Startup                                                                        |
+      | A   | Raise Intent tests without results                    | aTestingIntent(testContextX,testContextZ) sharedTestingIntent1(testContextX)                  | addIntentListener() for given intents                                             |
+      | B   | Raise Intent tests with Context results               | bTestingIntent(testContextY) sharedTestingIntent1(testContextX, testContextY) => testContextY | addIntentListener() for given intents                                             |
+      | C   | Find Intent tests (never started)                     | cTestingIntent(testContextX) => testContextZ                                                  | addIntentListener() for given intents                                             |
+      | D   | Find Intent tests (never started)                     | sharedTestingIntent2(testContextX) => testContextZ                                            | addIntentListener() for given intents                                             |
+      | E   | Find Intent & Raise Intent with Channel result        | sharedTestingIntent2(testContextY) => channel                                                 | addIntentListener() for given intents                                             |
+      | F   | Find Intent & Raise Intent with PrivateChannel result | sharedTestingIntent2(testContextY) => channel<testContextZ> *                                 | addIntentListener() for given intents                                             |
+      | G   | Find Intent tests (never started)                     | sharedTestingIntent2(testContextY)                                                            | addIntentListener() for given intents                                             |
+      | H   | Raise Intent (bad config/behavior)                    | sharedTestingIntent2(testContextY) => testContextZ                                            | - no action                                                                       |
+      | I   | Raise Intent (bad config/behavior)                    | sharedTestingIntent2(testContextY) => testContextZ                                            | addIntentListener(‘MadeUpIntent’, handler)                                        |
+      | J   | PrivateChannels are private                           | privateChannelIsPrivate(privateChannelDetails) => privateChannelIsPrivateResult               | Tries to retrieve privateChannel sent in the privateChannelDetails context, fails |
+      | K   | PrivateChannel lifecycle events                       | kTestingIntent(testContextX) => channel<testContextZ>                                         | addIntentListener() for given intents                                             |
+
+  @FDC3-2.0
+  Scenario: 2.0-RaiseIntentSingleResolve
+    When I call "api1" with "raiseIntent" with parameters "aTestingIntent" and "{testContextX}"
+    And I refer to {result} as "intentResolution"
+    Then "{intentResoltion}" is an object with the following contents
+      | source.appId | intent         | source.instanceId |
+      | A            | aTestingIntent | <exists>          |
+    And I call "intentResolution" with "getResult"
+    And "{result}" is void
+    And I can close the app with instanceId "{intentResoltion.source.instanceId}"

ng/features/open-tests.feature

@@ -0,0 +1,15 @@
+Feature: FDC3 Open
+App A calls a function (see below) to open a second app, B
+
+  Background:
+    Given A Desktop Agent in "api1"
+    And "AppB" is the ID of an FDC3 Application named "AppBName"
+
+  @FDC3-1.2
+  Scenario: AOpensB1
+    When I call "api1" with "open" with parameter "AppBName"
+    Then "{result}" is an object with the following contents
+      | appIdentifier | instanceId |
+      | AppB          | <exists>   |
+    And I receive an "app-opened" event with appId "AppB"
+    And I can close the app with instanceId "{result.instanceId}"

ng/index.html

@@ -0,0 +1,6 @@
+<html>
+  <body>
+    <p>Hello Vite!</p>
+    <script type="module" src="src/ui/testing-app.ts"></script>
+  </body>
+</html>