THIS SPACE IS UNDER CONSTRUCTION

User story

  • As a user I want to login into the application (MAIN) So that I can consult the list of my profiles 
  • As a user I want to login into the application (MAIN) So that I can choose my profile
  • As a user qualified by his profile (citizen, physician, nurse, dentist, midwife, pharmacist) I want to login into the application (MAIN) So that the application will display the correct information corresponding to my profile

Initial data/state:

  • The user must be logged in MAIN (cf TS-001)


Test Script IDTest ActionsAssertion
TS-004-01 (citizen)
SeqActorActionAutomatic/Manual
1MAINStarting an identification actionAutomatic: could be automate but cannot be generic since the applications to test have all a different layout.
2CSAMAuthentication via eid / TOTP / itsME

see TS-001

3eHealth-IDPConsulting the list of profiles Could be difficult to automate as CSAM and MAIN are different applications
4eHealth-IDPChoosing the citizen profile Could be difficult to automate as CSAM and MAIN are different applications
5MAIN//

At point 3, the following assertions must be checked:

eHealth-IDP:

  • profile list must be displayed by the IDP
  • profile list displayed  must correspond to the profile list defined by the application.
    • if test fails, the configuration of the realm is not correct.
  • It redirects to the MAIN application

When the test actions are performed the following assertions must be checked (point 5):

MAIN

  • must display an error if the profile chosen doesn't have the right to connect to the application (MAIN)
    • must display a welcome page relative to the   the profile chosen


TS-004-02 (physician)

Seq

Actor

Action

Automatic/Manual

1MAINStarting an identification actionAutomatic: could be automate but cannot be generic since the applications to test have all a different layout.
2CSAMAuthentication via eid / TOTP/ itsME

see TS-001

3eHealth-IDPConsulting the list of profiles Could be difficult to automate as CSAM and MAIN are different applications
4eHealth-IDPChoosing the physician profile Could be difficult to automate as CSAM and MAIN are different applications
5MAIN//

At point 3, the following assertions must be checked:

eHealth-IDP:

  • profile list must be displayed by the IDP
  • profile list displayed  must correspond to the profile list defined by the application.
    • if test fails, the configuration of the realm is not correct.
  • it redirects to the MAIN application

When the test actions are performed the following assertions must be checked (point 5):

MAIN

  • must display an error if the profile chosen doesn't have the right to connect to the application (MAIN)
    • must display a welcome page relative to the   the profile chosen


TS-004-03 (nurse)

Seq

Actor

Action

Automatic/Manual

1MAINStarting an identification actionAutomatic: could be automate but cannot be generic since the applications to test have all a different layout.
2CSAMAuthentication via eid / TOTP/ itsME

see TS-001

3eHealth-IDPConsulting the list of profiles Could be difficult to automate as CSAM and MAIN are different applications
4eHealth-IDPChoosing the nurse profile Could be difficult to automate as CSAM and MAIN are different applications
5MAIN//


At point 3, the following assertions must be checked:

eHealth-IDP:

  • profile list must be displayed by the IDP
  • profile list displayed  must correspond to the profile list defined by the application.
    • if test fails, the configuration of the realm is not correct.
  • It redirects to the MAIN application

When the test actions are performed the following assertions must be checked (point 5):

MAIN

  • must display an error if the profile chosen doesn't have the right to connect to the application (MAIN)
    • must display a welcome page relative to the   the profile chosen


TS-004-04 (dentist)

Seq

Actor

Action

Automatic/Manual

1MAINStarting an identification actionAutomatic: could be automate but cannot be generic since the applications to test have all a different layout.
2CSAMAuthentication via eid / TOTP/ itsME

see TS-001

3eHealth-IDPConsulting the list of profiles Could be difficult to automate as CSAM and MAIN are different applications
4eHealth-IDPChoosing the dentist profile Could be difficult to automate as CSAM and MAIN are different applications
5MAIN//


At point 3, the following assertions must be checked:

eHealth-IDP:

  • profile list must be displayed by the IDP
  • profile list displayed  must correspond to the profile list defined by the application.
    • if test fails, the configuration of the realm is not correct.
  • it redirects to the MAIN application

When the test actions are performed the following assertions must be checked (point 5):

MAIN

  • must display an error if the profile chosen doesn't have the right to connect to the application (MAIN)
    • must display a welcome page relative to the   the profile chosen


TS-004-05 (midwife)

Seq

Actor

Action

Automatic/Manual

1MAINStarting an identification actionAutomatic: could be automate but cannot be generic since the applications to test have all a different layout.
2CSAMAuthentication via eid / TOTP/ itsME

see TS-001

3eHealth-IDPConsulting the list of profiles Could be difficult to automate as CSAM and MAIN are different applications
4eHealth-IDPChoosing the midwife profile Could be difficult to automate as CSAM and MAIN are different applications
5MAIN//


At point 3, the following assertions must be checked:

eHealth-IDP:

  • profile list must be displayed by the IDP
  • profile list displayed  must correspond to the profile list defined by the application.
    • if test fails, the configuration of the realm is not correct.
  • It redirects to the MAIN application

When the test actions are performed the following assertions must be checked (point 5):

MAIN

  • must display an error if the profile chosen doesn't have the right to connect to the application (MAIN)
    • must display a welcome page relative to the   the profile chosen


TS-004-06 (pharmacist
)

Seq

Actor

Action

Automatic/Manual

1MAINStarting an identification actionAutomatic: could be automate but cannot be generic since the applications to test have all a different layout.
2CSAMAuthentication via eid / TOTP/ itsME

see TS-001

3eHealth-IDPConsulting the list of profiles Could be difficult to automate as CSAM and MAIN are different applications
4eHealth-IDPChoosing the pharmacist profile Could be difficult to automate as CSAM and MAIN are different applications
5MAIN//


At point 3, the following assertions must be checked:

eHealth-IDP:

  • profile list must be displayed by the IDP
  • profile list displayed  must correspond to the profile list defined by the application.
    • if test fails, the configuration of the realm is not correct.
  • it redirects to the MAIN application

When the test actions are performed the following assertions must be checked (point 5):

MAIN

  • must display an error if the profile chosen doesn't have the right to connect to the application (MAIN)
    • must display a welcome page relative to the   the profile chosen
  • No labels