Create load-test using Locust

Open
  • Is something wrong?
#434 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
go, python
Domain
api, performance, testing-qa

Research direction

Start by reviewing the API structure in the rest/ and graphql/ directories, then obtain the dev gateway URL from the maintainer and read the Locust documentation. Define the load-test files under a project-root loadtest/ directory and confirm that they can exercise the dev API with the agreed workload.

Written by the indexing model from the issue text.

Description

feature request L3

Overview

Implement load-test on dev deployment of our API using (Locust)[https://locust.io/] in Python.
In my opinion, it's fine to create the /loadtest at the project root that is used for loadtest script.

nebula-api/
├── .venv/     # local Python environment, gitignored
├── loadtest/  # Locust files
├── rest/
├── graphql/
├── go.mod
└── go.sum

However, if you a better idea let me know.

Resources

When you want to work on this issue, let me know so I can give you the URL of the dev gateway for you to call the dev API.

Dominant language
Go
Stars
41
Forks
100
Avg merge
14d 5h
Merged PRs (30d)
5

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from UTDNebula/nebula-api

All issues in UTDNebula/nebula-api

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.