This repository has been archived by the owner on Mar 27, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 160
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: Add BDD test for legacy-connection protocol (edge to edge throu…
…gh controller). Make a few refactoring (#3353) - Add BDD test for legacy-connection protocol. Edge to edge case is fully implemented. Case through mediator is implemented partially (Only steps are added. Need to add .feature file to run test) - Make a few refactoring Signed-off-by: Abdulbois <[email protected]> Signed-off-by: Abdulbois <[email protected]>
- Loading branch information
Showing
6 changed files
with
763 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# | ||
# Copyright Avast Software. All Rights Reserved. | ||
# | ||
# SPDX-License-Identifier: Apache-2.0 | ||
# | ||
# Reference : https://github.com/hyperledger/aries-rfcs/tree/main/features/0160-connection-protocol | ||
|
||
@all | ||
@controller | ||
@legacyconnection_e2e_controller | ||
Feature: Establishing DIDComm V1 using Connection RFC-0160 protocol between the agents using controller API | ||
|
||
Scenario: legacy connection e2e flow using controller api | ||
Given "Alice" agent is running on "localhost" port "8081" with controller "https://localhost:8082" | ||
And "Bob" agent is running on "localhost" port "9081" with controller "https://localhost:9082" | ||
|
||
When "Alice" creates legacy invitation through controller with label "alice-agent" | ||
And "Bob" receives legacy invitation from "Alice" through controller | ||
And "Bob" approves connection invitation through controller | ||
And "Alice" approves connection request through controller | ||
And "Alice" waits for legacy post state event "completed" to web notifier | ||
And "Bob" waits for legacy post state event "completed" to web notifier | ||
|
||
Then "Alice" retrieves connection record through controller and validates that legacy connection state is "completed" | ||
And "Bob" retrieves connection record through controller and validates that legacy connection state is "completed" |
Oops, something went wrong.