Crown Platform Test Plan
Document History** , Approval & Contributors**
1. Revision History
|Version||Revised By||Date||Status||Release Notes|
1.2. Internal review
1.3. Document Approval
1.4. Document Contributors
The following people contributed to the production of this document:
|Test Manager||Chris Kibble|
Issue Report – Template
Steps to Reproduce:
Build Found In:
Issue Report – Explanation
Product : Desktop Wallet x64, Windows 10
We have a lot of products and I only see this expanding. We'll have API's, crown.tech, crown.today, iOS and Android products.
Issue : Selecting New Systemnode causes an error
This is the issue header which will outline the actual defect we're trying to resolve.
Steps to Reproduce :
- Open desktop wallet
- Select Systemnode tab
- Select My Systemnodes
- Select New System
The steps to recreate exactly how the error occurred when you found the issue.
Expected Behaviour: The wallet should not error and I should see a popup for a new systemnode
The expected behaviour is to tell the developer what you would expect to see instead of the issue. This can be useful as it may trigger a conversation between yourself and the developer (or the team) about a better fix or possible solutions.
Build Found In : 00.12.03.03
This is very important as you may be using an old test build and the issue may already have been resolved.
Priority : 2
Priority explained as 1 = Must fix immediately as it's blocking testing, 2 = Must fix before the next test release, 3 = must fix before release candidate, 4 = Fix in test if we have time
Severity explained as 1 = Crash or Error causing a block, 2 – Crash or error but we have a work around, 3 = defect which needs to be fixed before release candidate, 4 = defect which can be fixed on test if we have time