This shows you the differences between two versions of the page.
public:bug_reporting [2016/08/17 08:45] acorbi |
public:bug_reporting [2020/06/23 15:04] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Reporting bugs and/or feature requests on github ====== | ||
- | |||
- | ===== Who is this guide for ===== | ||
- | |||
- | * External users testing the platform | ||
- | * Internal staff helping improve the code base | ||
- | |||
- | ===== What this guide teaches ===== | ||
- | |||
- | * How to report bugs or problems currently being reproduced on the platform | ||
- | * How to request implementation of new features and enhancements | ||
- | |||
- | ===== Things to know in forehand ===== | ||
- | |||
- | ==== Issues should be filed on the corresponding github repository ==== | ||
- | |||
- | ==== Some resources as a background ==== | ||
- | |||
- | ===== Reproducing and describing bugs ===== | ||
- | |||
- | Keeping a consistent methodology for reproducing bugs is very important. Once a tester identifies an error, the conditions for repeating it need to be gathered in order for developers to reproduce the scenario and be able to test solutions. This process consist on following steps: | ||
- | |||
- | - a | ||
- | - b | ||
- | |||
- | ===== Requesting the implementation of a new feature or enhancement ===== | ||
- | |||
- | The process for requesting a new feature is similar to bug reporting. It differs on: | ||
- | |||
- | - a | ||
- | - b | ||