{"id":13579623,"url":"https://github.com/alteryx/locust-grasshopper","last_synced_at":"2025-04-09T05:12:00.223Z","repository":{"id":156585235,"uuid":"614084334","full_name":"alteryx/locust-grasshopper","owner":"alteryx","description":"a load testing tool extended from locust","archived":false,"fork":false,"pushed_at":"2024-09-23T21:14:58.000Z","size":215,"stargazers_count":178,"open_issues_count":1,"forks_count":9,"subscribers_count":6,"default_branch":"main","last_synced_at":"2024-12-04T16:44:55.830Z","etag":null,"topics":["load-testing","performance","performance-metrics","performance-testing","pytest","pytest-plugin","python"],"latest_commit_sha":null,"homepage":"","language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/alteryx.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":"CODEOWNERS","security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2023-03-14T21:25:49.000Z","updated_at":"2024-11-28T23:07:25.000Z","dependencies_parsed_at":null,"dependency_job_id":"75110cbb-a462-4642-b13e-9baeea726b6d","html_url":"https://github.com/alteryx/locust-grasshopper","commit_stats":null,"previous_names":[],"tags_count":31,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/alteryx%2Flocust-grasshopper","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/alteryx%2Flocust-grasshopper/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/alteryx%2Flocust-grasshopper/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/alteryx%2Flocust-grasshopper/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/alteryx","download_url":"https://codeload.github.com/alteryx/locust-grasshopper/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":247980844,"owners_count":21027808,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["load-testing","performance","performance-metrics","performance-testing","pytest","pytest-plugin","python"],"created_at":"2024-08-01T15:01:41.304Z","updated_at":"2025-04-09T05:12:00.201Z","avatar_url":"https://github.com/alteryx.png","language":"Python","funding_links":[],"categories":["Python","Tools \u0026 Integrations","Load Testing"],"sub_categories":["Frameworks"],"readme":"\u003cdiv id=\"top\"\u003e\u003c/div\u003e\n\n# Grasshopper\n\nA lightweight framework for performing load tests against an environment, primarily \nagainst an API. Grasshopper glues [Locust](https://locust.io/), [Pytest](https://docs.pytest.org/en/7.1.x/#), some plugins (namely [Locust InfluxDBListener](https://github.com/hoodoo-digital/locust-influxdb-listener) ) and some custom code to provide a\npackage that makes authoring load tests simple with very little boilerplate needed.\n\nHere are some key functionalities that this project extends on Locust:\n- [checks](#checks)\n- [custom trends](#custom-trends)\n- [timing thresholds](#thresholds)\n- [streamlined metric reporting/tagging system](#db-reporting)\n  (only influxDB is supported right now)\n\n## Installation\nThis package can be installed via pip: `pip install locust-grasshopper`\n\n## Example Load Test\n- You can refer to the test `test_example.py` in the `example` directory for a basic \n  skeleton of how to get a load test running. In the same directory, there is also an \n  example `conftest.py` that will show you how to get basic parameterization working.\n- This test can be invoked by running `pytest example/test_example.py` in the root of \n  this project.\n- This test can also be invoked via a YAML scenario file:\n```shell\ncd example\npytest example_scenarios.YAML --tags=example1\n```\n In this example scenario file, you can see how grasshopper_args, \n grasshopper_scenario_args, and tags are being set.\n\u003cp align=\"right\"\u003e(\u003ca href=\"#top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n## Creating a load test\nWhen creating a new load test, the primary grasshopper function you will be using \nis called `Grasshopper.launch_test`. This function can be imported like so: `from grasshopper.lib.grasshopper import Grasshopper`\n`launch_test` takes in a wide variety of args:\n- `user_classes`: User classes that the runner will run. These user classes must \n  extend BaseJourney, which is a grasshopper class \n  (`from grasshopper.lib.journeys.base_journey import BaseJourney`). This can be a \n  single class, a list of classes, or a dictionary where the key is the class and \n  the value is the locust weight to assign to that class.\n- `**complete_configuration`: In order for the test to have the correct configuration, you \n  must pass in the kwargs provided by the `complete_configuration` fixture. See example \n  load test on how to do this properly.\n\u003cp align=\"right\"\u003e(\u003ca href=\"#top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n## Scenario Args   \n\n- If you want to parameterize your journey class, you should use the `scenario_args` \n  dict. This is the proper way to pass in values from outside of \n  the journey for access by the journey code. Note that each journey gets a \n  ***copy*** on start, so the journey itself can safely modify its own dictionary \n  once the test is running.\n  `scenario_args` exists for any journey that extends the grasshopper `base_journey` \n  class. \n  `scenario_args` also grabs from `self.defaults` on initialization. For example:\n```python\nimport logging\nfrom locust import between, task\nfrom grasshopper.lib.journeys.base_journey import BaseJourney\nfrom grasshopper.lib.grasshopper import Grasshopper\n\n# a journey class with an example task\nclass ExampleJourney(BaseJourney):\n    # number of seconds to wait between each task\n    wait_time = between(min_wait=20, max_wait=30)\n    \n    # this defaults dictionary will be merged into scenario_args with lower precedence \n    # when the journey is initialized\n    defaults = {\n        \"foo\": \"bar\",\n    }\n    \n    @task\n    def example_task:\n        # log_prefix is a logger instance (LoggingAdapter)  used for logging with VU_number as a prefix.\n        # For more details, refer to the full implementation in base_journey.py\n        self.log_prefix.info(f'foo is `{self.scenario_args.get(\"foo\")}`.')\n        \n        # aggregate all metrics for the below request under the name \"get google\"\n        # if name is not specified, then the full url will be the name of the metric\n        response = self.client.get('https://google.com', name='get google')\n\n# the pytest test which launches the journey class\ndef test_run_example_journey(complete_configuration):\n    # update scenario args before initialization\n    ExampleJourney.update_incoming_scenario_args(complete_configuration)\n    \n    # launch the journey\n    locust_env = Grasshopper.launch_test(ExampleJourney, **complete_configuration)\n    return locust_env\n```\n\u003cp align=\"right\"\u003e(\u003ca href=\"#top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n## Commonly used grasshopper pytest arguments\n- `--runtime`: Number of seconds to run each test. Set to 120 by default.\n- `--users`: Max number of users that are spawned. Set to 1 by default.\n- `--spawn_rate` : Number of users to spawn per second. Set to 1 by default.\n- `--shape`: The name of a shape to run for the test. \nIf you don't specify a shape or shape instance, then the shape `Default` will be used, \n  which just runs with the users, runtime \u0026 spawn_rate specified on the command line (or picks up defaults \nof 1, 1, 120s). See `utils/shapes.py` for available shapes and information on how to add\nyour own shapes.\n- `--scenario_file` If you want a yaml file where you pre-define some args, this is how \nyou specify that file path. For example, \n  `scenario_file=example/scenario_example.YAML`. \n- `--scenario_name` If `--scenario_file` was specified, this is the scenario name that is \nwithin that YAML file that corresponds to the scenario you wish to run. Defaults to None.\n- `--tags` See below example: `Loop through a collection of scenarios that match some \n  tag`.\n- `--scenario_delay` Adds a delay in seconds between scenarios. Defaults to 0.\n- `--influx_host` If you want to report your performance test metrics to some influxdb, \nyou must specify a host.\n    E.g. `1.1.1.1`. Defaults to None.\n- `--influx_port`: Port for your `influx_host` in the case where it is non-default.\n- `--influx_ssl`: If your influxdb is using SSL, set this to True. Defaults to False.\n- `--influx_verify_ssl`: If your influxdb is using SSL, set this to True. Defaults to \n    False.\n- `--influx_user`: Username for your `influx_host`, if you have one.\n- `--influx_pwd`: Password for your `influx_host`, if you have one.\n- `--grafana_host`: If your grafana is a separate URL from the influxdb, you can \n  specify it here. If you don't, then the grafana URL will be the same as the \n  influxdb URL when the grasshopper object generates grafana links. \n\n\u003cp align=\"right\"\u003e(\u003ca href=\"#top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n## Launching tests with a configuration\nAll in all, there are a few ways you can actually collect and pass params to a test:\n\n### Run a test with its defaults\n`cd example`\n`pytest test_example.py ...`\n\n### Run a test with a specific scenario\n`cd example`\n`pytest test_example.py --scenario_file=example_scenarios.YAML --scenario_name=example_scenario_1 ...`\n\n### Loop through a collection of scenarios that match some tag\n`cd example`\n`pytest example_scenarios.YAML --tags=smoke ...`\n\n- As shown above, this case involves passing a `.YAML` scenario file into pytest instead of a `.py` file.\n- The `--scenario_file` and `--scenario_name` args will be ignored in this case\n- The `--tags` arg supports AND/OR operators according to the opensource `tag-matcher` package. More info on these operators can be found [here](https://pypi.org/project/tag-matcher/).\n- If no `--tags` arg is specified, then ALL the scenarios in the `.yaml` file will be run.\n- If a value is given for `--scenario_delay`, the test will wait that many seconds between collected scenarios.\n- All scenarios are implicitly tagged with the scenario name to support easily selecting one single\nscenario\n\n\u003cp align=\"right\"\u003e(\u003ca href=\"#top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n## Configuring Grasshopper\n\u003ca id=\"creating\"\u003e\u003c/a\u003e\n\nGrasshopper adds a variety of parameters relating to performance testing along with a\nvariety of ways to set these values.\n\nRecent changes (\u003e= 1.1.1) include an expanded set of sources, almost full access to all \narguments via every source (some exceptions outlined below), and the addition of some \nnew values that will be used with integrations such as report portal \u0026 slack \n(integrations are NYI). These changes are made in a backwards compatible manner, \nmeaning all existing grasshopper tests should still run without modification. The \noriginal fixtures and sources for configuration are deprecated, but still produce the \nsame behavior.\n\nAll of the usual [pytest arguments](https://docs.pytest.org/en/6.2.x/usage.html) also remain available.\n\nThe rest of the sections on configuration assume you are using `locust-grasshopper\u003e=1.1.1`.\n\u003cp align=\"right\"\u003e(\u003ca href=\"#top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n### Sources\nCurrently, there are 5 different sources for configuration values and they are, in \nprecedence order \n\n+ command line arguments\n+ environment variables\n+ scenario values from a scenario yaml file\n+ grasshopper configuration file\n+ global defaults (currently stored in code, not configurable by consumers)\n\nObviously, the global defaults defined by Grasshopper are not really a source for\nconsumers to modify, but we mention it so values don't seem to appear \"out of thin air\".\n\u003cp align=\"right\"\u003e(\u003ca href=\"#top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n### Categories\nThe argument list is getting lengthy, so we've broken it down into categories. These\ncategories are entirely for humans: better readability, understanding and ease of use. \nOnce they are all fully loaded by Grasshopper, they will be stored in a single \n`GHConfiguration` object (`dict`). By definition, every argument is in only one category\nand there is no overlap of keys between the categories. If the same key is supplied in\nmultiple categories, they will be merged with the precedence order as they appear in\nthe table.\n\n| Name        | Scope              | Description/Usage                                                                                                                                                                                                                                         |\n|-------------| ------------------ |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Grasshopper | Session            | Variables that rarely change, may span many test runs.                                                                                                                                                                                                    |\n| Test Run    | Session            | Variables that may change per test run, but are the\u003cbr/\u003esame for every scenario in the run                                                                                                                                                                |\n| Scenario    | Session            | Variables that may change per scenario and are often\u003cbr/\u003escenario specific; Includes user defined variables that are\u003cbr/\u003enot declared as command line arguments by Grasshopper.\u003cbr/\u003eHowever, you may use pytest's addoptions hook in your \u003cbr/\u003econftest to define them. |\n\nAt least one of the sections must be present in the global configuration file and\neventually this will be the same in the configuration section of a scenario in a scenario \nyaml file. Categories are not used when specifying environment variables or command line\noptions. We recommend that you use these categories in file sources, but if a variable \nis in the wrong section, it won't actually affect the configuration loading process.\n\u003cp align=\"right\"\u003e(\u003ca href=\"#top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n### Using Configuration Values \nYour test(s) may access the complete merged set of key-value pairs via the session scoped \nfixture `complete_configuration`. This returns a `GHConfiguration` object (dict) which\nis unique to the current scenario. This value will be re-calculated for each new scenario\nexecuted.\n\nA few perhaps not obvious notes about configuration:\n+ use the environment variable convention of all uppercase key names (e.g. `RUNTIME=10`)\nto _specify_ a key-value pair via an environment value\n+ use the lower case key to _access_ a key from the `GHConfiguration` object \n(e.g. `x = complete_configuration(\"runtime\")`) regardless of the original source(s)\n+ use `--` before the key name to specify it on the command line (e.g. `--runtime=10`)\n+ configure a grasshopper configuration file by creating a session scoped fixture loaded \nby your conftest.py called `grasshopper_config_file_path` which returns the full path to a \nconfiguration yaml file.\n+ grasshopper supports thresholds specified as\n  + a json string - required for environment variable or commandline, but also accepted\n  from other sources\n  + a dict - when passing in via the `scenario_args` method (more details on that below)\n  or via a journey class's `defaults` attr.\n\n```python\n@pytest.fixture(scope=\"session\")\ndef grasshopper_config_file_path():\n    return \"path/to/your/config/file\"\n```\n\nAn example grasshopper configuration file:\n```yaml\ngrasshopper:\n  influx_host: 1.1.1.1\ntest_run:\n  users: 1.0\n  spawn_rate: 1.0\n  runtime: 600\nscenario:\n  key1 : 'value1'\n  key2: 0\n```\n\u003cp align=\"right\"\u003e(\u003ca href=\"#top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n### Additional Extensions to the configuration loading process\n\nIf you would like to include other environment variables that might be present in the\nsystem, you can define a fixture called `extra_env_var_keys` which returns a list of key\nnames to load from the `os.environ`. Keys that are missing in the environment will not \nbe included in the `GHConfiguration` object.\n\nAny environment variables that use the prefix `GH_` will also be included in the \n`GHConfiguration` object. The `GH_` will be stripped before adding and any names that\nbecome zero length after the strip will be discarded. This is a mechanism to include any\nscenario arguments you might like to pass via an environment variable.\n\nIn the unlikely case that you need to use a different prefix to designate scenario\nvariables, you can define a fixture called `env_var_prefix_key` which returns a prefix\nstring. The same rules apply about which values are included in the configuration.\n\n\u003cp align=\"right\"\u003e(\u003ca href=\"#top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n## Checks\n\u003ca id=\"checks\"\u003e\u003c/a\u003e\nChecks are an assertion that is recorded as a metric. \nThey are useful both to ensure your test is working correctly \n(e.g. are you getting a valid id back from some post that you sent) \nand to evaluate if the load is causing intermittent failures \n(e.g. sometimes a percentage of workflow runs don't complete correctly the load increases). \nAt the end of the test, checks are aggregated by their name across all journeys that \nran and then reported to the console. They are also forwarded to the DB \nin the \"checks\" table. Here is an example of using a check: \n\n```python\nfrom grasshopper.lib.util.utils import check\n...\nresponse = self.client.get(\n    'https://google.com', name='get google'\n)\ncheck(\n    \"get google responded with a 200\",\n    response.status_code == 200,\n    env=self.environment,\n)\n```\nIt is worth noting that it is NOT necessary to add checks on the http codes. All the \nHTTP return codes are tracked automatically by grasshopper and will be sent to the DB. \nIf you aren't using a DB then you might want the checks console output.\n\u003cp align=\"right\"\u003e(\u003ca href=\"#top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n## Custom Trends\n\u003ca id=\"custom-trends\"\u003e\u003c/a\u003e\nCustom trends are useful when you want to time something that spans multiple HTTP \ncalls. They are reported to the specified database just like any other HTTP request, \nbut with the \"CUSTOM\" HTTP verb as opposed to \"GET\", \"POST\", etc. Here is an example \nof using a custom trend:\n```python\nfrom locust import between, task\nfrom grasshopper.lib.util.utils import custom_trend\n...\n\n@task\n@custom_trend(\"my_custom_trend\")\ndef google_get_journey(self)\n    for i in range(len(10)):\n        response = self.client.get(\n            'https://google.com', name='get google', context={'foo1':'bar1'}\n        )\n```\n\u003cp align=\"right\"\u003e(\u003ca href=\"#top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n## Thresholds\n\u003ca id=\"thresholds\"\u003e\u003c/a\u003e\nThresholds are time-based, and can be added to any trend, whether it be a custom \ntrend or a request response time. Thresholds default to the 0.9 percentile of timings. \nHere is an example of using a threshold: \n\n```python\n# a journey class with an example threshold\nfrom locust import between, task\nfrom grasshopper.lib.journeys.base_journey import BaseJourney\nfrom grasshopper.lib.grasshopper import Grasshopper\n\nclass ExampleJourney(BaseJourney):\n    # number of seconds to wait between each task\n    wait_time = between(min_wait=20, max_wait=30)\n    \n    @task\n    def example_task:\n        self.client.get(\"https://google.com\", name=\"get google\")\n        \n    @task\n    @custom_trend(\"my custom trend\")\n    def example_task_custom_trend:\n        time.sleep(10)\n\n# the pytest test which launches the journey class, thresholds could be \n# parameterized here as well.\ndef test_run_example_journey(complete_configuration):\n    ExampleJourney.update_incoming_scenario_args(complete_configuration)\n    ExampleJourney.update_incoming_scenario_args({\n        \"thresholds\": {\n            \"get google\":\n                {\n                    \"type\": \"get\",\n                    \"limit\": 4000  # 4 second HTTP response threshold\n                },\n            \"my custom trend\":\n                {\n                    \"type\": \"custom\",\n                    \"limit\": 11000  # 11 second custom trend threshold\n                }\n        }\n    })\n    \n    locust_env = Grasshopper.launch_test(ExampleJourney, **complete_configuration)\n    return locust_env\n```\n\nThresholds can also be defined for individual YAML scenarios. Refer to the `thresholds` \nkey in `example/example_scenarios.YAML` for how to use thresholds for YAML scenarios.\n\nAfter a test has concluded, trend/threshold data can be found in \n`locust_env.stats.trends`. \nThis data is also reported to the console at the end of each test.\n\n\u003cp align=\"right\"\u003e(\u003ca href=\"#top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n## Time Series DB Reporting and Tagging\n\u003ca id=\"db-reporting\"\u003e\u003c/a\u003e\n\nAdditional design details about how a database listener works with grasshopper/locust can be \nfound in the [Database Listener Design Documentation](./docs/database_listener_design_documentation.md).\n\nWhen you specify a time series database URL param to `launch_test`, such as \n`influx_host`, all metrics will be automatically reported to tables within the `locust` \ntimeseries database via the specified URL. These tables include:\n- `locust_checks`: check name, check passed, etc.\n- `locust_events`: test started, test stopped, etc.\n- `locust_exceptions`: error messages\n- `locust_requests`: HTTP requests and custom trends\n\nTo run the influxdb/grafana locally, you can use the docker-compose file in the example directory:\n```shell\ncd example/observability_infrastructure\ndocker-compose up -d\n```\nand then you can access the grafana UI at `localhost`. The default username/password is `admin/admin`.\nTo then run a test which reports to this influxdb just add the `--influx_host=localhost` handle. \n\n\nThere are a few ways you can pass in extra tags which \nwill be reported to the time series DB:\n\n1. **HTTP Request Tagging**   \n     All HTTP requests are automatically tagged with their name. If you want to pass in \n     extra tags for a particular HTTP request, you can pass them in \n     as a dictionary for the `context` param when making a request. For example:\n\n    ```python\n    self.client.get('https://google.com', name='get google', context={'foo':'bar'})\n    ```\n    The tags on this metric would then be: `{'name': 'get google', 'foo': 'bar'}` which \n    would get forwarded to the database if specified. \n\n2. **Check Tagging**   \n   When defining a check, you can pass in extra tags with the `tags` parameter:\n    ```python\n    from grasshopper.lib.util.utils import check\n    ...\n    response = self.client.get(\n    'https://google.com', name='get google', context={'foo1':'bar1'}\n    )\n    check(\n       \"get google responded with a 200\",\n       response.status_code == 200,\n       env=self.environment,\n       tags = {'foo2': 'bar2'}\n    )\n    ```\n\n3. **Custom Trend Tagging**   \n    Since custom trends are decorators, they do not have access to \n   non-static class variables when defined. Therefore, you must use the \n   `extra_tag_keys` param, which is an array of keys that exist in the journey's \n   scenario_args. So for example, if a journey had the scenario args `{\"foo\" : \"bar\"}` and you wanted to tag \n   a custom trend based on the \"foo\" scenario arg key, you would do something like this:\n    ```python\n    from locust import between, task\n    from grasshopper.lib.util.utils import custom_trend\n    ...\n        \n    @task\n    @custom_trend(\"my_custom_trend\", extra_tag_keys=[\"foo\"])\n    def google_get_journey(self)\n       for i in range(len(10)):\n          response = self.client.get(\n             'https://google.com', name='get google', context={'foo1':'bar1'}\n          )\n    ```\n\u003cp align=\"right\"\u003e(\u003ca href=\"#top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n## Project Roadmap\n\n- [X] Custom Trends\n- [X] Checks\n- [X] Thresholds\n- [X] Tagging\n- [X] InfluxDB metric reporting\n- [X] docker-compose template for influxdb/grafana\n- [ ] PrometheusDB metric reporting\n- [ ] Slack reporting\n- [ ] ReportPortal reporting\n\nSee the open issues for a full list of proposed features (and known issues).\n\n\u003cp align=\"right\"\u003e(\u003ca href=\"#top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n## Contributing\n\nContributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are **greatly appreciated**.\n\nIf you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag \"enhancement\".\nDon't forget to give the project a star! Thanks again!\n\n1. Fork the Project\n2. Create your Feature Branch (`git checkout -b feature/AmazingFeature`)\n3. Make sure unit tests pass (`pytest tests/unit`)\n4. Add unit tests to keep coverage up, if necessary\n5. Commit your Changes (`git commit -m 'Add some AmazingFeature'`)\n6. Push to the Branch (`git push origin feature/AmazingFeature`)\n7. Open a Pull Request\n\n\u003cp align=\"right\"\u003e(\u003ca href=\"#top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Falteryx%2Flocust-grasshopper","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Falteryx%2Flocust-grasshopper","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Falteryx%2Flocust-grasshopper/lists"}