[FIP-nn] QA - Milestone Checklist
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 | Branch for new tests created on fio.test |
|
Feature Testing | Excluded Included | fio.test enhanced with functional tests Tests run cleanly Functional tests well documented (in fio.test) and reviewed with team |
|
Performance testing | Excluded Included | Work with Dev Lead to create performance test plan fio.test enhanced with performance tests |
|
History node testing | Excluded Included | Test against node with V1 History and confirm no errors in log file (add results to Dev Spec) 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 | Excluded Included | System and performance tests and results reviewed with Dev team |
|
UAT |
|
|
|
Merge to develop and install on DEV | Excluded Included | Rebase feature branch and merge to develop for UAT testing Install release on DEV server |
|
QA complete | Excluded Included | All bugs and outstanding items completed JS tests completed and run cleanly against DEV server |
|