Spec/tests closer to src code

[hirako2000]

Ideally the tests should be closer to the src code.

Why?
Incentive to test the code. Not having to search for where existing specs are etc.
If not possible/difficult with our current setup, let's at least bring structure to the specs we have in the test folder.

Or discuss. what we have right now is far from ideal.

Version:

• v2.x.x
• v1.x.x

Issue type:

• Bug
• Proposal/Enhancement
• Question
• Discussion

---

Tested on:

Desktop

• Chrome
• Chrome Canary
• Chrome dev-channel
• Firefox
• Opera
• Microsoft IE
• Microsoft Edge

Android

• Chrome
• Firefox
• Opera

IOS

• Chrome
• Firefox
• Opera

[thejmazz]

so can use jest style? with __spec__ (or similar) folder alongside code

[sasha240100]

@thejmazz We discussed. I suggest having tests in src folder like Component.spec.js. That way we can easily see which tests need to be done

[hirako2000]

I think @thejmazz is correct.
We can bring it closer to the src, but with that test and mock pattern.

[hirako2000]

@sasha240100 can you check the async change I made, and merge?

[sasha240100]

@hirako2000 Yes, where to merge?