ci(all): add ci pipeline to run unit and integration tests

[damienwebdev]

We should add CI to ensure consistent build quality. Preferably, we should use Azure DevOps.

Currently, while tests are written, they are not run in CI.

We need to run both the integration and unit tests, and these two processes can be done in parallel.

See https://github.com/magento/adobe-stock-integration/blob/1.1-develop/.travis.yml as an example of a working Travis sample. We would need to translate this over to Azure Devops and run against PR builds and master.

• Linting (static) (build(all): adding linting script #16 and Linting fixes #17)
• Unit (Added unit testing to CI  #18 & test(configuration): added/updated unit tests for config files #19)
• Integration
• Api-Functional

[geryjuhasz]

what kind of CI are we talking about ? any specific service ?

[ferfabricio]

I can add Travis CI build if needed, please let me know.

[damienwebdev]

@geryjuhasz @ferfabricio we tend to use Azure DevOps, but if you have a working TravisCI I can port to Azure DevOps format.

[ferfabricio]

@damienwebdev I have a package that was set up with Travis CI and codecov:

https://github.com/tecnospeed/plugnotas-php

If you can I do this setup for this package.

[damienwebdev]

@ferfabricio Let's try it with that to start, see if you can get CI passing in your fork. The integration tests have a dependence on the Magento Integration Test Framework, so it may be more complicated than the setup in that package.

[damienwebdev]

@geryjuhasz I've updated the description to include the ideal services, but as I said, if you can write it on a particular service and get it to work, I'll port it over to what will work for me.

[geryjuhasz]

Sounds good, thank you

…

On Wed, 16 Oct 2019 at 21:36, Damien Retzinger ***@***.***> wrote: @geryjuhasz <https://github.com/geryjuhasz> I've updated the description to include the ideal services, but as I said, if you can write it on a particular service and get it to work, I'll port it over to what will work for me. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4?email_source=notifications&email_token=ABCKTPHE4FFVTXJSWAUBUK3QO5NKZA5CNFSM4JA44JIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBNQGKQ#issuecomment-542835498>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABCKTPH5OB2DAOHPQAKXE2DQO5NKZANCNFSM4JA44JIA> .