mirror of
https://github.com/logos-blockchain/logos-blockchain-testing.git
synced 2026-01-14 19:23:08 +00:00
a443374e4d
- Added an example that selects the deployer (local or docker compose) based on an environment variable. - Let cucumber's argument parsing environment select scenarios to run - this allows for a flexible test environment.
35 lines
1.5 KiB
Gherkin
35 lines
1.5 KiB
Gherkin
Feature: Testing Framework - Auto Local/Compose Deployer
|
|
|
|
Scenario: Run auto deployer smoke scenario (tx + DA + liveness)
|
|
Given we have a CLI deployer specified
|
|
And topology has 1 validators and 1 executors
|
|
And run duration is 60 seconds
|
|
And wallets total funds is 1000000000 split across 50 users
|
|
And transactions rate is 1 per block
|
|
And data availability channel rate is 1 per block and blob rate is 1 per block
|
|
And expect consensus liveness
|
|
When run scenario
|
|
Then scenario should succeed
|
|
|
|
# Note: This test may fail on slow computers
|
|
Scenario: Run auto deployer stress smoke scenario (tx + DA + liveness)
|
|
Given we have a CLI deployer specified
|
|
And topology has 3 validators and 3 executors
|
|
And run duration is 120 seconds
|
|
And wallets total funds is 1000000000 split across 500 users
|
|
And transactions rate is 10 per block
|
|
And data availability channel rate is 1 per block and blob rate is 1 per block
|
|
And expect consensus liveness
|
|
When run scenario
|
|
Then scenario should succeed
|
|
|
|
Scenario: Run auto deployer stress smoke scenario no liveness (tx + DA + liveness)
|
|
Given we have a CLI deployer specified
|
|
And topology has 3 validators and 3 executors
|
|
And run duration is 120 seconds
|
|
And wallets total funds is 1000000000 split across 500 users
|
|
And transactions rate is 10 per block
|
|
And data availability channel rate is 1 per block and blob rate is 1 per block
|
|
When run scenario
|
|
Then scenario should succeed
|