Page MenuHomePhabricator

[Cashtab] Standardize testing regime
ClosedPublic

Authored by emack on Jan 22 2022, 02:42.

Details

Reviewers
bytesofman
Group Reviewers
Restricted Project
Commits
rABC128c55c78820: [Cashtab] Standardize testing regime
Summary

As part of code quality assurance, there is a need to develop a minimum test plan for Cashtab that touches on:

  • interactions with fresh new wallets
  • interactions with wallets which have old TXs relevant to the diff
  • regression testing of functions relating to the diff
  • cross browser compatibility beyond chrome
  • testing on physical mobile devices

We've seen some edge cases recently around these scenarios so will be ideal to have a consistent minimum test plan coverage before the Diff gets to reviewers. This will become more important as we onboard more developers and reviewers get busier.

Manifest: T2041

Test Plan

Diff Detail

Repository
rABC Bitcoin ABC
Branch
webTestingGuidelines
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 17971
Build 35764: Build Diffcashtab-tests
Build 35763: arc lint + arc unit

Event Timeline

emack requested review of this revision.Jan 22 2022, 02:42
bytesofman added inline comments.
web/cashtab/README.md
27

While this is true, I think we should keep it out of the README. Want the content to be as procedure dense as possible with specific relevance to this repo.

31

Existing functions that impacted by your diff must be regression tested to ensure no unintended behavior. For example, if you're adding a function to facilitate One To Many XEC transactions, you must test that the existing One to One XEC transactions work as intended.

76

This includes but is not limited to:

This revision now requires changes to proceed.Jan 24 2022, 20:53
emack marked 3 inline comments as done.

Updates to README

This revision is now accepted and ready to land.Jan 25 2022, 16:06
This revision was automatically updated to reflect the committed changes.