add text
This commit is contained in:
parent
57e500eb8a
commit
acc1c38c58
|
@ -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
|
implementing the OIDC4VP protocol that we have developed. Consequently, the
|
||||||
IdHub is multifaceted, capable of functioning as an issuer, wallet or verifier.
|
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 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
|
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
|
user stories during the requirements phase. These criteria are designed to match
|
||||||
|
|
Reference in New Issue