Please enable JavaScript.

Coggle requires JavaScript to display documents.

Automated testing of GBT - Coggle Diagram

- - - - the client-server application that builds and runs containers
        
        containing
        
        daemon dockerd
        
        API's used by programs to instruct the daemon
        
        a command-line interface (CLI) client docker
    - - a tool that allows us to handle multiple containers at once
      - create a single docker-compose.yml file
        
        which provides a snapshot of the whole project from ten-thousand feet in a few lines
  - - - Docker Engine, Docker CLI client, Docker Compose, etc...
  - - - cd docker ./up docker-compose ps
        
        up is a bash script that runs docker compose up to create and start the required containers
        
        docker ps lists all running containers in the docker engine. docker-compose ps lists containers related to images declared in the docker-compose file
        
        The result of docker-compose ps is a subset of the result of docker ps
        
        there should be up to 7 docker images running
        
        called
        
        product
        
        a WireMock instance that simulates WON responses for the Product endpoint
        
        media_asset
        
        a WireMock instance that simulates WON responses for the MediaAsset endpoint
        
        whatson
        
        an nginx server
        
        provides a single IP address for the mocked WHATS’On services
        
        with each service on a different port
        
        WireMock cannot handle this requirement
        
        ses_sftp
        
        a real SFTP server running locally in a container
        
        localstack
        
        a local instance of AWS services
        
        mailhog
        
        an instance of the smtp server
        
        optional
        
        fuse
        
        runs an image of JBoss Fuse
        
        all of them with status up
    - - cd docker ./down
    - - build the bundle
        
        mvn clean package -DskipTests -Dcobertura.skip=true
        
        in GBT root directory
        
        The maven package command will create a jar file for each bundle
        
        under the target directory (eg. esb-compliance-1.56.jar)
      - deploy the bundle
        
        drop the jar file into the esb/<bundle>/docker/fuse-home/deploy directory
- - - - to allow you to download packages
  - - - called test-definition.feature
        
        eg. handle-ingest-status-update.feature
        
        Feature: Handle Freeway ingest status updates Scenario: valid status update received from Freeway When a status update message is placed on the queue Then the message should be picked up and deleted And the message should be archived And the media position should be updated in WHATS'on
        
        written in Gherkin DSL
        
        uses keywords to structure executable specifications
        
        Each keyword is translated to many spoken languages
        
        example above uses English
      - describe the features that need to be tested
    - - called test-implementation.js
        
        eg. status-update-handling-steps.js
        
        When(/^a status update message is placed on the queue$/, function () { return sqs.sendMessage({ MessageBody: JSON.stringify({}), QueueUrl: "http://10.5.0.10:4566/000000000000/freew-esb-ingest-outbound.fifo" }).promise(); });
      - step definitions
        
        written in JavaScript
        
        translate the Gherkin scenarios into actions
    - - a testing framework that supports Behaviour-Driven Development