If each test case a html file, it results in too many html files added,
which are hard to visit by category and management.
If adding multiple test cases in one file, not easy to find a rule about
which case should be in which file.
In my opinion, it essentially the same as "how to classify test cases".
We used to write test cases in this framework:
```js
describe('some test suite', function () {
describe('some sub test suite', function () {
})
```
------------------------------
Su Shuang (100pah)
------------------------------
On Mon, 16 Sep 2019 at 16:58, Yi Shen <shenyi....@gmail.com> wrote:
> There is another thing I think we should discussed about.
>
> Currently all our tests in the test folder[1] are not organized well.
> It's hard for contributors, or even for me to find out how / where to add
> a test case for further regression testing after they fixed a bug.
> For example. If they fixed a bug about dataZoom. Should they create a new
> test HTML file for this test case, or supplement this test case to the
> exits test files.
> [1] https://github.com/apache/incubator-echarts/tree/master/test
>
