hackforla / hackforla/knowledgebase-content
Create a Guide/Template: Implementing Tests with Your Code Changes
- Vorherrschende Sprache
- Keine Sprachdaten
- Sterne
- 2
- Forks
- 1
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
### Overview
We need to create a guide to best practices for implementing tests with your code changes.
### Action Items
The phases in the guide-making process are listed below. Each phase displayed in blue is linked to a wiki page with instructions on how to complete that phase. Open the wiki page in a new tab, copy the instructions for each part into the section labeled 'Tasks' at the bottom of this issue, and complete each task listed.
- [ ] [Gather Examples Solo](https://github.com/hackforla/guides/wiki/How-to-Gather-Examples:-Solo) (open in a new tab)
- [ ] [Gather Examples Collaboratively](https://github.com/hackforla/guides/wiki/Phase-2-%E2%80%90-Gather-Examples-Collaboratively)
- [ ] [Create a Guide Draft](https://github.com/hackforla/guides/wiki/How-to-Draft-a-Guide)
- [ ] If needed, create a template
- [ ] [Have your guide peer reviewed](https://github.com/hackforla/guides/wiki/Peer-Reviews-for-Guides)
- [ ] [Present your guide for leadership review](https://github.com/hackforla/guides/wiki/Submitting-Your-Guide-for-Leadership-Review)
### Resources/Instructions
Google Drive Folder for this Guide’s documents and shortcuts (to documents in other locations) [0153 [DRAFT]Implementing Tests with Your Code Changes](https://drive.google.com/drive/folders/13LdpMqPH1RERTH_w_jCosEYSpYnhYGK8)
- [[DRAFT] Guide to Implementing Tests with Your Code Changes
](https://docs.google.com/document/d/1m5CLD6tF2zbPoMhQFsF7d7Rn6aHsxQnEwHeOytJKAl4/edit?tab=t.0#heading=h.5uyf3t2ubelq)
### Projects to Check
### Tasks
- [ ] This is where you will copy instructions from the wiki page for the step you are currently on.
Beitragsleitfaden
Rechercherichtung
Start with the linked Google Drive folder and the draft guide document, then review the linked wiki pages for each guide-making phase. Copy the relevant instructions into the Tasks section and work through example gathering, drafting, peer review, and leadership review. Done means the guide and any needed template have completed the listed review process.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Bereich
- documentation
- Issue-Typ
- Dokumentation
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100