Jul 21, 2022

Jul 28, 2022

Aug 4, 2022

 Risk, Jira, Confluence and way to report weeklies on Confluence and recommending to have cumulative way, which allows to have access to whole history, to have a precise follow-up and to write little notes each time.

 @Esther Ogunjimi - 15 minutes

 @Jake Watson @Jaume DUBOIS @Esther Ogunjimi (Unlicensed) will collaborate outside of the meeting

 Mapping Backlog/Roadmap activities to Jira . List of APIs aligned to current BB specs. Prioritize first API from each BB to be taken up for testing.  List of  functional specifications to be added /refined in BB specs in next quarter. Mapping resource needs in all Groups  to achieve these

BB Leads - 60 minutes

 @Max Carlson approved the test approach. As suggested by @PSRAMKUMAR for the BB leads to come up with plan for the next release of BB specifications for the next quarter. The BB leads can focus on the roadmap - work to do with test plan, stubs etc. Focus should be on having a concrete road map for each BB.

@Aleksander Reitsakas Test approach for information mediator needs to be separate because the BB is hosted in other system.

@Taylor Downs is there a plan to test various application compliances with information mediator specification?

@Aleksander Reitsakas there is an overall plan and the sandbox setup script so as to be able to install.

Use cases will be installed in the same environment and test that they are working.

The UCs need to have two parties which communicate to each other.

IM and Registration are exempted from test plan as they require a divergent approach for their test plan.

Test set up is manual and can be repeated because the testing of IM requires multiple infrastructure through different machine. Communication cannot be unit test.

@Max Carlson Registration BB doesn’t have open API to test using the test plan. The best way to test Registration and IM BB might be to have a specific sandbox use case and add end to end test around that - this is integration testing and not unit testing. This will help to validate compliance.

Registration API can be tested but not the whole BB can be tested.

Any registration product GovStack will support or recommend should have accessibility API support.

Product accreditation will be carried out iteratively.

@Jake Watson The current focus writing the functional back box test of the BB. Integration testing will be complicated to write because of the need to synchronize the data set across the BB to support various UCs. Integration and interoperability testing will come later.

Here is the link to the test doc by @Taylor Downs

The real value of the specifications is to break the current way products are procured and allowing the global system integrators to participate more.

There will be presentation from the marketplace and catalogue team.

Conclude discussion on process for API test pipeline

@Jake Watson @Taylor Downs @PSRAMKUMAR @Max Carlson & BB Leads - 10 minutes

There is a consensus on the test plan.

Identify one big exemption with Information Mediator.

Registration BB does not have lot of APIs for testing and will tilt toward functional testing and that will come later.

@Taylor Downs submitted a PR for the registration test plan: https://github.com/GovStackWorkingGroup/bb-registration/pull/3 . Information Mediator cannot be tested using this plan since it needs to be deployed on lots of different servers.

Open Issues

5 minutes

AOB