33 lines
1.1 KiB
Markdown
33 lines
1.1 KiB
Markdown
---
|
|
name: Test scenario request
|
|
about: Suggest a test scenario for Project Oni to consider
|
|
title: "[test request] "
|
|
labels: hint/needs-analysis, hint/needs-triage, kind/test-scenario
|
|
assignees: raulk
|
|
|
|
---
|
|
|
|
**What would you like us to test?**
|
|
|
|
<!-- A clear and concise description of what the test scenario looks like, e.g. I'd like you to test that/if/how [...] -->
|
|
|
|
**Technical implementation details.**
|
|
|
|
<!-- Provide any technical insight that would help us implement such scenario. Think about the setup, choreography between nodes, operations involved, etc. -->
|
|
|
|
**What should we measure?**
|
|
|
|
<!-- Test scenarios are behaviours we orchestrate. In most cases, you'll want measurements captured. What would those be? -->
|
|
|
|
**Which components are involved?**
|
|
|
|
<!-- Enumerate the Filecoin system components that are involved in this test scenario. Feel free to provide further details. -->
|
|
|
|
**On a scale from 0-10, what's the proposed _**discomfort factor**_? In other words, how uncomfortable would you be if we went live **without** having tested this? Explain why.**
|
|
|
|
<!-- 8/10. Because... -->
|
|
|
|
**Additional remarks.**
|
|
|
|
<!-- Anything else that Project Oni should know. -->
|