Expand description
Goose
Have you ever been attacked by a goose?
Goose is a load testing framework inspired by Locust. User behavior is defined with standard Rust code.
Goose load tests, called Goose Attacks, are built by creating an application with Cargo, and declaring a dependency on the Goose library.
Goose uses reqwest
to provide a convenient HTTP
client.
Documentation
License
Copyright 2020-2023 Jeremy Andrews
Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Modules
- Functions and structures related to configuring a Goose load test.
- Optional telnet and WebSocket Controller threads.
- Helpers and objects for building Goose load tests.
- An optional thread for writing logs.
- Optional metrics collected and aggregated during load tests.
- A list of things that typically must be imported to write a Goose load test.
- Utility functions used by Goose, and available when writing load tests.
Macros
scenario!("foo")
expands toScenario::new("foo")
.transaction!(foo)
expands toTransaction::new(foo)
, but also does some boxing to work around a limitation in the compiler.
Structs
- Global internal state for the load test.
Enums
- A
GooseAttack
load test operates in one (and only one) of the following modes. - A
GooseAttack
load test moves through each of the following phases during a complete load test. - An enumeration of all errors a
GooseAttack
can return. - Used to define the order
Scenario
s andTransaction
s are allocated.