...
How should we incorporate developer written unit testing into tickets appropriately?
For API tests:
Role based testing
What is the appropriate level of hands-on / hands-off guidance for contributors?
Contrib channel is a great way for some people
For meet-n-greets with new contributors, loop in one of the engineers to be their technical point of contact
Are we writing API tests? The instruction for running tests in the Readme didn't work for me (I would like to update it)
Start doing | Stop doing | Keep doing | Shout outs |
---|---|---|---|
|
|
| |
| |||
| Thank you everyone for the warm welcome! | ||
| |||
Action items:
- Sayaka Ono: Update to Readme for running API tests
- Lite Farm to add a ticket to Update API doc (https://api.beta.litefarm.org/api-docs/#/)
- Sayaka Ono to do a knowledge transfer session with Duncan Brain and Mwayanjana Bolokonya (Unlicensed) on jest testing
- Mwayanjana Bolokonya (Unlicensed) to create a Confluence document to help people set up local testing
- Duncan Brain to put together a 1-pager to give contributors so they can self-classify
Persona 1: Total newbie, never worked on production code. Maybe self-taught or a boot camp
Persona 2: Some experience on a team,
Persona 3: No issues slotting in, comfortable with open source
- Mwayanjana Bolokonya (Unlicensed): Verify and update (Mwayanjana Bolokonya (Unlicensed) to find doc) to include Github Actions automations. Kevin believes backlog → Development (when creating branch from Jira) and development → verification (when a branch is merged into integration) are automated.
- Lite Farm to add complexity levels to tickets