Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test-plan-outline: update based on 2022-10-20 meeting #13

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

test-plan-outline: update based on 2022-10-20 meeting #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 24 additions & 3 deletions testing/test-plan-outline.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
= Omni Test Process Outline
Omni Team
v0.0.1, October 6, 2022: Early Draft
v0.0.2, October 20, 2022: Early Draft
:numbered:
:toc:
:toclevels: 2
Expand All @@ -11,15 +11,22 @@ Purpose blah blah

This document does not address desired or planned future features or the overall pace of development for new features.

[#dev-process]
== Development Process

=== TODO

. Keep up-to-date Bitcoin Core
. Get Spec up-to-date
. More up-front-documentation/specification (to drive test plan)
. More documentation and architecture reviews
. More frequent documentation and architecture reviews
. More code reviews
. Architectural changes to improve quality and testability
.. Improve OmniLayer Transaction Parsing
... Improved multithreading?
... Caching improvements?
... SQLite?
.. Move Omni Consensus code into C++ library for standalone testing


== Release Process/CI
Expand All @@ -29,19 +36,33 @@ This document does not address desired or planned future features or the overall

. Automated binary builds
. Automated Docker container build
. Dependent builds
. Automatically deploy builds to test Omniwallet environment, etc.
. Release candidates

== Automated Tests

=== Bitcoin Core Tests

=== Omni Tests
=== Existing Omni Core Tests

. OmniJ Spock RegTests
. OmniJ Spock Consensus Tests (not active, gone since Jenkins went offline)
. Python NFT tests written by Adam
. Python tests written by Peter?

=== Existing Application-level tests

. German has some Angular tests of OmniExplorer API


=== TODO Omni Tests

. Improve our test coverage
. Automated/Nightly test of MainNet full-sync (See "Architectural Changes" in <<dev-process>>)
. Ability to mirror MainNet tokens on RegTest (Sean started a tool to do this)
. Automatically test Omni Core builds with OmniEngine/Explorer/Wallet, OmniProxy, OmniBolt, etc. (see Integration Test section)


== Manual Tests

Expand Down