bitshares / bitshares/bitshares-ui
QA Proposal: Test Scripts
- Dominant language
- JavaScript
- Stars
- 520
- Forks
- 575
- Avg merge
- 12h 7m
- Merged PRs (30d)
- 5
Description
I'm in the process of creating a test script environment, which would allow us to test standard processes prior to a new live wallet release.
Plan is to create test scripts as we proceed in the wallet releases
Please give me layout feedback: https://docs.google.com/spreadsheets/d/1qtqUQlIkFRw5rLi8vSGITsuRSglH3RYXDZhjOE0I_gY/edit?usp=sharing
* So basically add 1-2 days to a new wallet release for testing, anyone interested could copy the current test script sheet and do the testing.
* Open a github issue under version number so that testers can submit the sheet link filtered to FAIL.
* UI devs could browse through the logs and come back for feedback or try to reproduce
Contributor guide
Research direction
Start with the linked Google spreadsheet and review the proposed wallet-release testing workflow. The issue does not name repository files, tests, or an implementation entry point, so clarify the target release process and repository integration before starting. Done would be an agreed test-script layout and a documented way for testers to submit FAIL results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100