From acc1c38c589065ba3cfc4ef0ce363b1d2f5d67ab Mon Sep 17 00:00:00 2001 From: mildred Date: Mon, 4 Mar 2024 21:05:09 +0100 Subject: [PATCH] add text --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index beebfda..8cfc287 100644 --- a/README.md +++ b/README.md @@ -27,7 +27,8 @@ and engage in dialogues with other idHub instances that operate as user wallets implementing the OIDC4VP protocol that we have developed. Consequently, the IdHub is multifaceted, capable of functioning as an issuer, wallet or verifier. -For E2E automated testing, we use Playwright, a tool for end-to-end testing, to execute user flow simulations and validate the IdHub behaviour under controlled conditions. Playwright is designed for automating browser interactions, making it ideal for end-to-end testing. + +Playwright is designed for automating browser interactions, making it ideal for end-to-end testing. The data used in our tests is pre-configurated or generated dynamically during the execution of the tests and is purely fictitious. This approach allows us to create a controlled testing environment isolated from real-world data, ensuring the integrity and reliability of ourtests. The testing to be executed is grounded in the acceptance criteria defined within the user stories during the requirements phase. These criteria are designed to match