[Chore] Improving contribution guides (#40)

* Added testing guiding

* Added issue templates and pull request templates

Author: luistak

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,33 @@
+---
+name: 🐛 Bug report
+about: Bugs, missing documentation, or unexpected behavior.
+---
+
+- package` version:
+- DOM Environment:
+
+### Relevant code or config:
+
+```js
+var your => (code) => here;
+```
+<!-- If there is a repository or codesandbox please also paste in here -->
+
+### What happened:
+
+<!-- Please provide the full error message/screenshots/anything -->
+
+### Reproduction:
+
+<!--
+If possible, please create a repository or a code-sandbox that reproduces the issue with the
+minimal amount of code possible.
+-->
+
+### Problem description:
+
+<!-- Please describe why the current behavior is a problem -->
+
+### Suggested solution:
+
+<!-- Optional -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,23 @@
+---
+name: 💡 Feature Request
+about: I have a suggestion or new component (and might want to implement myself)!
+---
+
+### Describe the feature you'd like:
+
+<!--
+A clear and concise description of what you want to happen. Add any considered
+drawbacks.
+-->
+
+### Suggested implementation:
+
+<!-- Optional -->
+
+
+### Describe alternatives you've considered:
+
+<!--
+A clear and concise description of any alternative solutions or features you've
+considered.
+-->

.github/ISSUE_TEMPLATE/support_question.md

@@ -0,0 +1,6 @@
+---
+name: ❓ Support Question
+about: Get help with any windowed observable package
+---
+
+<!-- If you've discovered a bug or would like to propose a change please use one of the other issue templates. -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,20 @@
+**What**:
+
+<!-- What changes are being made? (What feature/bug is being fixed here?) -->
+
+
+**Why**:
+
+<!-- Why are these changes necessary? -->
+
+
+**Checklist**:
+
+<!-- Remove an item if that's irrelevant to your changes -->
+<!-- to check an item, place an "x" in the box like so: "- [x] Documentation" -->
+
+- [ ] Tests
+- [ ] Typescript definitions updated
+- [ ] Ready to be merged
+
+<!-- feel free to add additional comments -->

CONTRIBUTING.md

@@ -4,3 +4,11 @@ Thanks for being willing to contribute!
 
 **Working on your first Pull Request?** You can learn how from this _free_
 series [How to Contribute to an Open Source Project on GitHub][egghead]
+
+## Bugs
+
+Bugs are tracked using [Github Issues](https://github.com/luistak/windowed-observable/issues). If you found a bug, please make sure they are not already reported and follow the template in order to create a new report.
+
+## Proposing changes
+
+Create a [new issue](https://github.com/luistak/windowed-observable/issues/new/choose) with the corresponding template in order to propose changes.

TESTING.md

@@ -0,0 +1,58 @@
+# Testing
+
+## Running components tests locally
+
+Run every test in the package
+
+```sh
+yarn test:ci
+```
+
+Run and watch modified files 
+
+Go to `core` or `react` package and run
+```sh
+yarn test:watch
+```
+
+## Technologies
+
+We are using a react test setup with:
+
+- [Jest](https://github.com/facebook/jest)
+- [@testing-library](https://github.com/testing-library)
+  - [react](https://github.com/testing-library/react-testing-library)
+  - [jest-dom](https://github.com/testing-library/jest-dom)
+  - [user-event](https://github.com/testing-library/user-event)
+
+And these eslint plugins to ensure best practices
+
+- [eslint-plugin-jest-dom](https://github.com/testing-library/eslint-plugin-jest-dom)
+- [eslint-plugin-testing-library](https://github.com/testing-library/eslint-plugin-testing-library)
+
+## Principles
+
+> [The more your tests resemble the way your software is used,
+> the more confidence they can give you.](https://testing-library.com/docs/guiding-principles)
+
+We are following [@testing-library](https://testing-library.com/docs/guiding-principles) guiding principles, trying to avoid [testing implementation details](https://kentcdodds.com/blog/testing-implementation-details)
+
+## Best practices
+
+- [**Common mistakes using @testing-library**](https://kentcdodds.com/blog/common-mistakes-with-react-testing-library)
+- [Avoid nesting](https://kentcdodds.com/blog/avoid-nesting-when-youre-testing)
+- [Aha testing](https://kentcdodds.com/blog/aha-testing)
+
+## Recommended extensions
+
+### Jest vscode extension
+
+We recommend using the [official jest extension](https://marketplace.visualstudio.com/items?itemName=Orta.vscode-jest) to ensure a better testing experience.
+
+But this extension have a specific drawback, there is [no official support for multiple jest-configs](https://github.com/jest-community/vscode-jest/issues/428) or [support for monorepos](https://github.com/jest-community/vscode-jest/issues/129), although we added a `setupTests.ts` that only execute for this extension, each package have their own jest config
+
+### Which query?
+
+[`Which query`](https://github.com/testing-library/which-query) is an awesome extension that aims to enable developers to find a better query when writing tests
+
+There is also [the docs](https://testing-library.com/docs/dom-testing-library/api-queries) and [this article](https://testing-library.com/docs/guide-which-query) that may help you to fint the best query