Versions Compared

Key

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

...

Code Block
└───src
    ├───main
    │   ├───java
    │   └───resources
    │       └───config
    │           └───P12
    │               └───acc
    └───test
        ├───java
        │   └───be
        │       └───imec
        │           └───hie
        │               ├───features
        │               │   ├───consent
        │               │   ├───ehealthbox
        │               │   ├───therapeuticExclusion
        │               │   └───therapeuticLink
        │               ├───runners
        │               ├───steps
        │               │   ├───consent
        │               │   ├───ehealthbox
        │               │   ├───therapeuticExclusion
        │               │   └───therapeuticLink
        │               └───utils
        └───resources
            ├───attachments
            ├───testdata
            └───chromedriver.exe

...

Simply replace to chromedriver in the project with the new one from the link above.

How to add a new feature to

...

an existing

...

To change the tests for an existing feature in the project, you need to change the respective feature file and step(s).

How to edit a feature file

  • Go to the feature file 

How to edit a step

to do

How to edit utilities

to do

How to add a new feature to an existing service

to do

How to add a new feature file

to do

How to add new steps

to do

How to add new utilities

to do

How to add a new service

to do

How to handle test data

...

service

  1. Create a new *.feature file ,with a name corresponding to the feature, in the package of an existing service (e.g. features/ehealthbox).
  2. Write the feature you want to test in the newly created file. You can create one or more scenarios for this new feature. See the example below:

    Code Block
    languagegherkin
    titleExample *.feature file
    Feature: TS-407: eHealthBox info
      As a user
      I want to know my eHealthBox info
      In order to know how many messages are in standby
    
      Scenario: Verify the eHealthBox info
        Given user is logged in
        When user is on the box info page
        Then the box info is shown correctly


  3. For each step in a scenario, there is should be a corresponding function in one of the steps of the existing service (e.g. steps/ehealthbox).
    If there isn't a step matching your step yet, you should create a new function for it in one of the step.java files in one of the existing services.
    Here is an example of such a function:

    Code Block
    languagegherkin
    titleExample step function
    @Given("user is logged in")
        public void user_is_logged_in() {
            //Instructions for the software vendor: Please write the UI support code here.
        }


  4. To validate the scenario of the new feature, you'll have to create a new utils

How to add a new service

to do


Features

Create a feature

SImply create a new *.feature file, with a name fitting for the new feature, in the package of an existing service (e.g. features/ehealthbox). For example:

Image Added

Edit a feature

A very good explanation of everything you can do with a feature file can be found on this Gherkin reference.

Steps

Create a step

Edit a step

Utilities

Create a utility

Edit a utility


Test data