integration-tests
SolidWrite and run integration tests against a GenLayer environment.
Testing & QA 4,294 stars
90 forks Updated yesterday NOASSERTION
Install
Quality Score: 86/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
# Integration Tests
Run contracts against a real GenLayer environment (GLSim, Studio, or testnet) with full consensus validation.
## Running Tests
```bash
# Against default network (from gltest.config.yaml)
gltest tests/integration/ -v -s
# Against specific network
gltest tests/integration/ -v -s --network localnet
gltest tests/integration/ -v -s --network studionet
gltest tests/integration/ -v -s --network testnet_bradbury
```
Always use `-v -s` for visible output during development.
## Test Pattern
```python
from gltest import get_contract_factory
from gltest.assertions import tx_execution_succeeded
def test_full_flow():
factory = get_contract_factory("MyContract")
contract = factory.deploy(args=[])
# Write methods return transaction receipts
tx_receipt = contract.set_data(args=["hello"]).transact()
assert tx_execution_succeeded(tx_receipt)
# Read methods return values directly
result = contract.get_data(args=[contract.address]).call()
assert result == "hello"
```
`ACCEPTED` and `FINALIZED` are transaction lifecycle states, not proof that
contract execution succeeded. A transaction can be accepted and finalized with
an execution error, and failed execution applies no state changes. For deploy
transactions, failed execution means no contract is created.
Always assert `tx_execution_succeeded(receipt)` before reading state, checking
schema/code, or treating a missing contract as an infrastructure issue.
## Key Differences from Direc...
Details
- Author
- internet-court
- Repository
- internet-court/internet-court-skill
- Created
- 2 months ago
- Last Updated
- yesterday
- Language
- TypeScript
- License
- NOASSERTION
Similar Skills
Semantically similar based on skill content — not just same category
Testing & QA Solid
direct-tests
Write and run fast direct mode tests for GenLayer intelligent contracts.
4,294 Updated yesterday
internet-court Testing & QA Listed
integration-tests
Integration Tests — design-driven, systematic verification for the Integration Sprint. Derives boundary-value, flow-branch, and pattern-branch test cases from the enabled design specs, builds stubs for non-reproducible external interfaces, automates API and UI tests as committed project assets, and records results to .scrum/test-results.json. Runs before UAT & Release.
16 Updated today
sohei56 Testing & QA Listed
integration-testing
Use when implementing integration, API, or database-driven tests, or when deciding the right test type for a cross-boundary behavior.
0 Updated 2 weeks ago
sipandey