Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • crown-core crown-core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 75
    • Issues 75
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Crown
  • crown-corecrown-core
  • Wiki
  • Quality assurance
  • Documents
  • Reporting Issues in GitLab

Last edited by Josh Wilcox Jun 21, 2018
Page history

Reporting Issues in GitLab

Crown Platform Test Plan

Version 0.1

17/01/2018

Chris Kibble

Document History** , Approval & Contributors**

1. Revision History

Version Revised By Date Status Release Notes
0.1 Chris Kibble 17/01/2018 Creation

1.2. Internal review

Role Name

1.3. Document Approval

Role Name Signature Date

1.4. Document Contributors

The following people contributed to the production of this document:

Role Name
Test Manager Chris Kibble

2. Glossary

Abbreviation Full Description
CRW Crown Platform

Issue Report – Template

Product:

Issue:

Steps to Reproduce:

Expected Behaviour:

Build Found In:

Priority:

Severity:

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 :

  1. Open desktop wallet
  2. Select Systemnode tab
  3. Select My Systemnodes
  4. Select New System
  5. Error

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: 1

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

Clone repository
  • 19.01.18 Testnet Fork Report
  • Credentials for electrumx servers
  • How to turn on off enforcement
  • Quality Assurance
  • Quality Assurance
    • Instant Send Testing
    • documents
  • Seed nodes
  • bounties
  • code of conduct
  • coding style guide
  • communications & marketing
  • community
  • community
    • Announcement Responsibilities
    • Developers
    • community built
View All Pages