Skip to content

cascading bat test functionality #18

@tallguyjenks

Description

@tallguyjenks

Problem Statement:

The BAT tests for a service should also reach out to the platform and find inter-related services and pull their tests and run those as well so at that point all tests for a deployment and its interrelated dependencies are executed validating full functionality for the apps across an entire environment

Stream of consciousness, idea, what should likely happen is that when an application and this is gonna be a hypothetical, say an experience application needs to get data from my process application, which needs to get raw data from a system application because of the tree of dependencies the experience API is dependent on the process. API is dependent on the system API so when deploying changes to the experience API, it will run its bat tests. Ideally, an automation should exist to then grab the dependencies for the experience API, which in this case is the process API and then run its tests which that operation should then do the same and run the bat tests for its dependencies the system API.

The easiest way of accomplishing this would be to have a sub action that exists solely to facilitate the process of setting up the bat tests, getting them configured and actually running them so kind of like a stripped down version of the build action with no compilation and unit testing or anything needed we can just shallow clone the repository just for the bat d run the configuration steps and then run the test. The first step in the sub action should be able to get the dependencies for the given repository it's running in and then kick off those actions so they all aren't waiting for the completion of the former before running.

Where the key metadata should live for what is a dependency for a given application could should maybe be on any point platform in a custom field might need to look into where those fields map to how they're accessible and potentially used any point CLI to grab that data from the API as JSON and then utilize the jq CLI comma to par it and then operate up upon it.

Scope of Work:

  • [ ]

Definition of Done:

  • [ ]

Resources:

in pipeline run bat tests for service and then query tag in anypoint platform services that share a tag and then shallow clone the repositories BAT folders and then run each of them to verify

test the importing of other services on exchange into other services and then using their endpoints

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions