[QoS][E2E & Load Testing] Move Service-Specific E2E Test Logic into QoS Modules
@adshmh is already working on this.
Since May 29, 2025.
Assessment
This issue has not been assessed yet.
Description
Objective
Incorporate service method-specific logic that was created for the purposes of the PATH E2E & Load Tests (e2e package) into the QoS modules.
Origin Document
PR Review comments from @adshmh here:
https://github.com/buildwithgrove/path/pull/274#pullrequestreview-2878035938
NOTE - This should be done as part of the JUDGE refactor.
Goals
Much of the logic that was created for the purposes of allowing comprehensive testing of services (for example EVM blockchains) will actually be quite valuable in performing detailed method-specific functionality inside specific QoS packages.
As an example, the EVM qos package could perform the work of:
- storing all EVM methods that could be tested (
eth_getBalance, etc.) - constructing the params for these methods
- validating both the request and response per-method
Deliverables
- QoS-applicable logic moved from
e2etoqos/** - service configurations (YAML file) moved from
e2e/config/ toconfig
General deliverables
- Comments: Add/update TODOs and comments alongside the source code so it is easier to follow.
- Testing: Add new tests (unit and/or E2E) to the test suite.
- Makefile: Add new targets to the Makefile to make the new functionality easier to use.
- Documentation: Update architectural or development READMEs; use mermaid diagrams where appropriate.
Creator: @commoddity
Co-Owners: @adshmh @Olshansk
- Dominant language
- Go
- Stars
- 12
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pokt-network/path
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
pokt-network/path#509 ·
-
bug gateway
Difficulty 4/5 3-5 days Newbie friendliness 45/100
pokt-network/path#477 ·
-
config documentation evm portal-db portal-ui qos
Difficulty 4/5 3-5 days Newbie friendliness 48/100
pokt-network/path#475 · 1 comment ·
-
[RADIX][TRON][SUPPLIER] Suppliers should not have to append additional API paths in their RM configMay be free again @adshmh claimed this 405 days ago, and no pull request is open. Openqos
pokt-network/path#443 · 1 comment · 3 assignees ·
-
[PORTALDB][CONFIG] Surface sanctions settings and thresholds as configurables in both the Config files and Portal DBMay be free again @commoddity claimed this 428 days ago, and no pull request is open. Openconfig documentation portal-ui qos
pokt-network/path#409 · 1 assignee ·
All issues in pokt-network/path
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Rafaeldelinares/gentle-mesh#125 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Gentleman-Programming/gentle-ai#5643 ·
Maintainers usually reply within 1 day
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
FootprintAI/Containarium#2869 ·
Maintainers usually reply within 1 day
-
kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kubevirt/kubevirt#19559 · 1 reaction ·
Maintainers usually reply within 1 day
-
bug raised-by:verifier
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
medici-finance/assay#3817 ·
Maintainers usually reply within 1 day