I'm currently tasked with automating a 10+ year old, and rather large application.
There are no exposed APIs, it's built as a monolith. There are no unit tests, nor promise of unit tests to come. The entire application cannot be run locally, and testing has to cover Internet Explorer as the primary platform.
Management think it would be acceptable to have 5000+ selenium tests to cover this. I know this is unworkable and impossible to maintain, especially in an 'Agile' methodology given how flaky both GUI tests in general, and the UI of the system are.
What might be a good strategy to approach this project, other than running far away?