Added test reporters and coverage analysis

[Slartibartfass2]

No description provided.

[github-actions]

LCOV of commit c6c6085 during Code Quality Checks #104

Summary coverage rate:
  lines......: 3.8% (12 of 316 lines)
  functions..: 3.1% (1 of 32 functions)
  branches...: no data found

Files changed coverage rate:
                                                              |Lines       |Functions  |Branches    
  Filename                                                    |Rate     Num|Rate    Num|Rate     Num
  ==================================================================================================
  src/lib/components/composites/Demo.svelte                   | 100%     12|50.0%     2|    -      0

[Merseleo]

Again, I think this is a good basis for all the testing and further configuration will follow when writing the tests. However, maybe you could add a meaningful test example, if this is possible (i. e. for a e2e test and a component test, which is probably not possible so far as we don't have any components completed, and normal tests).
And as far as I understood examples etc. correctly the configs look good for now.

One last request: maybe you should add a short section about testing in the Readme.md, so how we test, how to run them locally and what is reported in the CI (optionally). Or do you think differently?

[Slartibartfass2]

I'll add a real component test in #74, I don't think it makes much sense to add a demo test now.

I'll add a section in the README as soon as we are finished discussing the location of the tests.

[Merseleo]

I think we are on the right track.
The new section in the README.md surely is helpful for new people and for us at beginning too. But one last question (must not be done in this PR): do you think it is helpful to host the report anywhere and link to them in the README.md or add a coverage badge or something like that?

[Slartibartfass2]

I think we are on the right track. The new section in the README.md surely is helpful for new people and for us at beginning too. But one last question (must not be done in this PR): do you think it is helpful to host the report anywhere and link to them in the README.md or add a coverage badge or something like that?

we could use github pages to host, but I am not convinced that's necessary. If you want to check out the coverage, one could either download the report or just run the tests in the repo.

About the coverage badge: Maybe that's possible, but I'm not sure. Perhaps we can research this and add this later.

[Merseleo]

LGTM