July 14, 2023 API Testing

 Date

Jul 14, 2023

 Participants

  • @Damian Borowiecki (Deactivated)

  • @Aneta Pałczyńska (Deactivated)

  • @Paweł Gesek

  • @Taylor Downs

  • @PSRAMKUMAR

  • @Vikash Madduri

  • @Satyajit Suri

  • @Valeria Tafoya

  • @Łukasz Ruzicki

 Goals

  • Discussing priorities, backlog refinement and other topics related to API Testing group

 Discussion topics

Item

Who

Discussion

Item

Who

Discussion

Updates

@Damian Borowiecki (Deactivated)

Further priorities

@Damian Borowiecki (Deactivated)

  • API Testing Roadmap

  • openIMIS integration into Digital Registries BB finalization

  • openIMIS integration into Payments BB

  • Continue working on Use Cases

Changes in APIs - how it should be addressed

@Paweł Gesek / @Damian Borowiecki (Deactivated)

UI redirects - BB Identity

@Paweł Gesek

  •  

Challenges with openIMIS adaptor for Digital Registry BB

@Łukasz Ruzicki

  • openIMIS is not fully compliant with Digital-Registry BB objective of being “multi-tenant platform where users can create and manage new registry databases. Each registry database created in the system will have automatically REST services generated." (definition from 4. key digital functionalities).

  • openIMIS still can serve as Digital-Registry for multiple use cases (including USCT) and proper adaptor module would enable users to map external data formats to the internal structures, but as long as they’re within certain domain (e.g. beneficiaries can be mapped, but digital-registry for car storage wouldn’t work) and “stretch” it for particular Use Cases.

  • Based on this conditions we should be fine with continuing development of the adaptor for the openIMIS Digital-Registry BB, and there’s no need to switch for another BB Implementation yet. Correctly created adaptor will make it easier to fine tune the openIMIS for multiple use case requirements.

AOB

 

  •  

 Action items

Action Items

Responsible party

Date

Action Items

Responsible party

Date

 

 

 

 

Meeting recording