Avoiding the “test it”

After a long time of hard trainings, studying complex methodologies, getting the best certifications in the market, we are hired by a company without well-defined testing concepts who wish to start a testing team. Cool, it is interesting the company get this view: we need a team who takes care of our application conformity with what was previously defined and other specific aspects when you choose to get a testing team.The problem is that is common (not because people are ignorante but aknowledged) listen the famous phrase: “application is deployed, test it now”. It is important not just the development team but all the project stakeholders know exactly how testing process works.
These days I have listen the following comment: “I don’t understand why we need a testing professional, we have program that does testing for us!” ok, I agree that it is much easier doing Unit Testing with softwares like JUnit and it is more intelligent using these kind of softwares on it. But JUnit isn’t necessary when the client ask for X and you delivery Y working properly…
Cool! We have a program who finds bugs alone, just clicking a button, why people from Microsoft didn’t do that on Windows? Come on, we know that is not, companies should start getting the testing culture, also universities should introduce Software Testing to the students, this topic is a subject inside the Software Engineering, when mentioned.
It is important to known that JUnit and other related tools are responsible for Unit Tests, which is just an artifact to show that the developer has his task well-delivered. Unit Test (or Component/Modular Test) is just one phase of the whole formal process of the Software Testing, preceded for the Work Product Review and proceeded to the Integration, System, User Acceptance, Regression phase, etc. 
Do you want to introduce a testing team in your company? So, here is a good tip: Try to understand how it works before, like that you know what you should supply and what to ask for to a Test Analyst. Firstly, it’s important to understand that testing isn’t a part of the development process, but a separated process, team, project and/or an apart organization, possibly sold separately from the rest of the development.
When I say that all the stakeholders should understand how testing works, I say all, inclusively clients. Should be understandable that when the project has time and budget involved, it’s common not to cover some functionalities not because people are incompetent but lack of this, for example. In this case not just validation test cases make senses to deliver a system working properly but is a good kick-off…