Use "tests" levels as functional testing examples

[narqo]

We should split our current examples into two parts: so called "examples for documentation" and "examples for functional testing".

First part (current <block>.examples) will be used to show block's functionality which is interesting for users. Second part would consists of development specific cases of usage of the block.

[narqo]

I think that this kind of levels should be called specs not tests. So the building "targets" would be:

• Build and run all tests (test.js. node.test.js, etc) for blocks from "common" level.

› bem make common.tests

• Build all "specs" from "common" level to test that blocks still work fine in all kind of test-cases. As an example of this kind of test-cases, could be inline transparent button on the green background

› bem make common.specs

• build all examples for blocks from "desktop" level. This examples could be used in public library documentation

› bem make desktop.examples

@veged @dfilatov, need your opinion

[dfilatov]

I think current tests should be renamed to specs (and *.test.js files should be renamed to *.spec.js too). Our current tests have been written as BDD specs.

[veged]

@dfilatov +1

[narqo]

:joy_cat: :+1: