14dcd29eee
author shashankshampi <shashank.sanket1995@gmail.com> 1729780155 +0530 committer shashankshampi <shashank.sanket1995@gmail.com> 1730274350 +0530 test: Code Migration from status-cli-tests fix_: functional tests (#5979) * fix_: generate on test-functional * chore(test)_: fix functional test assertion --------- Co-authored-by: Siddarth Kumar <siddarthkay@gmail.com> feat(accounts)_: cherry-pick Persist acceptance of Terms of Use & Privacy policy (#5766) (#5977) * feat(accounts)_: Persist acceptance of Terms of Use & Privacy policy (#5766) The original GH issue https://github.com/status-im/status-mobile/issues/21113 came from a request from the Legal team. We must show to Status v1 users the new terms (Terms of Use & Privacy Policy) right after they upgrade to Status v2 from the stores. The solution we use is to create a flag in the accounts table, named hasAcceptedTerms. The flag will be set to true on the first account ever created in v2 and we provide a native call in mobile/status.go#AcceptTerms, which allows the client to persist the user's choice in case they are upgrading (from v1 -> v2, or from a v2 older than this PR). This solution is not the best because we should store the setting in a separate table, not in the accounts table. Related Mobile PR https://github.com/status-im/status-mobile/pull/21124 * fix(test)_: Compare addresses using uppercased strings --------- Co-authored-by: Icaro Motta <icaro.ldm@gmail.com> test_: restore account (#5960) feat_: `LogOnPanic` linter (#5969) * feat_: LogOnPanic linter * fix_: add missing defer LogOnPanic * chore_: make vendor * fix_: tests, address pr comments * fix_: address pr comments fix(ci)_: remove workspace and tmp dir This ensures we do not encounter weird errors like: ``` + ln -s /home/jenkins/workspace/go_prs_linux_x86_64_main_PR-5907 /home/jenkins/workspace/go_prs_linux_x86_64_main_PR-5907@tmp/go/src/github.com/status-im/status-go ln: failed to create symbolic link '/home/jenkins/workspace/go_prs_linux_x86_64_main_PR-5907@tmp/go/src/github.com/status-im/status-go': File exists script returned exit code 1 ``` Signed-off-by: Jakub Sokołowski <jakub@status.im> chore_: enable windows and macos CI build (#5840) - Added support for Windows and macOS in CI pipelines - Added missing dependencies for Windows and x86-64-darwin - Resolved macOS SDK version compatibility for darwin-x86_64 The `mkShell` override was necessary to ensure compatibility with the newer macOS SDK (version 11.0) for x86_64. The default SDK (10.12) was causing build failures because of the missing libs and frameworks. OverrideSDK creates a mapping from the default SDK in all package categories to the requested SDK (11.0). fix(contacts)_: fix trust status not being saved to cache when changed (#5965) Fixes https://github.com/status-im/status-desktop/issues/16392 cleanup added logger and cleanup review comments changes fix_: functional tests (#5979) * fix_: generate on test-functional * chore(test)_: fix functional test assertion --------- Co-authored-by: Siddarth Kumar <siddarthkay@gmail.com> feat(accounts)_: cherry-pick Persist acceptance of Terms of Use & Privacy policy (#5766) (#5977) * feat(accounts)_: Persist acceptance of Terms of Use & Privacy policy (#5766) The original GH issue https://github.com/status-im/status-mobile/issues/21113 came from a request from the Legal team. We must show to Status v1 users the new terms (Terms of Use & Privacy Policy) right after they upgrade to Status v2 from the stores. The solution we use is to create a flag in the accounts table, named hasAcceptedTerms. The flag will be set to true on the first account ever created in v2 and we provide a native call in mobile/status.go#AcceptTerms, which allows the client to persist the user's choice in case they are upgrading (from v1 -> v2, or from a v2 older than this PR). This solution is not the best because we should store the setting in a separate table, not in the accounts table. Related Mobile PR https://github.com/status-im/status-mobile/pull/21124 * fix(test)_: Compare addresses using uppercased strings --------- Co-authored-by: Icaro Motta <icaro.ldm@gmail.com> test_: restore account (#5960) feat_: `LogOnPanic` linter (#5969) * feat_: LogOnPanic linter * fix_: add missing defer LogOnPanic * chore_: make vendor * fix_: tests, address pr comments * fix_: address pr comments chore_: enable windows and macos CI build (#5840) - Added support for Windows and macOS in CI pipelines - Added missing dependencies for Windows and x86-64-darwin - Resolved macOS SDK version compatibility for darwin-x86_64 The `mkShell` override was necessary to ensure compatibility with the newer macOS SDK (version 11.0) for x86_64. The default SDK (10.12) was causing build failures because of the missing libs and frameworks. OverrideSDK creates a mapping from the default SDK in all package categories to the requested SDK (11.0). fix(contacts)_: fix trust status not being saved to cache when changed (#5965) Fixes https://github.com/status-im/status-desktop/issues/16392 test_: remove port bind chore(wallet)_: move route execution code to separate module chore_: replace geth logger with zap logger (#5962) closes: #6002 feat(telemetry)_: add metrics for message reliability (#5899) * feat(telemetry)_: track message reliability Add metrics for dial errors, missed messages, missed relevant messages, and confirmed delivery. * fix_: handle error from json marshal chore_: use zap logger as request logger iterates: status-im/status-desktop#16536 test_: unique project per run test_: use docker compose v2, more concrete project name fix(codecov)_: ignore folders without tests Otherwise Codecov reports incorrect numbers when making changes. https://docs.codecov.com/docs/ignoring-paths Signed-off-by: Jakub Sokołowski <jakub@status.im> test_: verify schema of signals during init; fix schema verification warnings (#5947) fix_: update defaultGorushURL (#6011) fix(tests)_: use non-standard port to avoid conflicts We have observed `nimbus-eth2` build failures reporting this port: ```json { "lvl": "NTC", "ts": "2024-10-28 13:51:32.308+00:00", "msg": "REST HTTP server could not be started", "topics": "beacnde", "address": "127.0.0.1:5432", "reason": "(98) Address already in use" } ``` https://ci.status.im/job/nimbus-eth2/job/platforms/job/linux/job/x86_64/job/main/job/PR-6683/3/ Signed-off-by: Jakub Sokołowski <jakub@status.im> fix_: create request logger ad-hoc in tests Fixes `TestCall` failing when run concurrently. chore_: configure codecov (#6005) * chore_: configure codecov * fix_: after_n_builds |
||
---|---|---|
.. | ||
clients | ||
schemas | ||
src | ||
tests | ||
validators | ||
.gitignore | ||
Dockerfile | ||
Dockerfile.tests-rpc | ||
README.MD | ||
config.json | ||
conftest.py | ||
constants.py | ||
docker-compose.anvil.yml | ||
docker-compose.status-go.local.yml | ||
docker-compose.test.status-go.yml | ||
entrypoint.sh | ||
pytest.ini | ||
requirements.txt | ||
schema_builder.py |
README.MD
Here’s the updated README with the additional prerequisites and instructions:
Overview
Functional tests for status-go
Table of Contents
How to Install
- Install Docker and Docker Compose
- Install Python 3.10.14
- Set up a virtual environment (recommended):
- In
./tests-functional
, run:python -m venv .venv source .venv/bin/activate pip install -r requirements.txt
- Optional (for test development): Use Python virtual environment for better dependency management. You can follow the guide here
- In
- Install pre-commit hooks (optional):
pre-commit install
How to Run
Running dev RPC (Anvil with contracts)
In ./tests-functional
:
docker compose -f docker-compose.anvil.yml up --remove-orphans --build
This command will:
- Start an Anvil container with ChainID
31337
, exposed on0.0.0.0:8545
- Deploy Status-im contracts to the Anvil network
Running Tests
To run the tests:
-
In
./tests-functional
, start the testing containers:docker compose -f docker-compose.anvil.yml -f docker-compose.test.status-go.yml -f docker-compose.status-go.local.yml up --build --remove-orphans
This command will:
- Create a container with status-go as daemon, exposing
APIModules
on0.0.0.0:3333
- Configure
status-go
to use Anvil as theRPCURL
with ChainID31337
- Deploy all Status-im contracts to the Anvil network
- Create a container with status-go as daemon, exposing
-
To execute tests:
- Run all tests:
pytest
- Run tests marked as
wallet
:pytest -m wallet
- Run a specific test:
pytest -k "test_contact_request_baseline"
- Run all tests:
Implementation Details
-
Functional tests are implemented in
./tests-functional/tests
using pytest. -
Each test performs two types of verifications:
verify_is_valid_json_rpc_response()
: Checks for a status code200
, a non-empty response, JSON-RPC structure, presence of theresult
field, and the expected ID.jsonschema.validate()
: Validates that the response contains expected data, including required fields and types. Schemas are stored in/schemas/wallet_MethodName
.
-
Schema Generation:
- New schemas can be generated with
./tests-functional/schema_builder.py
by passing a response to theCustomSchemaBuilder(schema_name).create_schema(response.json())
method. This should be used only during test creation. - Search
how to create schema:
in test files for examples.
- New schemas can be generated with
Build Status Backend
You can build the binary with the following command in the status-go
root directory:
make status-backend
For further details on building and setting up status-go
and status-backend
, refer to the official documentation:
Location of the binary: cmd/status-backend/status-backend
This README should cover your additional setup, installation, and testing instructions with clear steps for users. Let me know if there are any further modifications needed!