[FIP-nn] QA - Milestone Checklist
- Eric Butz
The milestone checklist tracks the QA tasks that need to be completed for new features
Task |
| Checklist | Status / Deliverables |
|---|---|---|---|
Links |
|
|
|
QA Epic or Story |
|
|
|
QA Test Plan |
|
|
|
Scoping |
| Project manager will create initial QA epic or story Create QA stories and subtasks for items in Feature QA Milestone Checklist Estimate stories |
|
Test Plan |
|
|
|
Create Test Cases | Excluded Included | Document test cases in Jira List out all the test cases in a subtask attached to the QA story |
|
Meeting - Test plan review | Excluded Included | Meeting held with Dev Manager and Lead Dev to review test plan |
|
Feature Testing |
|
|
|
fio.test branch | Excluded Included |
| |
Feature Testing |
| ||
Performance testing |
| ||
History node testing | For transactions that automatically create accounts (e.g., regdomain) if the public key used is new, we need to make sure that the correct entries are added to the the history_plugin.cpp. See for example: [FIP-42] Chain plugin API updates by adsorptionenthalpy · Pull Request #363 · fioprotocol/fio To test, the transaction should be run, and a history get_actions for the target account should show the (regdomain, etc.) action. When released to testnet, it should be confirmed that bloks.io shows the appropriate transaction history. |
| |
Meeting - Testing code and results review |
| ||
UAT |
|
|
|
Merge to develop and install on DEV |
| ||
QA complete |
|