June 16, 2023 API Testing

 Date

Jun 16, 2023

 Participants

  • @Dominika Bieńkowska (Deactivated)

  • @Karolina Kopacz (Deactivated)

  • @Damian Borowiecki (Deactivated)

  • @Paweł Gesek

  • @Michał Dulko (Deactivated)

  • Łukasz Ruzicki

  • @Satyajit Suri

  • @Steve Conrad

  • @Taylor Downs

  • @Benjamin Balder Bach

  • @PSRAMKUMAR

  • @Valeria Tafoya

 Goals

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

 Discussion topics

Agenda

Discussion

Agenda

Discussion

Update from SolDevelo

Further priorities

Introduction of standards to APIs (like FHIR)

  • Digital Registries APIs require birth certificate which is not right

  • We should discuss it with Ingmar, this should be optional field a not required

  •  

Mapping test data to openIMIS

  • Registers, multiple databases, fields with other data type or no coverage like BirthcertificateID

AOB

  • How should we deal with parameters such as authentication code or token that require a data f?

    • Candidates should provide login API and data from it should be used in endpoints that require such data

    • Taylor: It stores an updated connection and a registered user in the test context.

      • def register_and_log_in_user(%{conn: conn}) do user = Lightning.AccountsFixtures.user_fixture() %{conn: log_in_user(conn, user), user: user} end

    • Extend the contract of setup.sh --config 'suite-a' so that instead of merely returning OK it should return { status: "ready", apiToken: "abc123", ...otherStuff }

  • BB Scheduler reviews

  • Can we use Benjamin’s automated approach for mock application?

    • Benjamin would need to add some comments

 Action items

Action Items

Responsible party

Date

Action Items

Responsible party

Date

 

 

 

 

Meeting recording