QA at Late Dev Phase: points to consider

QA at Late Dev Phase: points to consider
November 18 10:00 2014 Print This Article

Often software producers underestimate importance of software testing and do not acknowledge it as a significant and integral part of a development process.

In order to save time and money or due to other reasons such managers involve a software testing company on late phases of the development life cycle. Doing that they achieve quite the opposite results, as correcting defects at the late phases is more expensive and time-consuming than at the beginning.

Testers miss important stages of the software construction when mobile testing, desktop testing or web site testing starts late.

If Testers Begin to Work at a Program at Late Phases of the Development They do not Participate In:

  • elaboration of the project plan;
  • project risks determining and evaluation;
  • creation of the software requirements;
  • budget planning of the project;
  • static testing of the application.

So, the project managers will not get testers’ remarks and opinion about the mentioned points, and the project will be not so cost efficient as it could have been.

Besides, in this case test engineers need more time on learning the project. They are not familiar with the project peculiarities as profound, as they could have been, if they were involved in the project at the very beginning.

That is why manual and automated testing must start from the first phases of a software development process.

Related Posts:

  • No Related Posts

About Article Author

view more articles
Nataliia Vasylyna
Nataliia Vasylyna

View More Articles


write a comment

No Comments Yet!

You can be the one to start a conversation.

Add a Comment

Your data will be safe! Your e-mail address will not be published. Also other data will not be shared with third person.
All fields are required.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.