April 28, 2023 API Testing

Update from SolDevelo

• https://govstack-global.atlassian.net/wiki/spaces/GH/pages/125370373

• http://testing.govstack.global/

• Tests:

  • Payments BB G2P AWAITING REVIEW

  • Identity BB blocked

  • Digital Registries - 4 PRs AWAITING REVIEW on hold

• USCT Use Case

  • Outreach Communication Step

Further priorities

• https://govstack-global.atlassian.net/wiki/spaces/GH/pages/177274939

• Tests

  • TOP PRIORITY

  • Payments BB G2P - Apr 21, 2023

  • Identity BB - May 10, 2023

  • next priorities

  • Registration BB - May 19, 2023

  • Digital Registries BB improvements May 16, 2023

• USCT Use Case in progress

  • Outreach Communication Step

• App on hold until top priority tests are done

Identity BB Block

Conclusion: We shouldn’t call UI to retrieve auth code in scope of API Spec suite. Instead, in this type of scenario we should use some fixed token and expect test candidate to make it work. For instance if test expects “tokenABC” to be a valid token, then during candidate application setup it should be ensured that tested solution can work with it.

Gherkin spec

• Difference between data seeded testing and data structure testing.
  https://docs.google.com/presentation/d/1QWQQSxSIOEIElzJMbyZDaPhooW7ULRE0j5MZHLg6Ud8/edit?usp=sharing

• In Workflow BB data structure tests are preformed. However not all building blocks might be compliant with that approach.

• Structure validation test doesn’t expect the candidate application to provide the test data we expect in seeded tests.

• We should constantly improving test format. The tests that are invoked should be closely related to how we define compliance of the implementation with compliance.

• We could split data structure and data content tests in the test harness.