November 25th, 2022 - Testing Team Meeting Note

Attendees

@Dominika Bieńkowska (Deactivated)
@Esther Ogunjimi
@Damian Szafranek
@Damian Borowiecki (Deactivated)
@Karolina Kopacz (Deactivated)
@Kamil Piotrowski (Deactivated)
@Paweł Gesek
@Satyajit Suri
@Taylor Downs
@Sreepathy
Vishwa
@Martin Karner
@Ingmar Vali
@Jaume DUBOIS

Meeting Link

Attendees

Agenda

Presenter

Duration

Status

Update on activities involved in the BB API spec development and API testing effort

BB Leads

 

Update timelines of activities in Tracking Pipeline for API Development and API Test Activities

Demo of Mock Server for BB API Testing

 

 

Github repository - https://github.com/sreepathysois/Mockoon_CLI_MockServer_BB_OpenAPI_Spec_Test_Updated

IM Integration Testing Approach

 

 

 

Q&A

 

 

  1. What technologies have/should be used when creating mocks - do we want to make more generic and similar architecture and simple api for each BB, or maybe a proof of concept in several technologies, e.g. django/fastapi/node.js for different repos?


  2. How advanced should the API mocks be - only handling and validation of requests, or maybe additionally a database for more advanced test cases requiring several queries to test the entire 'journey'?


  3. Automated tests to check compliance of external systems with blocks - so far we have talked about integration with CircleCI. Are there any examples (e.g. for existing mocks) of calling these tests for existing systems or will we be doing this from scratch? What is the scope of that? We assume external systems will be different enough to make one general solution difficult, should we plan to create boilerplates for CI/CD calls? If so, do we limit ourselves to CircleCI or do we also take into account e.g. github workflows?


  4. Can we get access to CI/CD services?


  5. Are there any applications that are currently on the other side of BB (they don't use the API, but have services mapped to endpoints that are described by our schemas)? Does it matter to us in the context of tests how the implementations are connected to check the compatibility or should we base on what's already there and working well?


  6. Who is the main person approving the quality of the solution? What does the acceptance process look like? Are there any standards for architecture and code? It seems that there is no workflow used in branches. Can we give some advice here? Also are there any style guidelines? We propose to add tools such as eslint to maintain the quality of code better.


  7. How are test cases created in gherkin? Who is responsible for writing them, will there be only technical support on our side, or should we also write test cases? (example in this file test/features/detail-instance.feature)


  8. Assuming that many BB teams will want our support, how should we prioritize all the work?


  9. Can we choose the technology for the application? What we propose as the best approach is to use Python on backend and React with Typescript and Next.js on frontend.


  10. Would this app be a separate and independent one beside the GovStack website?

Meeting Recording

 

Action Items

Decisions