THIS SPACE IS UNDER CONSTRUCTION

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 29 Next »

It is advised to read the eHealthBoxconsent, therapeutic link or therapeutic exclusion  user manual first to gain a better understanding of the framework.

Introduction

This manual is meant for everyone that works on the development of the SOAP testing framework.

Target audience

  • Developers of the eHealth SOAP services

Project tree

└───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

Maintenance

Web

The chromedriver,  found at src/test/resources/chromedriver.exe, has to be updated occasionally
to keep it up-to-date with the most recent version of Chrome.

The most recent version of chromedriver can be found here.

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

Features

Create a feature

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:

Edit a feature

A very good explanation of everything you can do with a feature file can be found here.

Steps

Create/edit a step

You can write a new step in one of the existing step files or you can create a new file for it in the steps package. For example:


A very good explanation of how step definitions work can be found here.

Some useful tips to work with step definitions can be found here.

Utilities

Create a utility

Edit a utility

FAQ

How to add a new service

to do


  • No labels