Skip to content
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.
/ beta-testing Public archive

πŸ› Report all the bug found during beta testing

Notifications You must be signed in to change notification settings

spheronFdn/beta-testing

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

12 Commits
Β 
Β 
Β 
Β 

Repository files navigation

Spheron Beta Testing Program

Launching the Spheron Beta Testing Program to find bugs and vulnerabilities in our system and get some important feedback for the new web app.

How can I participate?

It's is open to everyone, you just have to raise an issue at https://github.com/argoapp-live/beta-testing using the bug report template. Tester must fill all the details in the bug report template to be eligible

When will I start finding the bugs?

The bug testing program is starting from 14 April 2022. To start off, you need to visit our aqua release (https://aqua.spheron.network/). You will be already whitelisted in our NFT contract, you can mint 1 NFT and start accessing the platform.

Here is the changelog note for our Aqua Release: https://drive.google.com/file/d/1oL7fuguL_O1T6nXisqUAaKH_QAjVg5sp/view?usp=sharing All the previous features are all in place but these new features are added in the platform. Test end-to-end even the older feature.

What will be the process of highlighting the bugs?

  • Bug must be raised on GitHub by going to the issue, then create a new issue.
  • Choose the bug report template and fill all the detail properly.
  • Please mark the of the bug by labeling the issue with any of these low, high, critical
  • For UI related issue, use ui-bug as label and for API related issue, use api-bug as label
  • Must add criticality label for any issue raised - critical or high or low

What will be the different criticality levels of the bugs?

There will be three types of bug that participants can find in the system:

  • Critical: (bugs that can stop our entire system) - System Issue, Smart Contract Bug, Security Vulnerability, UI Crash, etc.
  • High: (bugs that will not create any loss but improve the system) - Security Issues (but will not create that impact which critical can), System Issue (ex false data), Smart Contract Bug, UI issue (this will be bugs that will create a user confusion related to funds and other features)
  • Low: (bugs that will not cause any big issue but it’s good to have them rectified) - UI issues (ex formatting issues, component load issue, refresh issues), Security Issue

Social Media

About

πŸ› Report all the bug found during beta testing

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published