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
  • testing definition of done

Last edited by Josh Wilcox Jun 21, 2018
Page history

testing definition of done

Crown Platform Definition of Done – Testing

Version 0.1

09/01/2018

Chris Kibble

Document History** , Approval & Contributors**

1.1. Revision History

Version Revised By Date Status Release Notes
0.1 Chris Kibble 09/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

3. Definition of Done

Documentation

All Test Cases are up to date, including defects found and added to the test case library

All BDD's up to date, including defects found and added to the test case library

Release material is up to date and reviewed by 2 members

Risk has been documented, the team are aware of possible risks and mitigations or work arounds

We have a rollback plan

Unit Testing

100% Unit testing coverage reviewed by 2 members

All Unit tests checked in

All Unit tests run fully automated

Integration

100% testing coverage between isolated instances

All Integration tests checked in

All Integration tests run fully automated

Feature

Any remaining defects documented and approved by 3 members as acceptable otherwise they must be resolved

Test coverage has met 100%

Demo / Review must be approved by 3 members as acceptable

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