My test team have been task with writing some automation tests for a tool that interacts with a number third party pieces of software. We have no control over this software and is likely to change at any point in the future. My preferred option is to create a test bed or ‘fake site’ for our application to test all configuration on as the ‘fake site’ will not change unless we change it.
As time is tight the Product Owners want us to write tests against the top 10 third party software that use our tool directly. For me this seems more of a monitoring tool than a testing tool? It could also be difficult to maintain as if the third party changes the software we will also have to modify our tests.
It is also worth noting that we have no contact with these third parties that our tools run against.
I see the value of the ‘Monitoring Tool’ but feel we need to test the tool first before we go on to the Monitoring tool so we can distinguish what the problem is, the tool or the 3rd party site changing