Gather inputs to test guidelines from colleagues and publish in documentation

[buep]

We have a draft for test guidelines in a Praqma internal GDoc: https://docs.google.com/document/d/1VA7YW6ua_tEBtVXzmvYHgyjLf4MCEraUuCjnvSXLVuQ/edit#

It will be published when discussed internally.

When published we must update the following sections in current documentation:

• https://github.com/Praqma/Praqmatic-Automated-Changelog/blob/master/roadmap.md#testing-and-quality
• https://github.com/Praqma/Praqmatic-Automated-Changelog/blob/master/docs/developer_info.md#tests

See #98 for issues and #99 for PR.

[buep]

Hi @emilybache and @carmosin today would you have time at some point to review our testing guideline for our Ruby project PAC that can generate changelogs?

I think you're the experts, we just gathering some testing guidelines in the project that could guide future effort in this project.
Any inputs are welcome - what should a good testing strategy really include?

[buep]

CC @MadsNielsen @michaelmadsen

[emilybache]

Hi, I'm in oslo now and involved in the conference tomorrow but of course I'd like to help. I can review testing guidelines- where do I find them?

[buep]

You find the guidelines in top os this issue in the Google doc link.

Thanks :-)

[emilybache]

I made some comments inline. I think you're mostly on the right track!

[buep]

Thanks a lot - I'll get back soon when I look into them :-)