This change replaces with "Storj" all instances of "Storj DCS" or
"Storj OSP".
Issues: storj/storj-private#479
#5069 and #5839
Change-Id: I78d13f2abd8bde5d2cb42d8006016ee87130a566
* doc(testplan): storj private cloud
* Update storj-private-cloud-testplan.md
this commit pushes the content to the template file and removes unused sections.
This testplan is going to cover the changes to allow for scaling audit workers. It will go over the scaling audit worker design doc found under blueprints.
Co-authored-by: Antonio Franco (He/Him) <antonio@storj.io>
* docs/testplan: Testplan for Automatic Account Freeze-Unfreeze
This testplan is going to cover the new account Freeze/Unfreeze. It will go over the automatic-account-freeze design doc found under docs/blueprints.
* Update automatic-account-freeze-unfreeze.md
Co-authored-by: Antonio Franco (He/Him) <antonio@storj.io>
This testplan is going to cover the changes to storage-node email notifications. It will go over the storage-node email notification design doc.
Co-authored-by: Antonio Franco (He/Him) <antonio@storj.io>
* docs/testplan: Adding a testplan for Token Payment Processor
This testplan is going to cover the token payment processor, it will go over must haves and additional features that we can add on later.
* docs/testplan: Adding a testplan for Token Payment Processor
Updated final testplan for review
* docs/testplan: Adding a testplan for Token Payment Processor
Removed unnecessary tests related to mempool scanning
* Update token-payment-processor-testplan.md
Co-authored-by: littleskunk <jens.heimbuerge@googlemail.com>
* This commit stubs out the test plan for fuzz testing.
* pushing small change before rebasing.
* This commit implements a rough draft of our security tests, most importantly fuzz tests.
* Moving testplan up a directory and renaming to indicate executive summary.
* Cleaning out fuzzing tests from cmd/uplink,
* updates to tools list
Added a testplan folder in docs, with a README and TEMPLATE for testplan
We want community involvement with testplans, since we believe that testplans written as early as possible before implementation starts work like a checklist and as soon as we finish the implementation we can compare it to the test plan to check for any bugs. Also even before implementation is finished, if a developer can read a test plan beforehand they can prevent most bugs, hence why we believe that the earlier we write a test plan the more bugs we can prevent.
Co-authored-by: Igor <38665104+ihaid@users.noreply.github.com>
