Create a suite of tests #20
Description
Hi!
I am tired but after the pull requests that I have seen and the few time @ogabrielinacio and me to review and maintain the package, I think one thing that can help us is to invest time in creating a suite of tests to ensure this package is not broken between pull requests. Although I recommend people to clone their own frozen copies or copies based on versions from pub.dev, some users may want to have the latest code from main.
Provisioning is a very important step, so let's try to keep it strong!
I suggest to create a suite of tests composed by:
- Unit tests.
- Integration tests.
- Examples.
I added "Examples" as part of the test suites because at the end, the examples are normally basic applications that tries to show the basics by one side and the most advanced features by other.
Unit tests and integration tests can be part of the CI/CD of this package (not configured yet), examples are a bit more hard to maintain but it is an important part so, if after a change, the examples doesn't break, it may be a good sign of health.
I am not committing me nor to anyone, nor @ogabrielinacio to do this. I think it may possible that between all interested ones we can add tests. Unit tests are normally easier to implement than integration tests, so, if anyone is interested, feel free to contribute!
About what testing toolkit we could use it, no idea to be honest. But maybe it is interesting to read: