cerc-io/lotus
16
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 27 Wiki Activity

update issue templates + labels.

Browse Source
This commit is contained in:
Raúl Kripalani 2020-06-25 11:14:15 +01:00
parent e9402da131
commit 1cb087c99e
3 changed files with 35 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
.github/ISSUE_TEMPLATE/system-process.md vendored Normal file
View File

@ -0,0 +1,25 @@
---
name: ⚙️ System process
about: Identify a system process to cover through tests
title: "[system process] "
labels: hint/needs-analysis, hint/needs-triage, kind/system-process
assignees: raulk
---
**Describe the system process.**
<!-- Freeform description/braindump of what the system process does, when is it invoked, what components it interacts with, etc. -->
**Brainstorm test scenarios.**
<!-- Freeform brainstorming of test scenarios. Think about happy paths, natural faults, induced faults (e.g. attacks), stress tests, fuzzying, etc. -->
**Discomfort factor (0-10).**
<!-- How uncomfortable would you be if we launched mainnet without our Oni tests covering this system process / test scenario? -->
<!-- Rubric in https://github.com/filecoin-project/oni/labels?q=discomfort. -->
**Additional remarks.**
<!-- Anything else that Project Oni should know. -->

19
.github/ISSUE_TEMPLATE/test-scenario-request.md vendored
View File

@ -1,5 +1,5 @@
---
name: Test scenario request
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
@ -7,25 +7,22 @@ assignees: raulk
---
**What would you like us to test?**
**Describe the test scenario.**
<!-- 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 background and technical implementation details.**
<!-- Provide any technical insight that would help us implement such scenario. Think about the setup, choreography between nodes, operations involved, etc. -->
<!-- Provide any info and 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? -->
<!-- Indicate what we should be measuring for comparison/analytical purposes. -->
**Which components are involved?**
**Discomfort factor (0-10).**
<!-- 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... -->
<!-- How uncomfortable would you be if we launched mainnet without our Oni tests covering this system process / test scenario? -->
<!-- Rubric in https://github.com/filecoin-project/oni/labels?q=discomfort. -->
**Additional remarks.**

4
.github/labels.yml vendored
View File

@ -49,7 +49,7 @@
color: fcf0b5
description: "Kind: Improvement"
- name: kind/test-scenario
color: fcf0b5
color: feb95e
description: "Kind: Test Scenario"
- name: kind/tracking-issue
color: fcf0b5
@ -67,7 +67,7 @@
color: fcf0b5
description: "Kind: Spike"
- name: kind/system-process
color: fcf0b5
color: ff4782
description: "Kind: System Process"
###