agile Questions

We have a very complex software product that is installed and runs on a Computer or Server.  The Software is managed by a Management Console in the Cloud. 

For years all of our End to End testing was manual.  But this was very resource intensive and time comsuming.  So a couple of years ago we moved to a more agule development approach and built a test automation system to run these End to End tests.  However, we quickly found limitations for example we couldn't have automated tests check what is being displayed in the UI running on the Computer, or check what is being displayed in the Management Console in the Cloud.  So we can never fully replicate in automation what the manual tests were doing.

The result is that we still run, some if not all, of the automated tests manually so check the parts that the automation can't.  So it hasn't really saved us any time or effort.  Also the reliability of the automated tests is an issue due to trhe complexity of the software and it having so many moving parts.  We often run into timing related issues.

Is it possible that some software does not make a suitable candidate for End to End test automation?  If so, what sort of approach should be taken in that situation?  I've been ready about test automation a lot and looked at a number of different tools and systems, but both the tools and the theory all seem to be based around website testing, rather than testing Desktop software.

Many thanks in advance for any thoughts and suggestions. 

I am interested to volunteer for manual testing of web application. How could I do that?

Suppose you work at a Company. 

And a new Client arrives, he needs the system he has, and he continues to build, to be tested. 

What is the approach you take, to find

-which tests to approach

-which tests to automate

-which tools to use

-how to build a solution for that client Testing and Automation testing needs?

I am on a team of two working on standardizing testing for the company. The culture here is very resistant to change, as I am sure many colleagues on here have experienced themselves. I want to continue pushing this elephant up the stairs, but I am afraid some of these templates (IEEE 829 standard templates) are too dense for most of them. My mentality right now is to take this in strides. I want to avoid creating a 12 part test plan that people need to follow if they are just going to get defensive and say they do not have the time to even test, or test this way. Of course we have plans to educate as much as we can, but this is going to take years. What are your suggestions, then, with creating templates? Right now I have identified three that need to be used across all teams (Test Strategy, Test Plan, and Test Summary). We have plans on creating a best practice document/resource for teams to educate them on the industry standards.