Frisbee – Kubernetes Native Testbed

The effort being put in automating tests should not take over delivering value to users. Frisbee makes it possible to:

🎁 Setup initial dependency stack – easily!

🏭 Test against actual, close to production software - no mocks!

⏳ Replay complex workloads written in an intuitive language!

🏗️ Combine Chaos Engineering with large-scale performance testing!

🕹️ Assert actual program behavior and side effects

🧭 Scenarios

• Logical Dependencies
• Scheduled Execution
• Advanced Placement
• Conditional Loops
• Conditional Execution
• Runtime Assertions
• Elastic Topologies
• Recoverability Experiments
• Time-Driven Chaos Engineering
• State-Driven Chaos Engineering
• Metrics-Driven Chaos Engineering
• App-Specific Graceful Shutdowns
• Failover

TL;DR

1. Make sure that kubectl and Helm are installed on your system.

2. Update Helm repo.

   >> helm repo add frisbee https://carv-ics-forth.github.io/frisbee/charts

3. Install Helm Packages.

   # Install the platform
   >> helm upgrade --install --wait my-frisbee frisbee/platform
   # Install the package for monitoring YCSB output
   >> helm upgrade --install --wait my-ycsb frisbee/ycsb
   # Install TiKV store
   >> helm upgrade --install --wait my-tikv frisbee/tikv

4. Create/Destroy the test plan.

   # Create 
   >> curl -sSL https://raw.githubusercontent.com/CARV-ICS-FORTH/frisbee/main/charts/tikv/examples/plan.baseline.yml | kubectl -f - apply
   
   # Destroy
   >> curl -sSL https://raw.githubusercontent.com/CARV-ICS-FORTH/frisbee/main/charts/tikv/examples/plan.baseline.yml | kubectl -f - delete --cascade=foreground

If everything went smoothly, you should see a similar Grafana Dashboard .

Through these dashboards humans and controllers can examine to check things like completion, health, and SLA compliance.

Client-View (YCSB-Dashboard)

Client-View (Redis-Dashboard)

📙 Documentation

Frisbee addresses the key pain points developers and QA engineers face when testing cloud-native applications in the earlier stages of the software lifecycle. We make it possible to:

• Run tests: create temporary containers for application dependencies, setup their initial state and clean them up in the end.
• Write tests: describe complex topologies, dynamic operating conditions, Chaos Events, and distributed assertions.
• Debug tests: integrate application-specific metrics, monitor site-wide health metrics, and raise notifications on SLA violations.

For more information, Frisbee installation and reference documents are available at:

👉 Quick Start

👉 Test Plans

🙋‍♂️ Getting Help

We are here to help!

👉 If you face troubles, check the Frequently Asked Questions.

👉 For feature requests and bugs, file an issue.

👉 For great new ideas, browse through the GitHub discussions.

👉 To get updates ⭐️ star this repository.

➕ Contributing

The original intention of our open source project is to lower the threshold of testing distributed systems, so we highly value the use of the project in enterprises and in academia.

We welcome also every contribution, even if it is just punctuation. Here are some steps to help get you started:

✔ Read and agree to the Contribution Guidelines.

✔ Read Frisbee design and development details on the GitHub Wiki.

✔ Contact us directly for other ways to get involved.

Acknowledgements

This project has received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement No. 894204 (Ether, H2020-MSCA-IF-2019).