Versions Compared

Old Version 7

changes.mady.by.user Unknown User (fabian.steels@cetic.be)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (fabian.steels@cetic.be)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

User story

  • As a user I want to change my
    • mandate 
  • profile So that the application (MAIN) could display relevant information related to my profile

Initial data/state:

  • a mandate with a 3rd person must be defined with mandates-csam (MD-CSAM) application. The principal must give a mandate to the agent corresponding to a profile defined into the application.
  • The user must be logged out of MAIN (cf AUTH- TS-9003) in order to change his mandate
  • Application profile configuration must be fill in (see Test Scripts: Athena)
Test script IDTest ActionsAssertion
ATH-
TS-
24
007


SeqActorActionAutomatic/Manual
1MAINLogin into the application and choose the OLD mandateAutomatic: see TS-001
2MAIN
starting an identification action
Global logout from the application

Automatic: could be

automate

automated but cannot be generic since the applications to test have all a different layout.

See TS-003

2
3
TEST3CSAMauthenticate himself with
MAIN

initialize a test loop based on the application profile configuration (mandate)

N=1

Automatic
Start a new identification action to choose the NEW mandateAutomatic: could be automated but cannot be generic since the applications to test have all a different layout.
4CSAMLogin via 
eid / TOTP / itsME

Automatic: see TS

5,6 or 7

Manual

-001

5eHealth-IDPConsult the list of mandates 
4CSAMchoose the Nth mandate (based on the application profile configuration)
Could be difficult to
automate
automated as CSAM and MAIN are different applications
5TESTcheck assertion on mainAutomatic: could be automate but cannot be generic since the applications to test have all a different layout. (what to test ?)
6
MAINGlobal logout from the applicationAutomatic: could be automate but cannot be generic since the applications to test have all a different layout.7TESTif it remains mandate to test, goto 3automatic 
eHealth-IDPChoose the NEW mandate Could be difficult to automated as CSAM and MAIN are different applications
7MAIN//


When the test actions are performed

In sequence 5,

the following assertions must be checked:

MAIN application:

the
  • The application must display correct information/layout following the
mandate connected
  • chosen mandate (OLD and NEW ones)

eHealth endpoint:

  • The IAM session should be open 
  • The IDP session should be open with the corresponding
profile
  • mandate
  • It redirects to the MAIN application