// Run or design live-environment GenLayer tests for this intelligent-oracle repo.
Design, deploy, and monitor a GenLayer Intelligent Oracle prediction market from any coding agent. Use when a user wants to create a settled-by-web-evidence prediction market without opening the web UI.
Deploy GenLayer intelligent contracts using the deployment script. User-invoked only.
Write and run fast direct-mode pytest tests for this repo's GenLayer intelligent contracts.
Use the GenLayer CLI to inspect, interact with, and debug this repo's intelligent contracts.
Validate this repo's GenLayer intelligent contracts with the GenVM linter.
Run tests and build checks across the intelligent-oracle project. Use after making changes to validate nothing is broken.
| name | integration-tests |
| description | Run or design live-environment GenLayer tests for this intelligent-oracle repo. |
| allowed-tools | ["Bash","Read","Write","Edit"] |
Use this skill when contract behavior must be checked against a real GenLayer environment such as hosted Studio, local Studio, or a testnet.
The routine Python suite in this repo is direct-mode pytest under test/. There is currently no committed gltest.config.yaml or tests/integration/ scaffold. Do not invent one for routine verification unless the user asks for live integration coverage.
intelligent-contracts/scripts/https://studio.genlayer.com/apiGENLAYER_RPC_URL and NEXT_PUBLIC_GENLAYER_RPC_URLIC_REGISTRY_ADDRESS and NEXT_PUBLIC_IC_REGISTRY_ADDRESSDeploy the registry factory only when the user intends to write on-chain state:
cd scripts && npm install && cp .env.example .env && npm run deploy
Use the root Next app to exercise live create/resolve flows after env vars are configured:
npm run dev
Manual live checks:
/ creates a valid oracle config and calls /api/bridge/deploy-intelligent-oracle./explorer reads registry oracles through NEXT_PUBLIC_GENLAYER_RPC_URL./oracle/[address] reads get_dict, polls transactions, and calls resolve.Only add gltest integration tests when explicitly requested. If added, keep them separate from direct tests, for example:
tests/integration/
test_oracle_live_flow.py
gltest.config.yaml
The config should point contract_path at intelligent-contracts/, not a generic contracts/ folder.
Example shape:
contract_path: intelligent-contracts/
networks:
studionet: {}
localnet: {}
Run with visible output:
gltest tests/integration/ -v -s --network studionet
IntelligentOracle.resolve.Direct mode should cover most deterministic logic. Live tests are slower and can depend on external services, so keep them intentional.