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 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 the profiles defined by the application will appear in the CSAM 
  • As a user qualified by his profile (
    • MAIN
  • 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 UC 5, 6 or 7)

TS dependencies:

  • NoneTS-001)


Test Script IDTest ActionsAssertion
TS-
10
004-01 (citizen)


SeqActorActionAutomatic/Manual
1MAIN
starting
Starting an identification actionAutomatic: could be automate but cannot be generic since the applications to test have all a different layout.
2CSAM
authenticate himself with
Authentication via eid / TOTP / itsME

see

UC 5,6 or 73CSAM

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 
choose a profile (any of them)
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.
US-10-02out of scope
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

out of scope

The user is authenticated and accesses to the permitted services in MAIN.