Improve user feature

Description

Background

According to the behat test needs to be improved. In this issue Feature Users is going to be improved.

Requirements

  • Tag feature for user context

  • Use a background if multiple scenario's use same context, example:

  • Scenario: User overview

    • Use Viewing as behaviour

    • Remove interaction from Given (start with When if context is completely defined in background)

    • Replace the URL's for descriptions

    • Check if the selections from the background/context are on the page instead of some labels

  • Scenario: Add an user to the Admin scope

    • Use "Creating" as behaviour

    • Replace the URL's for descriptions

    • Remove interaction from Given (start with When if context is completely defined in background), example:

  • Scenario: Add an existing user to the Admin scope

    • Use "Trying to add existing user" as behaviour

    • Replace the URL's for descriptions

    • Remove interaction from Given (start with When if context is completely defined in background), example:

  • Scenario: Add an existing user to the Public scope

    • Is duplicate of trying to create an existing user

  • Scenario: Login with a newly added user

    • Can be removed this is covered in

  • Scenario: Add an existing user to the Public scope

    • Can be removed, same logic as admin scope

  • Scenario: Login with a newly added user into the admin scope

    • Should be moved to

    • Use "Try to login to the admin with a user with the public scope"

    • Remove interaction from Given (start with When if context is completely defined in background)

    • Replace the URL's for descriptions

    • Use following "flow" (so only one Given, When Then, in that order), example:

  • Scenario: Delete a user

    • Use Deleting as behaviour

    • Remove interaction from Given (start with When if context is completely defined in background)

    • Replace the URL's for descriptions

    • Use following "flow" (so only one Given, When Then, in that order), example:

  • The following scenario's are missing and should be added:

    • Editing a user

    • Creating / editing with invalid data

  • Use folder structure for features, so add the group features in own folder. This folder can be a sub folder of user since this is user functionality.

Technical tasks

None

Deployment actions

None

Assignee

Unassigned

Client

Integrated Marijn

Epic Link

Fix versions

Configure