QA/ Integration related issues #162

Closed
opened 2024-11-06 10:47:16 +01:00 by kamikazechaser · 7 comments
  • The Africastalking POST route should be settable via an env/flag
    - [ ] The Africastalking server should (structured) log errors from any handlers it executes (See #165)
- [x] The Africastalking POST route should be settable via an env/flag ~~- [ ] The Africastalking server should (structured) log errors from any handlers it executes~~ (See #165)
kamikazechaser added the
Activity
Doing
devops
labels 2024-11-06 10:47:33 +01:00
carlos was assigned by kamikazechaser 2024-11-06 10:47:38 +01:00
Alfred-mk was assigned by kamikazechaser 2024-11-06 10:47:38 +01:00
kamikazechaser changed title from QA/Intergation related issues to QA/ Integration related issues 2024-11-06 10:47:49 +01:00
Author
Owner
  • Document requirements to build .vis files into .bin files in the README.md
- [x] Document requirements to build .vis files into .bin files in the README.md
Author
Owner

Low priority

Currently the services folder contains one registration folder with all .vise files. They should be grouped by menu hierarchy to allow easy development from anyone willing to contribute. The go-vise assembler expects a file + preprocessor data to produce an stdout.

Certain features can be added to go-vise to make this process available as a library.

## Low priority Currently the services folder contains one `registration` folder with all `.vise` files. They should be grouped by menu hierarchy to allow easy development from anyone willing to contribute. The go-vise assembler expects a file + preprocessor data to produce an stdout. Certain features can be added to go-vise to make this process available as a library.
Author
Owner
  • Document libdgbm requirements for local development on Linux distros.
- [ ] Document libdgbm requirements for local development on Linux distros.
Author
Owner
  • Balance should update on next session (Is the separate service suppose to do this?) [BLOCKED, get term service up and running]
  • Placeholders for send to blockchain address and alias
  • Placeholders for token details which are usually obtained from the "graph" db/sarafu.network
  • Remove balance value when selecting token
  • Implement last10tx (option 4 in my profile)
  • Implement balances (option 3 in my profile)
- [x] Balance should update on next session (Is the separate service suppose to do this?) [BLOCKED, get `term` service up and running] - [x] Placeholders for send to blockchain address and alias - [x] Placeholders for token details which are usually obtained from the "graph" db/sarafu.network - [x] Remove balance value when selecting token - [x] Implement last10tx (option 4 in my profile) - [x] Implement balances (option 3 in my profile)
Author
Owner

USSD data service updates

  • For alias resolution: Use the api/v1/alias/:alias endpoint and decode with the AliasAddress struct
  • Token holdings now alos returns tokenCommodity and tokenLocation
### USSD data service updates * For alias resolution: Use the `api/v1/alias/:alias` endpoint and decode with the `AliasAddress` struct * Token holdings now alos returns `tokenCommodity` and `tokenLocation`
kamikazechaser pinned this 2024-11-25 07:59:47 +01:00
Author
Owner

Test sending of vouchers to:

  • Registered and activated phone numbers
  • Alias, if successfully resolved
  • Blockchain address (Usually without any validation, except the length, can be checksummed on USSD end before submitting to the custodial service)
Test sending of vouchers to: - [x] Registered and activated phone numbers - [x] Alias, if successfully resolved - [x] Blockchain address (Usually without any validation, except the length, can be checksummed on USSD end before submitting to the custodial service)
Owner

closed and let's do individual issues for the rest?

closed and let's do individual issues for the rest?
lash closed this issue 2024-12-10 11:20:36 +01:00
lash unpinned this 2024-12-11 12:20:53 +01:00
Sign in to join this conversation.
No Milestone
No project
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: urdt/ussd#162
No description provided.