Automated testing - review, analyze, improve and document

[marclaporte]

We worked on a manual test plan: #1031

After the release of 2.5.x, let's take some time to brainstorm on automated testing.

@ulfgebhardt @kroky @Shadow243 @mercihabam @josaphatim @Baraka24 @IrAlfred

[marclaporte]

Related: #1553

[marclaporte]

@IrAlfred This is a great use case for automated testing: #1422

[marclaporte]

@kambereBr @Shadow243 Copying here so we don't forget

@Garethp wrote "This looks really good, thanks. I'll merge this in, but if you could add some integration tests for these use-cases, ones where we inspect the objects as set from the SOAP response rather than the tests here that set the properties directly that would be ideal." here: Garethp/php-ews#275 (comment)

[marclaporte]

Related: #596

[marclaporte]

https://unencumberedbyfacts.com/2017/04/26/continuous-testing-for-cypht-with-travis-ci-and-browserstack/

[marclaporte]

Previous discussion: #250

[marclaporte]

Current coverage 80%: https://coveralls.io/github/cypht-org/cypht?branch=master
In 2021, coverage 98% https://coveralls.io/github/jasonmunro/cypht?branch=master

https://github.com/cypht-org/cypht/blob/master/.github/workflows/coveralls.yml

[marclaporte]

Work in progress: #1696