The roles and responsibilities of top management in a project are very huge. They are responsible for recruiting developers and testers, making schedules and so on. While creating a schedule if any doubt about the completion of project with in timeline arises in their mind then they need to rethink about it and reschedule it. They also need to make sure that they recruited right people as well as right amount of people for the project.
I have great respect for developers. There are developers who really work hard and work with passion so that they can develop a quality product. There are developers who respect testers and fix the bugs with real interest. But there also some developers who are aware of the existence of a bug but still they are waiting for a tester to find that bug for fixing it.
Before writing anything about testers I recommend you to read Pradeep Soundararajan’s post "Being a tester V/s Working as a tester". In that article Pradeep shares his learning about two kinds of testers.
a) One who is a tester.
b) One who works as a tester.
a) Good Testers
b) Bad Testers
Good testers are testers who have passion and skill for testing.
Bad testers are testers they lack passion for testing and they are on to testing because they want a job.
I have heard people blaming and cursing Testers for poor quality of software. For such people I have a request "Before cursing or blaming a tester for poor quality of software please think about other factors also”. Because it is not always true that testers are responsible for poor quality of software.
Thanks & Regards