API self-serve: QA Testing

[Abi-Nada]

[Draft card]

[timarney]

Noting for QA --- testing without using the actual API

We can mimic using the API by performing actions i.e. download, confirm etc... using "vault mode" i.e form without an API key generated.

For example to test "API confirmed page"

• Create a form

• Keeps response delivery as "vault"

• Create some test responses

• Confirm the responses (still using vault setup) ...

• You now have confirmed responses

• Generate an API key ... Your now in API "mode" ...

• Re-visit the responses page

• You should now see the API responses "confirmed page"

---

New "never confirmed"

• Create a form
• Generate a key
• Create some test responses
• You should land on "new responses available via API" card view ...

New "no responses"

• Create a form

• Generate a key

• Create some test responses

• You should land on "noresponses available" API card view

---

"Mixed" ---

• Perform the steps for "API confirmed page" .... but don't confirm them all
• You should now have confirmed and new submissions waiting
• Ensure view indicates confirmed + has a status box for "new" awaiting download.

[Abi-Nada]

Before QA Testing: Check in with @bryan-robitaille on updating the IDP and the project ID

[timarney]

For local testing

I tested 6 different possible states for the API responses page

A)

B)

C)

D)

E)

F)

[anikbrazeau]

Some states we might want to test:

• [ ] Draft form using all form elements, pages and branching
• [ ] Publishing a form with API response delivery
• [ ] Submitting and retrieving responses in English
• [ ] Submitting and retrieving responses in French
• [ ] Switching response delivery method from email to API
• [ ] Switching response delivery method from download to API
• [ ] Switching response delivery method from API to download