One of the challenges our QA faces is being able to test our application, which abstracts behavior from the SaaS API, such as the SF API, Eloqua API, Google API, etc., and ensuring the applicatino is behaving correctly. Some SaaS sources have data that changes and we DO need to also verify data. Since some of the SaaS sources are also not updateable programatically, you can't know if the SUT is in the state you need it. Thoughts?
It seems that a popular approach to QA automation is a quick start to cover a most critical area with automated tests ASAP and then proceed automating other areas of testing. This second phase requires more dedicated tool(s). So, what features are most important for such a tool so that it could be useful for your web application?
Visual baseline: to compare with results of new test runs
I am a test automation specialist and test manager and I am seaching for ideas in which way I have to change my mindset, my knowledge and tool expierience when beeing part of a development team or company for developping digital services and products?